Title: Extensions Error
Last modified: November 10, 2017

---

# Extensions Error

 *  Resolved [Donna Fontenot](https://wordpress.org/support/users/cavalierlife/)
 * (@cavalierlife)
 * [8 years, 7 months ago](https://wordpress.org/support/topic/extensions-error/)
 * Whenever I try to go to the Extensions in admin, I get only this:
 * “Options have been altered outside of this plugin’s scope. This is not allowed
   for security reasons. Please deactivate your account and try again.”
 * I’ve deleted both the seo framework plugin and the extensions manager and reinstalled,
   both from wordpress.org repo and from downloaded files through my premium account
   on theseoframework.com. I even removed the site from the list of activated sites,
   which was what I assumed “please deactivate your account” meant. None of that
   helped. I still get that message. And I don’t know how/where to reactivate the
   site in my account.
 * I have not altered options in any way outside of the plugin. Haven’t even looked
   at the options in quite a while.

Viewing 9 replies - 1 through 9 (of 9 total)

 *  Plugin Author [Sybre Waaijer](https://wordpress.org/support/users/cybr/)
 * (@cybr)
 * [8 years, 7 months ago](https://wordpress.org/support/topic/extensions-error/#post-9672107)
 * Hi [@cavalierlife](https://wordpress.org/support/users/cavalierlife/),
 * I speculate that this might be an issue with the PHP installation. e.g. Floating
   point errors.
    Nevertheless, the plugin verifies its settings so no unsolicited
   API connections can be made.
 * With “Deactivate account” it means the “Deactivate Account” button found in the“
   Account and Actions” box on its WordPress settings page. I’ll see if I can improve
   the semantics in an upcoming update.
 * ![Account and Actions](https://i0.wp.com/i.imgur.com/M6j7782.png?ssl=1)
 * When you click on that button, it will ask you if you’re sure: click it again
   after it turns red.
    Then it will try to disconnect your site (if it’s connected)
   and it will remove all activation settings. All extension options (if any) are
   held intact.
 * Then, you should see the activation page. Follow the steps provided there (enter
   a key or go free) and you should be able to activate the extensions again.
 * If the deactivation button doesn’t work or isn’t visible, let me know!
 *  Thread Starter [Donna Fontenot](https://wordpress.org/support/users/cavalierlife/)
 * (@cavalierlife)
 * [8 years, 7 months ago](https://wordpress.org/support/topic/extensions-error/#post-9674826)
 * I do not have an Account and Actions area, nor do I have a Deactivate button.
   None of this exists for me.
 *  Plugin Author [Sybre Waaijer](https://wordpress.org/support/users/cybr/)
 * (@cybr)
 * [8 years, 7 months ago](https://wordpress.org/support/topic/extensions-error/#post-9677079)
 * Hi [@cavalierlife](https://wordpress.org/support/users/cavalierlife/),
 * It’s a bummer to hear you’re still encountering issues. I’m wondering what screen
   you’re seeing, as you can’t view those settings. Could you send me a screenshot
   of it when you find the time?
 * In any case, I created a little plugin for you that should get you out of this
   issue instantly.
 * > [View it here](https://gist.github.com/sybrew/c9a9e8b0900f36cf597210372e53c75d).
   
   > [Download it here](https://gist.github.com/sybrew/c9a9e8b0900f36cf597210372e53c75d/archive/a97611587f94c9feb8541ffb122bab1f6e1f831c.zip).
 * Usage:
    1. Download the plugin ZIP folder above.
    2. Open ZIP contents, and store file `reset-tsfem.php` somewhere on your computer.
    3. Connect to your site using FTP.
    4. Upload `reset-tsfem.php` to `../wp-content/plugins/`
    5. Activate the plugin “Reset TSFEM activation settings”.
 * After that, you can simply delete the plugin through the WordPress plugin management
   interface.
 * If even that doesn’t let you reactivate the plugin once more, then please [contact me privately](https://premium.theseoframework.com/support/)
   with a link to your site and I’ll see what I can do from there.
 *  Thread Starter [Donna Fontenot](https://wordpress.org/support/users/cavalierlife/)
 * (@cavalierlife)
 * [8 years, 7 months ago](https://wordpress.org/support/topic/extensions-error/#post-9677847)
 * That worked! Now I see all those things. That entire page was being replaced 
   by the error, but once I activated the above plugin, it was all there again. 
   Thank you!!
 *  [insiderperks](https://wordpress.org/support/users/insiderperks/)
 * (@insiderperks)
 * [8 years, 6 months ago](https://wordpress.org/support/topic/extensions-error/#post-9760063)
 * I also ran into this issue and the plugin above resolved it. It would be nice
   to know what we did, though, to cause it. Just so we can avoid it in the future?
 *  Plugin Author [Sybre Waaijer](https://wordpress.org/support/users/cybr/)
 * (@cybr)
 * [8 years, 6 months ago](https://wordpress.org/support/topic/extensions-error/#post-9761065)
 * Hi [@insiderperks](https://wordpress.org/support/users/insiderperks/),
 * This happens after moving sites, so where the `wp-config.php` salts or the domain
   differs. If any of those change, the integrity checks will fail as those variables
   are used as keys for its hashing.
 * A popular use-case for this is WP Engine’s staging environment.
    Another would
   be using ServerPilot, where the home option is dynamic (which is bad).
 *  [insiderperks](https://wordpress.org/support/users/insiderperks/)
 * (@insiderperks)
 * [8 years, 6 months ago](https://wordpress.org/support/topic/extensions-error/#post-9761215)
 * So a question then. What if we regularly change our salts for security purposes?
    -  This reply was modified 8 years, 6 months ago by [insiderperks](https://wordpress.org/support/users/insiderperks/).
 *  Plugin Author [Sybre Waaijer](https://wordpress.org/support/users/cybr/)
 * (@cybr)
 * [8 years, 6 months ago](https://wordpress.org/support/topic/extensions-error/#post-9761637)
 * Hi [@insiderperks](https://wordpress.org/support/users/insiderperks/),
 * I don’t see a reason why you would. The salts are there to prevent rainbow table
   lookups for when your database gets hijacked, there’s nothing much more to that.
   Changing them would mean that every user needs to update the password too. Even
   when the salts become public, or even when your database is exposed, there’s 
   little concern as it’ll take many years before a password is cracked. Many magnitudes
   of order more so if both are securely obscure.
 * Take the above with a grain of salt, as not every WordPress installation uses
   secure-enough password storage. It’s always good to change your password every
   so often. Also, changing the salts and keys after they become exposed is a good
   practice too.
 * Regardless of the above, I did test it out before releasing TSFEM version 1.0.0,
   and at that moment I knew the “Deactivate” button would pertain effectiveness.
   Why and whether that has changed is yet to be determined, as I laid focus on 
   the 3.0 version release of TSF last month.
 * The gist is that when the integrity of the settings can’t be verified, only the
   API activation and activated extension settings will be rendered inefficacious.
   All other settings–like your department settings in Local SEO–shouldn’t be affected.
   So, there’s little harm done when moving sites and/or having to change salts 
   and keys.
 * When that happens, those settings need to be reset. This can be manually done
   with the deactivation button. The little plugin I shared above does exactly what
   the deactivation button should do, and I might have to implement it better in
   TSFEM when this happens. More on this will follow as I learn more.
 *  Plugin Author [Sybre Waaijer](https://wordpress.org/support/users/cybr/)
 * (@cybr)
 * [8 years, 5 months ago](https://wordpress.org/support/topic/extensions-error/#post-9847894)
 * Quick update: In the upcoming version (1.5) this issue will [no longer cause a block-out](https://github.com/sybrew/The-SEO-Framework-Extension-Manager/commit/9562cdaa25bdcb113a30226056ec8e4fceb49c5c)
   from the overview page.
 * There’s still a lot to be done, so I can’t promise an ETA.

Viewing 9 replies - 1 through 9 (of 9 total)

The topic ‘Extensions Error’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/the-seo-framework-extension-manager_2e363c.
   svg)
 * [The SEO Framework - Extension Manager](https://wordpress.org/plugins/the-seo-framework-extension-manager/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/the-seo-framework-extension-manager/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/the-seo-framework-extension-manager/)
 * [Active Topics](https://wordpress.org/support/plugin/the-seo-framework-extension-manager/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/the-seo-framework-extension-manager/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/the-seo-framework-extension-manager/reviews/)

 * 9 replies
 * 3 participants
 * Last reply from: [Sybre Waaijer](https://wordpress.org/support/users/cybr/)
 * Last activity: [8 years, 5 months ago](https://wordpress.org/support/topic/extensions-error/#post-9847894)
 * Status: resolved