Create a new blog post JS error

I can't reproduce on a local environment.

On the trial server, I can't reproduce neither.

Could you specify which error is in the web developer console?

I have seen this once or twice. It seems to occur when editing default content provided by a recipe, immediately after applying it. I was never able to reproduce it reliably though.

Oh wait, I guess this is different, I've only seen it on the first load of the edit form -- don't think I have seen it on node/add.

This happened to me once yesterday too hitting edit.

Happened to me several times today after a fresh install of Drupal CMS.

Creating a new node:page.

Clicking on `edit` from the canonical page, happening too as soon as the edit form is loaded in the browser.

Happened again creating a new node a few minutes after.

And again editing a translation of this node.

Seems to be random but also seems to be related to the "auto save" feature. Not sure.

Adding screenshot

Moving to Autosave Form queue. Does anyone have additional info about the error?

Whoever is experiencing this, could you please check your "recent log messages" if a more descriptive error is being logged?

Also maybe observe the network tab in the browser console and show some screenshots from there when this error occurs.

After digging through the issue queue this seems rather related to 🐛 Ajax error ajax.$form.ajaxSubmit() is not a function RTBC . Could you please check if you can still reproduce it after applying the patch from over there?

Thanks for looking into it @hchonov! I have not been able to reproduce it reliably, I just tried a fresh install twice (once via UI and once via drush) and I'm not seeing it now. Even when I did see it in the past, it only seemed to happen once on the first load.

If anyone else who saw it could provide more info or possibly test the patch that would be great!

In the meanwhile I am moving it back to the "Drupal CMS development repository" project so that it can get more eyes on it as it seems rather related to a different bug and not really caused by autosave_form.

I dig deeper into it and found what could be potentially causing autosave_form to cause this strange behavior. I investigated further the referenced issue 🐛 Ajax error ajax.$form.ajaxSubmit() is not a function RTBC and now I am introducing a workaround to ensure that autosave_form would not be causing this issue for anyone until Drupal core accepts my proposed solution over there.

I feel like everyone in here deserves a credit. I just released a new version 1.9 with this workaround.

Wow! Thank you for fixing and even doing a release so quickly.

You're welcome :). It would be great though if everyone that was experiencing the issue could update locally their autosave_form module (composer update drupal/autosave_form) and check that they do not experience this issue anymore.

Automatically closed - issue fixed for 2 weeks with no activity.