Follow up to WPML string translations and cornerstone issue

Support
#1

this is a followup to: WPML String Translation and Cornerstone

I finally managed to set up a staging site and fix the “number of files” issue.

How ever, even I essentially mirrored the site, I can’t reproduce the issue on the staging site.

RECAP: If I activate wpml string translations on the live site, I can’t edit pages in cornerstone due the “iframe error blah blah…”. Decativating this plugin - all’s roger. As said: this works on the staging site just fine, so I’m kinda “wt#”, duh…

#2

You will need to enable debugging on that site. I would reach out to WPML too see if they have a clue on the issue.

#3

pls see secure note

#5

I would reach out to WPML if this issue occurs when the string translation plugin is enabled. You are getting an error on certain pages even when not using Cornerstone. I’ll send more info in the secure note.

#6

That is odd. I don’t see the 500 error at all. To see this specific page, you have to be logged in anyway. Admins see all pages by default.

#7

Hey @VRANKOVINA,

The login credentials you provided are not working.

image
image900×458 12.7 KB

#8

here they do. jeeeeeeeeeeez… there should not be any restriction based on IP active. Not to my knowledge.
What’s the IP you try to log in?

#9

Hey @VRANKOVINA,

Both sites you shared are down.

#10

I’m sorry, but I have no clue what’s going on at your end. Here everything is just perfect.

EDIT: My security plugin says the site was down. Timestamp: Feb. 8th, 2026, 2:28 AM GMT-1. Looks like provider did some service on the server… Sorry for the inconvenience.

#11

I see this issue in your logs. I would reach out to WPML.

[04-Feb-2026 07:23:24 UTC] PHP Fatal error:  Uncaught ValueError: DOMDocument::loadHTML(): Argument #1 ($source) must not be empty in /home/****/plugins/wpml-string-translation/StringTranslation/Infrastructure/StringHtml/Repository/HtmlStringsRepository.php:31
#12

THx a heap! I’ll check this with WPML.

#13

You’re welcome.

#14

FYI: I talked to WPML guys. They suggested to update the string translations to the latest version 3.5. This needs to be done manually as WP does not recognise the update yet.

With no success.

#15

Thank you for the additional feedback. I’ll forward this to Charlie.

#17

After another reply form WPML this seems to be the solution:

  1. Go to the WPML >> String Translation.
  2. Open the “Auto register untranslated strings” section.
  3. Choose the “Disable auto register of untranslated strings” option
  4. Press the Save Settings button.
  5. Clear all sorts of site/server/CDN cache and see if this resolves the issue.

its working for the moment

#18

Thanks for sharing @VRANKOVINA.

#19

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.