• Ceecee

    (@edicodesign)


    followed the instructions to create a service account, added the snippet at the top of my wp-config and logged out to make sure the absolute path was correct. On the plug-in setup page, the snippet was recognized but it kep showing this Settings Locked- someone else has changed settings. Refresh the page. Kept refreshing and it would load for a moment , then show this Settings Locked toast notification. I then opted to try the “store key in db” option with the same results. There was no one else working on the site or changing any settings and I checked the google cloud console to make sure all my same settings were being applied as when I initialized it. Got too frustrated so deleted the plug-in (which I then had to go through and clean up the table it created in the db as well as some rows in other tables it had left).

    any ideas what is going wrong if the key file is correct, the snippet in wp-config is correct, and when using the en storage option, the JSON key is correct ?

Viewing 1 replies (of 1 total)
  • Plugin Support Delicious Brains Support

    (@dbisupport)

    Hi there,

    WP Offload Media Support Team here, Thanks for reaching out with your query we would be happy to assist.

    That error usually means that somebody else is making changes to WP Offload Media at the moment but if it’s been like that for a while or no one else is working on the site then another possibility is that the REST API results are being cached somehow.

    The warning may also be displayed if there’s a problem with the REST API itself. One such problem can be that the requests to the REST API are cached and the data returned is outdated.

    One of our customers was able to resolve this by disabling their cache plugin. If you have one or something similar installed, it may be worth trying that as well. Another thing to try when you have a caching plugin/tool is to disable caching for REST API or for admin users.

    You could also check your Site Health and check if REST API is passing.

    If the issue persists, we would suggest checking your browser’s debugging console to see if there are any errors reported when this occurs. For instructions on how to do this, see?https://deliciousbrains.com/wp-migrate-db-pro/doc/debugging-browser-console-errors/.

    Also, please send us the debugging information from the Support tab on the site you’re having trouble with.

    1. Go to the Support tab of your install
    2. Scroll down to the “Diagnostic Info & Error Log”
    3. Please copy the info and share it here, or provide the URL if you upload the info on a site

    Please feel free to hide any sensitive info you might find there. We’d like to check your current site’s configuration, maybe there’s a configuration and/or plugin that could be causing this.

    We look forward to hearing back.

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