Hello,
Working on an iframe embed on dev, when I ran into some odd behavior. Initially, I tried the following, working quickly:
- Made a new page.
- Edited the page: added summary, added iframe to the main-content.
- On Save & Publish, the page temporarily does the gear/saving animations, then returns to the editor with the “something has gone wrong” message.
- When I refresh the page, the summary edits were saved, but the main-content is blank.
When looked at the error logs, I saw three instances of this:
23-Feb-2026 2:42:01pm CST America/Chicago PHP Warning: Uninitialized string offset 0 in /var/www/beloit-dev.livewhale.net/livewhale/core/modules/framework/global.data.framework.php on line 860
After being a ‘smarty pants’ and poking around to make sure it wasn’t something client-related, I believe this is what is happening:
- The page is edited, with an invalid iframe being added to source code as the only element in a content area.
- On save, the invalid iframe is stripped from the content area early in the process.
- Later in the process, something tries to read the first character of the stripped content area (an empty string) some number of times and ends up failing, triggering errors, and reverting the page back to the editor view.
- Meanwhile, the rest of the page saves successfully in the background.
Thus, setting the HOSTNAME_WHITELIST in global config like I should prevents an empty content area from triggering the error. (Guess it’s kind of a client issue, but…)
Sharing for awareness, given I’m guessing some fix may be needed to prevent that code from reading an empty string made earlier in the save process.
Thanks,
Nick