![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png){kind=small}
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png){kind=small}
Entry tags:
New Create Entries management page
This 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.
* Rich Text editing
* Using the new Create Entries page for editing existing entries
* Using the new Create Entries page for comm admins deleting posts or performing admin overrides
* Draft posts of any type, including the in-browser saved drafts that exist right now
* some difficulties crossposting, looks like possibly date-related? we're trying to figure it out.
* Settings not properly saving when using the "gear" customize-this-page popup; some modules disappear
* Create Entries form being repeated after posting an entry
* Error in link to Beta Features at top of page
* Error messages when using new update page in older versions of Firefox
* Difficulties with IE (oh, IE)
* Errors with time being truncated
* inactive icons showing in the icon browser
* minsecurity of journal not reflecting properly in update form
* whole host of display glitches
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
* Rich Text editing
* Using the new Create Entries page for editing existing entries
* Using the new Create Entries page for comm admins deleting posts or performing admin overrides
* Draft posts of any type, including the in-browser saved drafts that exist right now
Known/Reported Bugs
* some difficulties crossposting, looks like possibly date-related? we're trying to figure it out.
Should be fixed
* Settings not properly saving when using the "gear" customize-this-page popup; some modules disappear
* Create Entries form being repeated after posting an entry
* Error in link to Beta Features at top of page
* Error messages when using new update page in older versions of Firefox
* Difficulties with IE (oh, IE)
* Errors with time being truncated
* inactive icons showing in the icon browser
* minsecurity of journal not reflecting properly in update form
* whole host of display glitches
Non-Crossposting Bug
However, if I don't want to crosspost, and untick the parent "Crosspost This" ticky box, I get the following bug: the child ticky for LJ grays out but remains ticked; if I attempt to submit the form (with title and body contents and all) by hitting either of the "Post" buttons, the form does not submit, and the label for the empty password field associated with crossposting to LJ turns red, nagging me to populate it. Which I shouldn't need to do if I'm not crossposting.
To post without crossposting, I have to manually turn off the child tickybox (the one specific to crossposting to LJ), and I have to have the parent tickybox ("Crosspost This") on to do so. (When I do, it unticks and grays out the parent tickey box.)
Put another way, unticking the "Crosspost This" ticky box doesn't turn off crossposting; crossposting remains on so long as the child ticky box (indicating the site to crosspost to) is on, and the child ticky box is not unticked by unticking its parent, as is conventional; in that weird state, the form does not submit, and the user is prompted for a password they shouldn't need.
(Also, it took me way too long to figure out what was wrong, because the prompt for the missing password is so low-key, I didn't notice it. (It may have scrolled off the screen at the moment I tried to submit?) All I could tell is that pushing the "post" button did nothing, and I figured it might just be some CSS or JS bug/imcompatibility w/ my browser. Maybe make the "Can't submit, missing required info" notice more prominent?)
FF 48.0.2 on Mac OS 10.6.8.