If you haven’t updated to 2.19 yet on your dev server, you might want to wait - we did the update and lost the LW toolbar on the back end, so no editing pages, etc.
Maybe some of you have already and didn’t have a problem?
Your mileage may vary of course, and I’m sure it will be fixed soon but just letting you know…
-= G =-
Thanks Gian Carlo!
It looks like a (working!) update to some core JS wasn’t properly calculated as a “cache-clearing” change in the upgrade for certain sites, so some prior JS that won’t work with the current version may be sticking around in some cases like this.
For the short-term, you can visit
/live/resource/js/core%5Cprivate.js/pages%5Cpages_editor.js
in your browser and add ?refresh=1 to force recache that core file:
/live/resource/js/core%5Cprivate.js/pages%5Cpages_editor.js?refresh=1
That seems to do the trick for any affected sites. I’ll check with the team to see what upgrade step was missed here—sorry for the inconvenience!—in terms of a less manual fix so other folks won’t have to worry about this. Thanks for bringing this to our attention!
Karl