We are still working on this as it's only happening on the live environment, once there are news we will update here.
If possible, please re share the access details to the live environment please as they ones we have no longer work and we need to take a new copy to continue working on this.
I can completely understand, however, there are a few things at hand.
The ticket was closed due to inactivity, our team was actively working on this issue and when we received no feedback the ticket was automatically closed 3 months ago.
Where we left off we were awaiting for permission from your side for our team to move forward with a fix. The given credentials did not work and the issue was never reproduced on a staging site.
I am enabling the private reply again, if possible, please share the access details as they have been removed.
We have set things up on the website to track changes to the astra-settings options, what it does is that the moment a change is done it records content to the debug.log, this will help trace when an unwanted change occurs.
Please keep an eye out for when it goes wrong, at which time we can inspect the log and see if it shows what caused it to change.
In summary we:
added an mu-plugin
activated the debug.log
also added the Adminer plugin so we can inspect the options table
Awaiting your reply so we can track the change to a specific time stamp and find it in the debug.log now.
You can delete all translated strings... Modify back the English default ones to the standard English text... then bulk translate them one more time to all languages... it should trigger the issue
Being that most of the strings have been turned to Spanish, we can of course switch them but I cannot guarantee that the translation back to English will be exactly what is desired which is why it's best if this was done from your side especially since this is a live site.
if you rather us do this, and dont mind if the English strings are not 100% what you would add, then we can proceed.
Also another thing to note is that the issue has not been able to be triggered upon demand which is why we have set up the tracking plugin on your site.