• Resolved allstarsft

    (@allstarsft)


    Hi,

    I always have this issue when I staged the Production site for testing. Then Super Cache for Cloudflare would face issues. Just today, I tried to deactivate Super Cache, at the Staged site — but it also reflected as deactivated in the Production site. And When I get it activated back at the Main site, want to Enable — it showed Successful — but its still Red indicated — Usually if its successful, it would have been in Green.

    Currently I am getting lost and confused, as both sites will start to confuse me with changed Site Title. I had this title : Staged site for owp-s1.allstars.com.sg, but it appeared at my Production site allstars.com.sg.. And there are other instances of other issues doing this.

    What is the best practice in this case? When using your Super Cache for Cloudflare plugin? Do I keep your plugin working / Enabled on both sites? My Cloudflare only has this DNS configured — see screenshot https://snipboard.io/hYLiOJ.jpg

    Currently I am trying to solve a Add To Cart button — Redirecting to Home Page issue so I cloned / staged to a new site for testing. Then the above problems arise.

    Now I have both sites with the Cache Plugin Enabled (Green indicator).

    Thanks.

    • This topic was modified 6 months ago by allstarsft.
    • This topic was modified 6 months ago by allstarsft.
Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Contributor iSaumya

    (@isaumya)

    Hi,
    I’m sorry but I did not understand your problem clearly. Disabling cache in the staging site or even deactivating the plugin on staging site should not cause any issues on the live site.

    Thread Starter allstarsft

    (@allstarsft)

    Right after cloning or staging the site, the staged / clone site will have its settings or plugins behaviour duplicated across – -somehow. And this caused problems to the Production site — like If I deactivate your plugin at staged/cloned site, the production site will have it deactivated as well .

    Initially I log in from Staged site (WP-admin), instead of going into the Admin backend of the Staged site, it went into the Production site backend instead.

    So am wondering what is the best practice for cloning or staging websites with Super Cache for Cloudflare in use at Production site? Apparently, after staging/cloning the site, I had to also include the url links in wp-config.php — and this work for some time. Now its stable.

    define('WP_HOME','https://owp-s1.allstars.com.sg');
    define('WP_SITEURL','https://owp-s1.allstars.com.sg');

    owp-s1 being the staged site. And I also had to do this to the Production site’s wp-config.php.

    Do I keep your plugin activated in the staged site?

    Thanks.

    • This reply was modified 6 months ago by allstarsft.
    Plugin Contributor iSaumya

    (@isaumya)

    Don’t see any reason for this to happen unless the staging and live site both share the exact same database.

    Thread Starter allstarsft

    (@allstarsft)

    Which in the first place it was wierd. They do not share the same DB. But this happened when I just did the staging/cloning.. After adding the urls coding into the respective wp-config.php, it seems fine now. (Otherwise things are haywired…. OceanWP verification system going haywire — keep asking me if this or that site is long term duplicate or ? … , and other wierd stuff happening that time)

    So Do I keep your plugin enabled on the staged/cloned site?

    Why do I keep asking this question was because, I had the impression that Cloudflare is only for the production site — allstars.com.sg — staging sites with subdomains are not included. So I thought to disable would be better.

    • This reply was modified 5 months, 3 weeks ago by allstarsft.
    • This reply was modified 5 months, 3 weeks ago by allstarsft.
    Plugin Contributor iSaumya

    (@isaumya)

    Do I keep your plugin enabled on the staged/cloned site?

    You can, but it doesn’t do anything on the staging site and it also don’t serve any purpose there unless you are caching the staging site which is odd.

    Thread Starter allstarsft

    (@allstarsft)

    Ok, so my impression is correct that Cloudflare only caches the Production site. SO by right, I should deactivate your plugin…. But now I am abit afraid to do that… due to the earlier issues of duplication of the instances. Now at Staging site, your plugin’s Status indicator is Green.

    Plugin Contributor iSaumya

    (@isaumya)

    You can just disable the cache inside the plugin settings page inside the staging site. That would be way easier than deactivating the plugin itself.

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