• Resolved Sean

    (@sean-h)


    Hi there,

    I have since fixed the problem, so this is just a suggestion.

    Can you maybe set any red warning banners that slide out to stay out a lot longer, or until manually dismissed? They do show useful information, but less than 2 seconds isn’t enough time to read it ??

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Tsvetan Mitev

    (@tsvetanm)

    Hello @sean-h,

    Thank you for your feedback.

    I have brought your suggestion to our Developers.

    If any changes are made on the notification screen time, we will make sure to included in the changelog.

    Best Regards,
    Tsvetan Mitev

    Thread Starter Sean

    (@sean-h)

    Hi @tsvetanm,

    In case you are wondering, the problem was caused by Wordfence, only WF is no longer installed on the staging site that was having this problem, even though I removed all traces of it, including the database tables.

    After contacting WF support, they suggested I create a .user.ini file in the public_html folder of the staging site and add the following line to it: auto_prepend_file = none They went on to say that it was because I removed WF from the staging site that I experienced this problem. For some reason, WF on the main site was ‘seeing’ what I was doing on the staging site and blocking me, on the staging site, in more ways than just this one instance.

    I removed WF from the staging site because it is the Premium version which complains about being used on another site. I also don’t think I need it on a staging site because I always password protect my staging sites, and this particular staging site is only for testing and won’t be pushed back live.

    Plugin Support Tsvetan Mitev

    (@tsvetanm)

    Thank you for the update, @sean-h.

    I suspect that the WordFence configuration of the main website was also copied to the staging site, which caused the problem here.

    Our staging environment creates a copy of the live website to a staging subdomain, but in some cases it’s a good idea to exclude some of the non core WordPress files which are directly related to the configuration of the live website:
    https://www.siteground.com/tutorials/staging/create-staging/#Choose_what_to_be_included_in_the_Staging_copy

    It’s a good idea to also disable or re-configure any plugins on the staging copy which are domain dependent.

    If you experience any issues with the our staging tool in the future, feel free to contact us via the Help Desk center of your Client Area and we will be happy to assist you.

    Best Regards,
    Tsvetan Mitev

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Red warning banner – REST API’ is closed to new replies.