Hi @berkmh,
This should only happen when the plugin’s upgrader is still upgrading in the background. We’ve added this check to prevent conflicts with the settings.
Are you able to access it yet?
If not, try hovering over the magnifying glass. You should see a link appearing at the bottom left of your browser, to:
.../wp-admin/admin.php?page=theseoframework-settings
Is this the case?
Hi Sybre,
I’m also experiencing the same issue : the magnifying icon and the setting link point to /wp-admin/admin.php?page=theseoframework-settings but when you click it, you’re redirected to the dashboard ( /wp-admin/ ).
HTH
Thanks for the feedback, Matt!
After a thorough investigation, I think another plugin might fiddle with the WordPress-options filter, making a strict update check fail–locking out the SEO settings page.
Nothing else in the v3.1 upgrade has changed that could invoke this behavior.
Could you help me figure out what might cause this, by performing the steps below?
- Install the Health Check & Troubleshooting plugin, it should be featured in your dashboard.
- Go to Dashboard -> Health Check -> Debug Information
- Hit “Show copy and paste field”, and copy the contents.
- Send the copied content to me, confidentially, via my contact page.
I think I’ll be able to find a cause and supply a resolution with this information.
Thanks!
Hi @skyminds,
I received the list. Thanks! I’ll try to triangulate it with other users facing the same issue; the plugin list is a bit too large for debugging.
Did you update to TSF v3.1.0 earlier, that crashed your website as you’re using Divi?
If so, could you try updating one line in /wp-content/plugins/autodescription/autodescription.php?
This is the line that needs changing (line 65):
define( 'THE_SEO_FRAMEWORK_DB_VERSION', '3103' );
Change it to:
define( 'THE_SEO_FRAMEWORK_DB_VERSION', '3104' );
This will force the upgrader to run again and complete itself; which might resolve the issue after one load.
Cheers 🙂
Hi Sybre,
That did the trick and I now have access to the SEO settings page 🙂
Thank you,
Matt
Great! Thanks 🙂 I’ll see if I can figure out why this would’ve failed without the change, and run the upgrader for everyone in the next update.
I think I’ve found the issue (loose vs strict checks), and it should be fixed as of 3.1.2. Thanks for the feedback!
You’re welcome Sybre – thank you for your great work !
Quick update: This seems to be an object/option caching issue, and it still persists as of 3.1.2/3.1.3.
If you experience this behavior (again), you might wish to flush these (or all) caches.
