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
no subject
thanks for the report; will keep an eye out for others, in case it becomes an issue later (I love how, even when you're unable to reproduce, you list all the necessary elements for maybe-future-reproduction *g*)
2) re: gear wiping out all modules
*chinhands* I think that it works better now. I'm assuming that the gear used to take you to a different page, instead of being on the same one?
3)
Hmm, by clear these fields, start over, do you mean the entry form itself?
4) create poll link:
*ponders* *adds to list* I hope to make it a moot point by having the create poll be on the form itself rather than leading off, but I'll see what I can do!
5)
oops, fixed!
6) there's actually no draft saving at the moment (I'm pretty sure that's just browser caching the field values at work), but I will keep that in mind, yes! It's all part of the draft saving stuff that's next on my list.
no subject
3) Yeah. Like a "clear fields" or "wipe this page" or "there's a bit of half-formed thought on your chin" or something. With the old update page, when I start an entry then change my mind, I'd refresh the page. It'd ask me if I wanted to restore from draft or start anew, and I could click Cancel to start anew.
4) I would be so far beyond in hearts with the poll creator being on the same page, it would be ridiculous and possibly embarrassing. ^^
6) Yeah, any draft saving has ever been the browser remembering things, largely because of the LJ code letting that happen. I just wish that the LJ code underneath actually remembered the security setting. Hell, if it set it to private each time, that would be an improvement. I just have times where I'm writing a sensitive post, run off to do something else, then come back, and it helpfully remembers my post, but not that I set it to not-public. I have so far remembered to check that, largely due to being incredibly neurotic, but I'll be on anti-anx meds one day, which means I'll have to rely on my memory. D:
Whee! This is fun!
no subject
3) Hmmmmmm. Out of curiosity, if you do ctrl+f5 or ctrl+shift+R, or if you click the address bar and hit enter, does the text remain cached?
(I can't get text to stay cached in my browser for some reason, so I can't check the same way *g*
6) FWIW, remembering the security setting is on my list *g* (only for the new page though)
no subject
6) Hooray!!
no subject