• Resolved Matta Cib

    (@matta-cib)


    Hello,
    How can I ensure that changes made on a production page are transferred to the corresponding staging page, or that a newly created production page is recognised and saved as a staging page in an existing staging site? Do I always have to create whole new staging sites? Or is there a sync button somewhere? In my test, a change made to an existing production page was not automatically transferred to the corresponding staging page. I couldn’t find anything about this in the FAQ. Thank you.

    The page I need help with: [log in to see the link]

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Contributor fayyazfayzi

    (@fayyazfayzi)

    Hi @matta-cib ,

    WP Staging does not auto-sync changes from production to staging. A staging site is a clone taken at creation time and stays isolated by design.

    If you change or create pages on the live site, you need to update the staging site to reflect those changes. You don’t always need a brand-new staging site, but updating one will overwrite its current state.

    There is no auto-sync button for safety reasons. Pushing changes works only from staging to production, not the other way around.

    Let me know your workflow and I’ll guide you on the best approach.

    Cheers!
    Fayyaz

    Thread Starter Matta Cib

    (@matta-cib)

    Hello @fayyaz ,

    Thank you for your reply, which was really helpful. I hadn’t found the page about synchronisation.
    As a newbie, may I ask two more questions?

    1) I would like to try out a plugin on the staging site, but the plugin’s functionality only affects visitors who are not logged in. And so, for testing purposes, I would need to be able to access the staging site as a normal visitor. This does not seem to be possible, as I cannot access the staging site as a visitor who is not logged in, but only as an admin. So testing doesn’t work in this case. Is that correct, or have I overlooked something?

    2) After installing the WP Staging plugin yesterday, I received a notification this morning from the ‘Broken Link Checker’ plugin about over 200 broken links. These all seem to relate to the new staging site. In ‘Broken Link Checker’, it does not seem to be possible to restrict the area to be scanned, so the question is whether it is possible to make the staging site invisible, so that it is not detected by plugins such as ‘Broken Link Checker’? I should add that I have installed WP Staging in a subfolder (xyz/staging/. The option of installing as a subdirectory (staging.xyz), which is probably only available in the Pro version, would possibly hide the staging site from ‘Broken Link Checker’…

    Many thanks and best regards
    Matta

    Plugin Contributor alaasalama

    (@alaasalama)

    Hi Matta!

    1. You can log into the staging site, then go to (WP STAGING > Settings) and enable this option “Disable admin authorization”, then you should be able to see the staging site without logging in.
    2. Maybe the “Broken Link Checker” support team can help you better here, I read their documentation quickly, and looks like their only way to exclude is per different domain, so yes, creating the staging site on a subdomain would work, but maybe they have another idea for you.

    Thanks,
    Alaa

    Thread Starter Matta Cib

    (@matta-cib)

    Hello @alaasalama ,

    thanks for your replay.

    I assume you are referring to the issue of how normal visitors can view the staging site, specifically the following feature located on the right-hand side of the settings page. It says something like this (translated into English)
    “Access permissions
    Select the user role you want to grant access to the staging site. […]”
    The problem: this is an option that is only available to users of the Pro version…
    By the way, this morning, 827 broken links were reported…

    Thank you and kind regards
    Matta

    Plugin Contributor alaasalama

    (@alaasalama)

    Hi Matta!
    No, I mean this one “Disable admin authorization”, here’s a screenshot: https://cln.sh/zzP1zfdJ

    Thread Starter Matta Cib

    (@matta-cib)

    Hello @alaasalama , thanks again for your replay.

    I had already tried this setting, but it doesn’t work: When I first activate the feature in the settings on the production site and then open the page https://xyz.de/staging/?p=57493 in incognito mode in another browser, for example, I have to log in with my email address and password. Once I have done that, I am logged in as an admin on the staging site. This means that simply activating the feature on the production site does not seem to allow me to visit the page as a normal visitor. And even if I then activate the ‘Disable admin authorisation’ option in the settings again, this time on the staging site, I unfortunately remain an admin and do not become a normal visitor. This can be seen firstly by the fact that after switching to the staging site p=57493, I am still greeted with ‘Welcome Matta’ in the top right-hand corner, and secondly by the fact that I can still use the features on the site that are not normally available to visitors who are not logged in. Somehow, I cannot get into ‘normal visitor mode’.

    Kind regards
    Matta

    Plugin Contributor alaasalama

    (@alaasalama)

    Hi Matta!

    The settings must be changed on the staging site. And your user won’t be converted to a normal user, but the staging site should be seen by any user instead of showing the login form of WP STAGING plugin.

    For example, I visited the staging site and I can see it, without logging in: https://cln.sh/VxVY42sj that means the option works.

    Thread Starter Matta Cib

    (@matta-cib)

    Hello @alaasalama ,

    Thanks again for your help. And you’re probably right: it works as you described, at least in private mode in Chrome, Edge and Opera. Unfortunately not with Firefox, with which I stupidly tested it … 🙁
    When I

    • delete the Rocket cache in my default browser, Vivaldi
    • switch to Firefox (146.0.1 on Ubuntu) and close all windows
    • delete the entire browser cache in Firefox
    • switch to private mode in Firefox
    • open a staging page in private mode in Firefox
      then, for whatever reason, I am greeted with an orange bar as an admin.
      Strange, but at least I’ve now figured out that it’s an isolated phenomenon and in other browsers it works. Thank you!
Viewing 8 replies - 1 through 8 (of 8 total)

You must be logged in to reply to this topic.