new create entries beta

[denise]

We had the old "new JS on journals" beta reporting entry as the topmost entry in this comm, which was causing some confusion! So, a fresh post for people to report problems they're having with the new Create Entries beta.

Things not yet implemented:

* a WYSIWYG/rich text editor to allow people to post formatted entries

* the ability to save draft entries, both so you can deliberately postpone entries for posting later and so that an unexpected browser crash or problem during the posting process won't cause you to lose work

* admin editing of community entries

* the "don't autoformat" checkbox (we can't quite figure out which pane to stick it in!)

Things that will be documented once it comes out of beta, but some people have missed:

* if you don't like the placement of panels or don't want to see certain panels, you can customize the placement and which panels appear by using the " Settings" link in the main toolbar at the beginning of the form.

If you have anything else to report, please let us know here!

Comments

[denise]

As it happens, there are some slight differences between the two update pathways, and it's possible that someone might be able to use this information to figure out what exactly is going wrong here and be able to fix it! Just to set expectations: the iPhone 5 is outside our device/browser support window, and we do try to make an effort to keep core functionality working in older browsers/on older devices, but there's a certain point at which we have to draw the line (if only because we just don't have the resources to test on older devices and in older browsers, and if you don't have access to an older device to test on, it's often impossible to figure out if you've been able to fix the bug!)

I've passed this along to see if anyone has any immediate ideas as to what might be happening here, but unfortunately I can't guarantee anyone will be able to fix it; with browsers/devices that are outside the window of our formal support policy, our practice is generally to poke at it for a few hours and see if anything obvious leaps out at us, but not commit fully to being able to fix it or to spend more than a few hours on it. It will probably wind up being that we can't fix it, because those kinds of bugs are usually impossible to track down and identify the source of and because it's probably that the browser/OS doesn't support some of the HTML/CSS we're relying on, but the fact it works differently on the two different versions of the update form means there's a chance someone might go "aha! I know what that is!" and be able to do a fix for you. We'll give it a go and see if anything obvious leaps out at us.

[lb_lee]

No problem, I figured it was something like that; it’s an old phone! And hey, I can post with it even if the method’s odd, so I have no complaint! Just figured I would share the info in case it’s handy.