Hi Carson,
Thank you for the reminder. I’ve actually been waiting to receive the email – turns out Gmail put it in my spam folder for some reason.
I’ve logged into your site and manually upgraded the database table. Unfortunately, any previous scope information has been lost, so you will either need to go manually restore it, or use an export file.
I’m really sorry that this happened – it’s very puzzling why the upgrade process didn’t run correctly.
For anyone else who might need to upgrade their database manually for the 2.10.0 update, here’s the SQL I used:
ALTER TABLE wp_snippets CHANGE scope scope VARCHAR(15) NOT NULL DEFAULT 'global';
UPDATE wp_snippets SET scope = 'global' WHERE scope = 0;
UPDATE wp_snippets SET scope = 'admin' WHERE scope = 1;
UPDATE wp_snippets SET scope = 'front-end' WHERE scope = 2;
If you’re using a non-standard prefix, you’ll need to replace wp_
with the prefix.
After Shea’s been doing the manual data base update as mentioned above and me bringing back my snippets to the right scopes, I can confirm that the issue was related to old data base structure.
Everything works as expected again.
Thanks for your outstanding support, Shea!!!
HINT: Before adjusting your script scopes, you should activate SAFE MODE via wp-config.php. Depending on the kind of scripts, the global scope of all scripts might break your site or – like in my case – the WP backend.
-
This reply was modified 6 years, 2 months ago by justyumyum.
Thank you for confirming @justyumyum. Once again, I’m sorry that this mess up happened in the first place – it’s annoying when something doesn’t work when it should. Glad that we could sort this out