License issue when pushing from staging to live

  • ceceet

    (@ceceet)


    1 month ago

    Hi friends,

    I didn’t include a site link because this seems to be a problem on every website that I use The SEO Framework on.

    I host sites using Cloudways, which offering staging sites for any live site that users have.

    As a result, I have a separate server on Cloudways for staging and one for production. Whenever I push changes from the staging site to live site, the license key for The SEO Framework stops working. I have to disconnect, reconnect, and reactivate extensions each time. This also happens if I pull a copy from a live site to a staging site.

    Is there any work around with this? I always activate on both the staging and the live sites, but that doesn’t resolve the issue for whatever reason. It’s a minor thing, it just gets a little redundant to do every time I make site changes on a staging that need pushed to a live site.

    Thanks for any help!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Sybre Waaijer

    (@cybr)

    1 month ago

    Hello!

    To mods: Since this issue affects both paid and free accounts, I think I can answer freely here.

    A workaround for reactivating extensions (where they stay active between account migrations) will be provided in the next update, but this functionality may be pushed to a later date.

    To workaround the API instance integrity issue, you could “downgrade” to instance version 1.0 or 2.0 by adding a constant to wp-config.php. Then, the instance should remain valid between the sites.

    Here’s the constant, and it will start working after deactivating the account — in this example, we set it to instance version “1.0”; the caveat is that the AUTH_KEY and AUTH_SALT in wp-config.php must be the same on your public and staging site.

    /**
 * This forces the plugin option verification instance version, which prevents users 
 * from sharing API information between sites.
 * This will only affect the version when the site hasn't been activated yet.
 *
 * @since 2.6.2
 * @param string The instance version to use.
 *               '1.0' relies on wp-config.php's AUTH_KEY and AUTH_SALT values.
 *               '2.0' relies on Extension Manager's folder location.
 *               '3.0' relies on the site URL.
 */
define( 'TSF_EXTENSION_MANAGER_INSTANCE_VERSION', '1.0' );

    Alternatively, you could exclude the instance settings from migrating. This way, both sites can maintain their own separate connection. However, this might be a bit involved, and I’m not sure if Cloudways even supports that.

    Thread Starter ceceet

    (@ceceet)

    1 month ago

    Thanks for such a detailed response!

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.