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

[juan_gandhi]

Hey, I've been using beta for a while, but where's "set post date"? I'm currently having fun filling my blog with dates from the past, hoping to go as deep as when I was 3 years old (I kind of have a very very good memory).

[denise]

Click the "rearrange panels" link in the top right corner and enable the "Display Date" panel! (We chose which panels were default-enabled based on how often the function in them was used, and very very few people change the dates on posts when they're posting, so that one didn't make the threshold.)

[juan_gandhi]

Thank you! Will do.

[passingbuzzards]

I’ve found that the new post editor sometimes prevents you from posting by claiming there is an unclosed HTML tag when that’s not actually the case. Specifically, I had an unordered list within the bullet of another unordered list, which the beta post editor blocked me from posting by claiming that one of the <ul> tags was unclosed (presumably the higher-level one?). In reality there were two <ul> tags and two </ul> tags; post preview didn’t show any errors and I was able to make the post once I switched back to the old editor.

ETA: After further investigation it looks like this was caused by having an extra </li> tag! But it the reason shown for not being able to post is specifically “Unclosed tag(s) in entry: <ul>” and for whatever reason this doesn't cause an error in the old editor (or in how the post is displayed).

[gurge]

uhh i've never done this before so here goes!

i'm on ios and using vivaldi. i'm trying to delete a private journal entry. i click 'yes' to confirm deleting it and then the page refreshes and tells me i have unclosed html tags, but the entry is not deleted. i tried a few times in the same window, then tried again on my phone - android s10e with google chrome browser - and got the same result.

it's looking like i'll have to switch out of beta to delete the entry.

Edit change date

[marianme]

Couldn't figure out how to post date an html beta post.

Re: Edit change date

[denise]

Hit the "rearrange panels" in the upper right, enable the "display date" panel!

beta Rich Text Editor - default text size in editor is very small

[darkoshi]

I have been using the beta version of the Create New Entry page for a while now and haven't noticed any problems with the "Casual HTML" option.

I noticed a problem with the "Rich Text Editor" option: The "size" dropdown has no entry selected by default, and with it blank like that, any text I write in the editor displays very small - the same as when I select size = "extra small". Shouldn't it default to a medium size text? If I leave the size unselected, then once I post the entry, the text in the entry displays in a normal size; it's only in the editor itself that it is so small.

Re: beta Rich Text Editor - default text size in editor is very small

[denise]

The rich text editor is the same as the one in the old update page -- it's very old (and very broken in many newer browsers) and we are hoping to rewrite it, but it's a very daunting task. But any issue such as this isn't a part of the new update page, it's just the RTE being very old and very broken and modern browsers not handling it well.

Re: beta Rich Text Editor - default text size in editor is very small

[darkoshi]

Ah, okay. That makes sense. I didn't realize it wasn't rewritten too.
It's no issue for me as I don't usually use the RTE. But someone on my friends list mentioned using it, so I thought I'd try it out.

[klia]

(Using Firefox 109.0 (25841) on iPad OS 16.7.2)

I'm not seeing any way to disable comments on an entry? Am I somehow missing it?

[denise]

It's in the "Comment settings" panel! (I can't remember if it's enabled by default or not, but if it isn't: hit the "Rearrange panels" gear icon in the upper right of the update form, check that box to include it.)

[klia]

Thanks. There was no comments panel on the whole page, so it must not be one of the primary/default panels?

Suggestion: display HTTPS in Entry Links

[ninetydegrees]

Suggestion: display HTTPS in Entry Links

The link that is displayed in the Entry Links module uses "http" instead of "https".

[swordarc]

I personally wish that when the beta editor throws an error over unclosed tags, it would indicate where the unclosed tag is in the post. I recently got an error involving an unclosed < div > tag, but the post in question used so many < div > tags that I couldn't find the problem one and ended up just switching back to the old editor to make the post go through.

[mindstalk]

Bug report:

Create Entries, using Markdown. Putting a URL in angle brackets lowercases the final URL, which breaks Google short links.

E.g. https://maps.app.goo.gl/ShTY8EGczovcMSMWA vs. this.

...though apparently the effect doesn't happen in comments!

[denise]

Ohhhh, now that's just weird. Thanks, I'll file an issue!

[mrshamill]

I didn't read through all the comments so I don't know if this has been noted, but I was unable to find the option to turn off comments on a post. Am I missing something?

[denise]

Hit the "Rearrange panels" in the upper right, check if you have the Comment Settings panel enabled: turning off comments is the first of the two options ("Comments:" set to "Disabled" turns off comments!)

[med_cat]

When editing an entry in the beta mode (which has been posted in beta mode), unable to save the edits. This is the message I get:

Unclosed tag(s) in entry:

[denise]

That error means you have a mistake in your HTML of the entry: look for the beginning <div> tag and put the closing </div> tag at the end of that block.

[med_cat]

Right, I thought as much but couldn't find that tag, and I just looked again and still can't find it. Once I turned off the beta feature, I was able to edit the entry without any difficulty...

[madripoor_rose]

Apologies if this is something basic, I'm tech illiterate: I partition off segments of a post with asterix because I like the way that looks. Suddenly that's showing up as an unevenly centered line?

[pangolin20]

Then you're using Markdown, where this indeed shows up as such a line. If you want to keep using Markdown, the best option is to use "*" for each asterisk.

[sireesanwar]

My issue is this:

When I go to post it comes up as Raw HTML. If I post this way then I can't switch to any other view. I want to see it in Rich Text Editor but it will not switch. I have tried multiple times on several communities and my journal.

I'm using Firefox 136.0.2 on a PC's Windows 11.

I was able to accomplish it in Edge.