Skip to main content

Brizy does not load in WP Staging

Ashley Hayden

One person on our team cannot edit pages or posts with Brizy in our WP Staging site. The below screenshot is what happens with no additional information as to what could happening or why. It does not happen to anyone else, it does not happen in the live site or any other website we manage with Brizy, and we all use the same login so it's not an account issue. It is only happening the WP Staging environment. We have also reached out to them and are posting here to cover our bases.

Here is everything we have tried:

- Different browsers
- Incognito/private mode
- Clearing cache and restarting browser
- Running all available updates and restarting computer
- Different computers
- Logging everyone else out and trying as the only login

Nothing works, no matter what. It is just this one person who has this issue in this one place.

 

0

Comments

6 comments

Date Votes
  • Ariel H.

    Hi Ashley,

    Thank you for keeping in touch.

    This is something we need to inspect from your WP Admin page.  Could you please add us as an Admin user to your WordPress Dashboard? Kindly send the following details to communitysupport@brizy.io:

    Community Post link: https://support.brizy.io/hc/en-us/community/posts/16863938276370
    WordPress Admin URL:
    Username:
    Password:

    In the meantime, please check your hosting panel to see if there's an option to temporarily disable ModSecurity. Sometimes, this can cause this error when attempting to edit a page. Additionally, since the URL has changed in the staging environment, you may want to try flushing the permalinks to see if it helps resolve the issue.
    https://wpastra.com/docs/how-to-refresh-wordpress-permalinks/

    Another helpful step that you can try is to optimize the database. You can follow the steps outlined in this guide:
    https://www.inmotionhosting.com/support/edu/wordpress/optimizing-your-wordpress-database-with-the-wp-optimize-plugin/

    Please try this and let me know how it goes.

    Best regards,
    Ariel H.

    0
  • Ashley Hayden

    Thank you, we have followed up via email from Sarah Denson sarah@weareregard.com with our license key to ensure the right account. WP Staging was able to find the error code information so that information was included; it is not a firewall or permalinks issue but a problem with a theme that was already deleted and no longer exists.

    0
  • KC George
    • Edited

    Hi Ashley,

    I was able to replicate the problem within your WordPress Dashboard. When attempting to edit a Brizy page I see the error "Something went wrong". Chrome DevTools showed that  Wordfence Security plugin was blocking admin-ajax.php request on your page. 

    To see if it would help, I disabled the Wordfence plugin, however it kept blocking the admin-ajax.php file. The plugin was still active and performing its intended function even though it had been deactivated.

    The email Sarah sent had a mention that the theme 'The Flavour Parent' had been removed. However, it still generates errors as WP Staging Support pointed out. The theme continues to generate errors even after being removed from your WordPress Dashboard, giving the impression that it is still in use.

    PHP Warning: Declaration of FW_Auto_Install_Upgrader_Skin::feedback($string) should be compatible with WP_Upgrader_Skin::feedback($feedback, ...$args) in /home1/thebrii1/public_html/wp-content/themes/theflavour-parent/theme-includes/includes/sub-includes/auto-setup/class-fw-auto-install.php on line 1882     

    Since the theme still generates errors after deletion and the plugin still working properly after deactivation, it's possible that the WordPress instance in your staging site has malfunctioned. You could try these to fix the issue

    • Delete the current staging environment and recreate staging using WP Staging in a different folder adhering to the recommended staging process, deactivate Wordfence Security plugin and check if the issue resolves
    • If this does not help, recreate staging using the Bluehost staging feature, deactivate Wordfence Security plugin and check if that resolves the issue.  

    Please see this screen recording for my test https://jmp.sh/AlxuSZKE

    0
  • Ashley Hayden
    • Edited

    Deleting the staging site and starting it over is not an option. All of the work to recreate a new site has already been completed and is already done within the staging environment.

    This problem was not happening for me - I have been editing and creating pages perfectly fine - it was just one person. But due to the testing, the error was also happening for me and I was locked out of editing anything. However I turned Wordfence off the live site and can edit pages again. 

    There is nothing we can do about this until the staging site is launched because we can't lose our work.

    0
  • KC George
    • Edited

    Hi Ashley,

    Moving it to production may not be a good option if you haven't finished the staging modifications. 

    Kindly ask these questions to your hosting company.

    • Even though Wordfence is disabled in your WordPress Dashboard, why is it still running on your website? (You will have to demonstrate that it is blocking the admin-ajax.php)
    • Why is 'The Flavour Parent' theme active on your staging site when it is not installed?

    If they can investigate the cause behind this behavior, hopefully you can deactivate Wordfence and the theme and make the final changes on the staging site before redeploying the modifications to production

    0
  • Ashley Hayden
    • Edited

    Sorry I edited my last reply again but you had already responded. I turned Wordfence off the live site and can edit pages again. There is nothing we can do about this until the staging site is launched because we can't lose our work. 

    Thank you for your time. 

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

Ask a Question