Using SG Optimizer on Staging Site

  • Resolved confusedneedhelp

    (@confusedneedhelp)


    2 years, 7 months ago

    Hi,

    I get the following error when using your plugin on a staging site.

    COULD NOT CONNECT TO THE WORDPRESS REST API

    I have deactivated all other plugins and the problem still remains.

    None of the caching controls work.

    The main issue is that I cannot stop dynamic caching without the plugin which has an impact on what I can and can’t test.

    It seems that even URLs with parameters are cached in dynamic caching. Is this right?

    Is there any advice for disabling dynamic cache on a staging site.

    Thanks for your help.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Plamen M

    (@plamenm)

    Hello @confusedneedhelp,

    Thank you for using our plugins. The SiteGround Optimizer is not meant to work in the Staging environment. The plugin is mean to cache and speed up a live site with a lot of access to it. A staging site is meant for development and making regular changes to it and is also used by 1 or several people maximum. This is against the purpose of the Optimizer plugin.

    Install the SiteGround Optimizer plugin after you push your staging site to live. Then you should no experience the reported issue.

    Regards,
    Plamen.M
    SiteGround.com

    Thread Starter confusedneedhelp

    (@confusedneedhelp)

    Thanks for the quick reply.

    I completely understand your answer.

    However, it seems that dynamic caching is set on and cannot be turned off unless the plugin works. So I think that I am getting dynamic caching on my staging site and I don’t want it. But there is nothing I can do to turn it off.

    Do you understand me?

    Plugin Support Plamen M

    (@plamenm)

    Staging sites are not being cached by our server level caching. You can test this by checking the headers of the site:

    curl -I -X GET https://Website-Address.TLD

    and then you should look for the x-proxy-cache header. It should read “MISS”, which is an indication of a not-cached content. If the option is “HIT”, this means that the content is being cached:

    x-proxy-cache: MISS

    Give this test a try and post a support ticket if the result is “HIT” on your staging site.

    Regards,
    Plamen.M
    SiteGround.com

    Thread Starter confusedneedhelp

    (@confusedneedhelp)

    Ok, thanks for confirming that. It is helpful to know that dynamic caching should not be enabled.

    I will try and test and come back if there is a problem.

    Cheers ??

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Using SG Optimizer on Staging Site’ is closed to new replies.