![[sticky entry]](http://www.dreamwidth.org/img/silk/entry/sticky_entry.png){kind=small}
The next code push will update the new Create Entries page in beta with a number of fixes for previously-reported bugs and enhancements. To make it easier to keep track, we're therefore opening up a new bug-reporting post (to avoid confusing things with bugs reported in the previous post).
When reporting bugs, please include:
* The browser name, browser version number, and operating system you're using
* The steps you took to reproduce the problem
* Whether or not you've tested the same steps in another browser (and if so, which)
* Whether you get the same result every time you try the same steps, or if it only happens sometimes
If we can't reproduce the problem under the same browser and operating system, we may also ask you for a list of any browser extensions you have installed.
Things that are still not yet implemented:
* the "don't autoformat" button
* the rich text editor
* editing existing entries (it will display the old form)
* draft posts of any type, including autosaving of entries
There are also still some issues with IE, especially in "privacy mode". Anything that requires Javascript is currently not working in IE in privacy mode, and we're trying to figure out if there's something we can do to fix that or if the settings of the browser override anything we can do.
New Create Entries management page
Oct. 30th, 2011 11:28 pm![[staff profile]](http://www.dreamwidth.org/img/silk/identity/user_staff.png){kind=small}
deniseThis post is to report bugs in the new Create Entries page. This is a complete rewrite of the old Update page, in order to allow for future expansion and new features such as draft posts, scheduled posts, recurring posts, expanding the range of what can be posted to your journal, and a whole host of other awesome things.
When reporting bugs, please include:
* The browser name, browser version number, and operating system you're using
* The steps you took to reproduce the problem
* Whether or not you've tested the same steps in another browser (and if so, which)
* Whether you get the same result every time you try the same steps, or if it only happens sometimes
If we can't reproduce the problem under the same browser and operating system, we may also ask you for a list of any browser extensions you have installed.
Not all features are completely implemented in the new Create Entries page yet. The biggest thing currently missing is the Rich Text editor -- the only option is the plain-old-HTML option. The design of the page is geared towards changing concepts and visual/workflow metaphors around what it means to "post an entry", too -- because of the forthcoming draft and scheduled posts, we needed to adapt some of the language and some of the ways we present concepts -- even though the draft and scheduled post functionality isn't ready to be released yet. So, if something looks awkward or like it doesn't quite fit, it's probably there to allow for something we'll be releasing in the future. (You can still mention it, though!)
Things we also consider to be bugs that should be reported, in addition to something not working right:
* if you can't figure out what to do at any step of the update process
* if you have accessibility-related problems (with your screenreader, with the tab order of the page, with the workflow, etc)
* if something about the new workflow completely breaks the way you use your journal, and you can't figure out any way to work around it (there may be a way to do what you're used to doing, but if you can't figure it out, that's something we might change or might want to document, etc)
You can enable or disable beta testing at any point.
( Not yet enabled + known bugs lists )
When reporting bugs, please include:
* The browser name, browser version number, and operating system you're using
* The steps you took to reproduce the problem
* Whether or not you've tested the same steps in another browser (and if so, which)
* Whether you get the same result every time you try the same steps, or if it only happens sometimes
If we can't reproduce the problem under the same browser and operating system, we may also ask you for a list of any browser extensions you have installed.
Not all features are completely implemented in the new Create Entries page yet. The biggest thing currently missing is the Rich Text editor -- the only option is the plain-old-HTML option. The design of the page is geared towards changing concepts and visual/workflow metaphors around what it means to "post an entry", too -- because of the forthcoming draft and scheduled posts, we needed to adapt some of the language and some of the ways we present concepts -- even though the draft and scheduled post functionality isn't ready to be released yet. So, if something looks awkward or like it doesn't quite fit, it's probably there to allow for something we'll be releasing in the future. (You can still mention it, though!)
Things we also consider to be bugs that should be reported, in addition to something not working right:
* if you can't figure out what to do at any step of the update process
* if you have accessibility-related problems (with your screenreader, with the tab order of the page, with the workflow, etc)
* if something about the new workflow completely breaks the way you use your journal, and you can't figure out any way to work around it (there may be a way to do what you're used to doing, but if you can't figure it out, that's something we might change or might want to document, etc)
You can enable or disable beta testing at any point.
( Not yet enabled + known bugs lists )
New changes live
May. 17th, 2011 02:47 pmfuNew with this code push, including fixes so that the JS always works even when expanding multiple layers, e.g., even after viewing answers, or after expanding a cut:
And a couple of tweaks, chiefly:
- polls
- media placeholders
- contextual hover
- expand all cut tags module
And a couple of tweaks, chiefly:
- fix quick reply overlapping content in some layouts
- make screened/delete/etc work for expanded comments
JS Conversion Beta: Report issues here!
Apr. 21st, 2011 01:53 amdeniseIf you're participating in the JQuery conversion beta test, report any issues you find here!
Currently, here are the things that have been implemented (and not implemented):
Implemented
Cut expand and collapse
Logging in
Screen/freeze/delete
Control strip injection for non-supporting journals
Quick reply
Thread expander
Not implemented
Contextual hover
Media embed placeholder expansion
Same-page poll submission
Icon browser
Same-page comment tracking
(This means that if you try to do something on the "not implemented" list while you have the beta features turned on, you'll be routed to the non-Javascript/non-inline version. That isn't a bug and you don't have to report it, but you should report anything else that's weird or that doesn't behave the way it used to!)
Currently, here are the things that have been implemented (and not implemented):
Implemented
Cut expand and collapse
Logging in
Screen/freeze/delete
Control strip injection for non-supporting journals
Quick reply
Thread expander
Not implemented
Contextual hover
Media embed placeholder expansion
Same-page poll submission
Icon browser
Same-page comment tracking
(This means that if you try to do something on the "not implemented" list while you have the beta features turned on, you'll be routed to the non-Javascript/non-inline version. That isn't a bug and you don't have to report it, but you should report anything else that's weird or that doesn't behave the way it used to!)
hello beta testers!
Apr. 10th, 2011 06:29 pm![[personal profile]](http://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
domtheknightAt long last there are specific things that need doing!
For some background, check outdenise's explanation of technical debt. One of the things she mentions near the end is that we need to mingle JQuery with the existing Javascript the site uses.
This is a big change for how the site works, and it means that things could go wrong when it goes live. We now have a way you can turn on beta testing so that we can see how the new code will operate on a day-to-day basis.
If you want to check it out, you can! If you notice any weird behavior, please let us know - you can comment here.
A couple things to note: not all the features you might enjoy right now will be available in beta testing, because not everything has been rewritten yet. There's a list available on that same page, and you don't need to report those things because our excellent devs are already working on them.
At any point in time if you want to switch back, you can just go to the same page and turn beta features off.
For some background, check out
denise's explanation of technical debt. One of the things she mentions near the end is that we need to mingle JQuery with the existing Javascript the site uses.This is a big change for how the site works, and it means that things could go wrong when it goes live. We now have a way you can turn on beta testing so that we can see how the new code will operate on a day-to-day basis.
If you want to check it out, you can! If you notice any weird behavior, please let us know - you can comment here.
A couple things to note: not all the features you might enjoy right now will be available in beta testing, because not everything has been rewritten yet. There's a list available on that same page, and you don't need to report those things because our excellent devs are already working on them.
At any point in time if you want to switch back, you can just go to the same page and turn beta features off.
domtheknightIf you edit your adult content flags on an individual entry when attempting to crosspost to Insanejournal, the crosspost will fail. It doesn't seem to matter what the original default adult content setting was, and it doesn't matter how many accounts you crosspost to at the time.
#1067: paid account status
May. 2nd, 2009 12:04 pmdomtheknightIf you upgrade to a paid account, some of the features are not properly upgrading right away. (Some of you might have noticed that you can't use all of your icons, for example. You can fix that particular issue by going to edit icons and saving - no need to make any changes.)
There's a patch out for this already, so it'll hopefully get fixed pretty quickly.
ETA: this has been fixed! You might still need to do the icon fix mentioned above, but any future upgrades will work properly.
There's a patch out for this already, so it'll hopefully get fixed pretty quickly.
ETA: this has been fixed! You might still need to do the icon fix mentioned above, but any future upgrades will work properly.
#984: comment subscriptions tied together
Apr. 26th, 2009 12:41 amdomtheknightIf you want to subscribe to comments in your own journal, you also have to subscribe to replies to comments in other journal (and vice versa). If you try to only subscribe to one of those, the changes won't save.
domtheknightIn Internet Explorer (version 7, perhaps previous versions as well), the "add another" buttons to upload multiple icons at a time don't work.
ETA: I've received additional data that the button doesn't work in IE6 or IE8, either.
ETA: I've received additional data that the button doesn't work in IE6 or IE8, either.
#938: crossposter strips LJ code
Apr. 25th, 2009 11:07 amdomtheknightThe crossposter currently strips LJ-specific html (such as the lj user tags or the lj-cut).
ETA: this is fixed!
ETA: this is fixed!
#750: location problems
Apr. 11th, 2009 01:18 pmdomtheknightFYI for saving your location on profiles: there's a bug where some countries will pull in "(states/regions/territories)" and then, when you try to save, give an error message of:
"You specified the United States as your country, but typed a non-US state in the "other state" field."
In some cases this bug might appear even if no location was picked at all.
(And perhaps relatedly, if no location is set, profiles are displaying "(states/regions/territories)" instead of hiding the location field altogether - that's bug 751.)
ETA 4/25: 750 has been fixed but 751 has not. So, you should be able to save, but the display might show up incorrectly still.
"You specified the United States as your country, but typed a non-US state in the "other state" field."
In some cases this bug might appear even if no location was picked at all.
(And perhaps relatedly, if no location is set, profiles are displaying "(states/regions/territories)" instead of hiding the location field altogether - that's bug 751.)
ETA 4/25: 750 has been fixed but 751 has not. So, you should be able to save, but the display might show up incorrectly still.
#732: membership in moderated comms
Apr. 7th, 2009 10:46 pmdomtheknightThere's a bug with moderated membership for communities. Users are able to request to join and the notification is sent to the admin, who approves the membership and gets a 'success' message. But those new members don't show up in the membership list on the profile or on /community/members.bml.
Admins are able to send invites to users, and users are able to accept the invitation, at which point in time they receive "you are now a member of $comm" message, and the invitgation shows up as accepted. But just like in the first case, users don't show up on the profile or /community/members.bml.
We also tested for functionality - people in this situation can't post entries.
(Incidentally, this affects![[site community profile]](http://www.dreamwidth.org/img/comm_staff.png)
dw_beta; if you requested membership sometime after mid-March, I approved you, but you can't see that.)
ETA: moderated membership is working correctly, but if you approved people during the downtime, you have to re-approve them all.
Admins are able to send invites to users, and users are able to accept the invitation, at which point in time they receive "you are now a member of $comm" message, and the invitgation shows up as accepted. But just like in the first case, users don't show up on the profile or /community/members.bml.
We also tested for functionality - people in this situation can't post entries.
(Incidentally, this affects
dw_beta; if you requested membership sometime after mid-March, I approved you, but you can't see that.)ETA: moderated membership is working correctly, but if you approved people during the downtime, you have to re-approve them all.
testing needed!
Apr. 6th, 2009 02:12 pmdomtheknightI need a couple of specific things tested:
1. If any of you ported a style from LJ (etc) prior to core2's release, and have not since upgraded your style to core2 (so you're still on a customized core1 style), we need to do some specific testing in that circumstance to try to reproduce a reported bug.
2. If any of you also have openIDs, we need to look at something with comments and comment notifications.
3. I need people to look at the menus in multiple browsers to see if anyone can reproduce this issue: picture of problem (what looks like tiny chunks of menu missing). That specific photo is from Safari 4.
If you can do any or all of those things, please comment here or PM or email me and I'll give you more details.
ETA: all of these tests should be done now, thanks!
[cross-posted to beta-testing listserv]
1. If any of you ported a style from LJ (etc) prior to core2's release, and have not since upgraded your style to core2 (so you're still on a customized core1 style), we need to do some specific testing in that circumstance to try to reproduce a reported bug.
2. If any of you also have openIDs, we need to look at something with comments and comment notifications.
3. I need people to look at the menus in multiple browsers to see if anyone can reproduce this issue: picture of problem (what looks like tiny chunks of menu missing). That specific photo is from Safari 4.
If you can do any or all of those things, please comment here or PM or email me and I'll give you more details.
ETA: all of these tests should be done now, thanks!
[cross-posted to beta-testing listserv]
#681: html in comment previews
Apr. 4th, 2009 10:36 pmdomtheknightIf you use the 'check spelling and preview' option when posting comments, the html shows up in raw form. If you just preview without checking spelling, the html shows up correctly.
#623: logging in on ?mode=reply
Mar. 31st, 2009 10:27 pmdomtheknightIf you're viewing an entry at ?mode=reply, and try to log in using the comment submission form, you instead are sent to a page with an error, "Your login cookie seems to have disappeared?".
domtheknightOne-sided relationships don't display accurately in the nav strip. If I subscribe or give access to a user but that user does not subscribe or give access back, the nav strip should state that I have subscribed or given access. Instead, it states that I am viewing [user]'s journal with a link to add him or her to my circle.
Where the relationship is reciprocal, or where the other user has subscribed or given access and I have not, the nav strip is correct.
Where the relationship is reciprocal, or where the other user has subscribed or given access and I have not, the nav strip is correct.
domtheknightWhen users are banned there appears to be a 'select all' button at the top of the list (at http://www.dreamwidth.org/manage/banuse
FYI: password problems on posting
Mar. 31st, 2009 11:07 amdomtheknightIn case you're trying to post right now, there's a known issue with a recent password patch. denise posted about it at dw_maintenance here.
denise posted about it at dw_maintenance here.domtheknightOpenID users can see locked posts (to which they have access) on the 'Recent Entries' page but not on day, month, year, or tag views.
domtheknightIf an error occurs when editing the profile, the error data doesn't print; instead a blank page with 'Edit Profile' is loaded.
ETA: fixed! Errors should now print.
ETA: fixed! Errors should now print.
