jQuery is pretty irritating, turns out. Upgrading it apparently breaks things. Rolling back to the backup via backup/restore didn't fix the issue, either, which leads me to ask what "backing up and restoring the codebase" even does—or is even supposed to do—if it won't reset issues created by fiddling with updates.

So the site has a menu, which is accessible as an anonymous user only now. Once I login, the menu vanishes. Since I was messing with the jQuery stuff (which turned out to be not even relevant to the unrelated problem I was having with the LESS library/module—and even deactivating this does nothing, but I'm not sure why it would anyway).

How can I get the site's menus back? It doesn't appear to be a permissions issue, restoring from an earlier backup fixes nothing, clearing all caches, etc. etc. etc. and it's becoming difficult to retain any sort of patience with this. If there's no way to do this, is Drupal 8 ready for prime time?

Argh.

I'd show screenshots of the issue, but the forum doesn't seem set up for a convenient what of show them. Basically, the menus from here: cubelight.graphics are missing once you log in. It makes no sense to me at all.

So. Any ideas?

Details: Seven administration theme, Bamboo regular theme, Drupal 7.43.

Comments

Jaypan’s picture

You didn't say how you updated jQuery.

And as for it being annoying, it's actually a pretty amazing little library. Your anger is misplaced in this case, as it's likely a caching issue or a human error somewhere.

cgfx’s picture

I updated with drush:

drush up jquery_update-7.x-3.x-dev

Then, once I saw the menus were broken (but only if logged in), I tried to go back to the earlier version:

drush up jquery_update-7.x-2.7

When that didn't change anything, I tried rolling back to an older version of the site via Backup & Restore. (Which doesn't seem to work as one would expect, I'm noticing. Baffling.)

At each step, all caches were flushed, and the site was loaded on iOS Safari, Safari, Chrome, and Opera, so I doubt caching is an issue. And even if it is, why are the menus visible to anonymous visitors, but not to me when I'm logged in?

Your anger is misplaced in this case, as it's likely a caching issue or a human error somewhere.

Obviously, since the problem only became an issue after I messed with jQuery. But you can understand why this sort of stuff is annoying? Why would this even break anything?

Jaypan’s picture

Ok, now we're getting a little further, you didn't update jQuery, you updated the jquery_update module. These are different things. jQuery is a javascript library. The jQuery update module is a module that allows you to change the jQuery version you are using. And looking at the version you upgraded to: drush up jquery_update-7.x-3.x-dev - it's a dev version. These are rarely stable enough for a site, and that's very likely why it broke.

I have no idea why rolling back didn't work, but what I'd suggest is fully uninstalling the jQuery update module, then reinstalling the 7.x-2.7 version. This should clean out the database of any remnants of the module - hopefully. It's hard to say for sure when you are using a dev version - by definition they are incomplete and are likely to have bugs and leave problems in your system.

As a side note, personally I don't use the jquery update module - after reading the number of threads it's cause problems for with people here on DO, it just doesn't seem worth the effort. I suppose if you are trying to integrate a library that requires a later version of jQuery, then I can see why updating would be appealing, but it may be better just to find a different script that will work with the default jquery version.