New Create Entries management page

[denise]

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.

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

Comments

[aedifica]

I have found a problem after all: display date is defaulting to a set date/time in the past (it looks like it's whatever date&time I last posted, though I'm not sure about that yet). When I hit "Post" I get an error message (displayed below) and the subject line, icon, *and security level* change back to my defaults, though the text of the entry is still there in the entry text box. So I fix the time, overlook the fact that the subject, icon, and security level have changed, and hit "Post" again... and get an entry accidentally posted at the wrong security level. I see fu's comment elsewhere indicating that that part might be fixed when drafts are enabled. But the defaulting to a set date/time in the past is still a problem.

The error message:
Error
- Incorrect time value: You have an entry which was posted at 2011-11-15 21:12, but you're trying to post an entry before this. Please check the date and time of both entries. If the other entry is set in the future on purpose, edit that entry to use the "Date Out of Order" option. Otherwise, use the "Date Out of Order" option for this entry instead.

Browser: Firefox 8.0 on this Windows 7 64-bit computer; I've noticed the same behavior on some other device--I don't remember for sure which device, but I think it was my T-Mobile G2 running Android 2.3.4, using the built-in browser.

P.S. I saw denise's discussion of entry date/time being a bikeshed issue, and I can respect that, but I *think* this is different: I'm not as worried about whether it defaults to one option or the other as I am about the fact that the date it's picking is unconnected to the time I'm writing or posting the entry.

[denise]

It is different, yeah -- the time should be the time the update page was opened, so as long as you haven't opened a new update form in another tab or another window and posted another entry in between the time you opened this one, you shouldn't have problems.

Can you try clearing your browser cache (without the update page open) and try opening a new update form again? See if that shows the right time (it could be your browser is caching an old version of the form).

[aedifica]

Post-cache-clearing: That looks much better, yeah--I think that was the problem. Thank you!

[denise]

\o/