denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
Denise ([staff profile] denise) wrote in [site community profile] dw_beta2011-10-30 11:28 pm
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.



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
momijizukamori: (dreamsheep | styles)

[personal profile] momijizukamori 2023-11-11 02:15 am (UTC)(link)
I checked with Denise and the change to the tag field was because a significant number of people were giving the feedback that they wanted some kind of tag validation at the time of entering the tag because they had too many tags created by accident by typos and managing/merging the typo tags was a pain in the neck
trobadora: (Default)

[personal profile] trobadora 2023-11-11 08:42 pm (UTC)(link)
Oh, that's interesting, I can see why people would want that! Though I'm not actually seeing how that works - new/misspelled tags seem to display identically to established ones once they're entered? And the old form already had autocomplete. (Sorry if I'm misunderstanding something!)

For how the tags display, would it be possible to make the comma-separated list an option that users could select? Or is that entirely impossible with the new code?
momijizukamori: Green icon with white text - 'I do believe in phosphorylation! I do!' with a string of DNA basepairs on the bottom (Default)

[personal profile] momijizukamori 2023-11-11 10:21 pm (UTC)(link)

Hmm, they should be styled differently - are they not for you?

'fediverse' is an existing tag for me, 'fabric yay' is a new one.

It's not impossible but we're really, really at the point where we need to get this out of beta first, which means any changes that aren't 'this is functionally broken' aren't gonna happen right now, sorry!

Edited (meant to embed the image, whoops) 2023-11-11 22:22 (UTC)
trobadora: (Default)

[personal profile] trobadora 2023-11-11 10:30 pm (UTC)(link)
Oh! No, you're totally right - there's a difference with the new tag having a dotted line border, that didn't register for me at all. I was only looking at the tag itself, not the border. Thanks for your patience!
momijizukamori: Green icon with white text - 'I do believe in phosphorylation! I do!' with a string of DNA basepairs on the bottom (Default)

[personal profile] momijizukamori 2023-11-11 10:31 pm (UTC)(link)

np! Yeah, it's a little subtle but it's there :)