When I edit the title, occasionally I'm getting:

(some JS pop-up before that, sorry, didn't catch it, then...)

JS error

And then I'm taken to admin/edit/field/node/1/title, which outputs a bunch of JSON:

[
{
command: "settings",
settings: {
basePath: "/spark/",
pathPrefix: "",
ajaxPageState: {
theme: "seven",
theme_token: "4jUchXTP5z-Ui9OeN_WZedEZS4LufwQmJeCtC2NuKjw"
}
},
merge: true
},
{
command: "edit_field_form_saved",
id: "node:1:title"
}
]

Comments

Dave Reid’s picture

Version: » 7.x-1.x-dev

I've been able to reproduce this as well.

Dave Reid’s picture

Because Drush doesn't rebuild the menu after enabling modules, I had to manually do a drush cc menu in order to have the AJAX messages go away.

Wim Leers’s picture

Assigned: Unassigned » Wim Leers

Thanks for your report, Dave!

If it's a simple matter of menu rebuilding, I can force that to happen through hook_install(), though that is of course very ugly because Drupal normally takes care of that when installing modules. I don't recall encountering this problem when installing any module through Drush. If you happen to know more about this peculiar Drush behavior, feel free to post pointers :)

Dave Reid’s picture

It's a bug in Drush that needs to be fixed. Would be good to at least hear from Angie if that will also resolve her ajax errors.

webchick’s picture

Tentatively, yes. In that I did drush pm-uninstall edit; drush en edit and got the AJAX error on the title field, then did drush cc menu and reloaded and the error went away.

Drush having a bug with not clearing the menu cache would also explain some other weird behaviour I've seen in totally unrelated modules lately.

webchick’s picture

Status: Active » Postponed

Looks like #1649368: Enabling/Disabling modules does not clear cache (menu) is the upstream bug.

Marking this postponed on that one.

Wim Leers’s picture

Title: Random AJAX errors » AJAX errors when installed using Drush
Wim Leers’s picture

Priority: Critical » Minor
Status: Postponed » Closed (works as designed)

This was apparently fixed upstream :)