Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
I'd like to request temporary access (wp-admin and FTP) to the website to investigate the issue further.
You'll find the necessary fields below the comment section if you log in to leave the next reply. The information you provide will be private, meaning only you and I can see and access it.
IMPORTANT
Please be sure to create a backup of the website and database before granting us access.
If you don't see the "wp-admin / FTP" fields, your login credentials for the post and website will be set to "PUBLIC." Do NOT publish the data unless you see the required wp-admin / FTP fields.
I may need to install a plugin called "All In One WP Migration" to create a copy of the website on which I can investigate the problem more thoroughly.
I would also be very grateful if you could provide a staging site on your server for this purpose. As I mentioned earlier, this issue seems to be related to SiteGround hosting and might not be replicable on a virtual server, but I will be glad to give this a test as confirmation.
If you have any questions about creating such a staging site, please contact your hosting provider. Please ensure that WPML is also registered on this staging site at https://wpml.org/de/account/websites/.
If you are unable to provide such a copy of the website for testing, please let me know on this ticket.
The private reply form looks like this:
hidden link
When replying again, click "I still need assistance".
Video: hidden link
Please note that we are required to request this information individually on each ticket. We are not permitted to access any login information that was not specifically provided in the private reply form for this ticket.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
On a local copy of your site, this issue does not occur. It further does not occur on your site when using a new image file.
This seems to be related to a CDN, as I see your existing media uses the tag:
"Connected media".
Is this CDN managed by SiteGround?
---
Could you please consult the SiteGround Support and ask them for assistance in setting up a staging site for us for testing?
The private reply form is enabled again.
Please also inform them about the following error:
Uncaught TypeError: Cannot read properties of null (reading 'image_optimizer_metadata')
at translatedValOrBlank (media-translation-popup.js?ver=3.0.0:362:60)
at media-translation-popup.js?ver=3.0.0:376:62
at Array.forEach (<anonymous>)
at updateDialogFormFields (media-translation-popup.js?ver=3.0.0:359:33)
at HTMLAnchorElement.<anonymous> (media-translation-popup.js?ver=3.0.0:260:3)
at HTMLAnchorElement.dispatch (load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,wp-hooks&ver=6.8.3:2:40035)
at v.handle (load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,wp-hooks&ver=6.8.3:2:38006)
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
My apologies, honestly, I have never seen this tag before, and this tag seems not to be connected to the fact of whether media is attached to a post in the media library.
I am asking my colleagues if they may have more background.
---
I realized that there is a custom field called "siteground_optimizer_compression_level" and you have set it to "Translate".
This kind of matches up with the error that reports an issue about reading 'image_optimizer_metadata'.
Please revise WPML > Settings and kindly note that not all custom fields or custom term meta should always be set to "Translate". You should only set such settings to translate if the field includes a value that needs to appear on the WPML Translation Editor.
Avoid adjusting settings for fields where you are unsure about which data they are handling. In doubt, always use "Not translate".
Further, the issue no longer occurs on your site when uploading a new image. Can you please confirm?
POINT 1:
I CONFIRM that a new media upload is accessible to Translate.
The problem usually happens when I use REPLACE MEDIA a few times within my Media Library. (since I need to replace media that have been corrected or updated).
Essentially this UPDATE seems to be the root cause and since a website NEEDS updates, it will be a problem to always ensure errors and having to reupload files and readjust templates and page containers.
POINT 2:
Since I am not very familiar with the correct settings for most of my plug-ins, I may have activated a few unnecessary ones.
Can you please direct me into the ones that I need to deactivate into DONOT TRANSLATE?
More specific directions with images snapshots would help me.
I feel I will do more harm to my website WITHOUT visual assistance.
Would that be feasible for you?
POINT 3:
Regarding the CDN from yesterday's comments, do you need me to do anything on the regard (i.e. contact SiteGround with specific questions that you could provide me with?
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
One of my colleagues confirmed that the tag on WPML > Media Translation was added in the latest version of WPML - it seems not to be connected to the issue.
The problem might be that you are replacing existing media using the plugin Enable Media Replace, and after that, WPML needs to sync the media again.
This means that WPML created one entry per language for each media file inside the media library. Once you replace the original media file, it breaks the connection to the already synced media. You can see this if you go to the Media Library and switch the language inside the admin bar.
If you run into this problem again, sync the media at WPML > Settings > Media Translation, and it should solve the issue.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Indeed, adjusting those settings is recommended, but it might not be related to the reported issue.
On the staging, I went to WPML > Settings > Custom Fields Translation and inside the text search field, I entered "siteground".
I suggest you further go through the entire list of custom fields and only set such a field to "Translate" for which you are aware that they actually include data that needs to be translated on the WPML Translation Editor.
If you set fields that do not require a translation to "Translate," it can cause unexpected issues.
I will now set up a new test site and try to replicate this issue so that we can take further internal steps. As I said, the author seems to be aware of the issue according to their support forum on wordpress.org but I will run another test to confirm if this is replicable on a new WordPress install.
