After checking with ChatGPT, it was suggested that the issue may be related to a parsing conflict between the url tag and the nolink parameter when switching Text Editors.
This is only a preliminary inference from that consultation, and I personally suspect that this kind of issue might not be easy to fix quickly at the root level.

At the moment, my main goal is simply to restore this world's World Homepage to an editable state as soon as possible.
Would it be possible to either switch my World Homepage editor back to Euclid, so I can remove the BBCode field that may be causing the issue, or have the WA team remove the problematic field from this page via the backend?

This world is currently set to Private and is being used only for testing.
I'm not sure whether the Widget information available in this state would be helpful, but here is the world for reference:

world:7ea39df2-2627-4340-bdb4-d8ad7decc3e9

Thanks for the detailed bug report, I'll see what I can do to fix the issue on the editor side but you are using an advanced editor features like:
- tooltipping the image which is not a permitted behaviour for the visual wysiwyg.
Switching between advanced and simple editor is highly discouraged because these are NON replacable because Euclid allows for much more advanced styles of text editing which will cause errors.

Hello, thank you for the reply!

Yes, I understand that switching between the Visual Editor and Euclid can potentially cause errors. Because of this, my current workflow is to first test things in a separate Test World before applying them to other main worlds.

In this case as well, I tested the BBCode nesting in a standalone article first, and only proceeded to switch the editor after confirming that everything displayed correctly in the World Homepage preview.

After reflecting on this issue, I think the main problem may lie in the following situation:

when an error is triggered by switching editors, the settings menu used to switch the editor on the World Homepage fails to load properly. This leaves the user unable to stop the switch or revert back to Euclid in order to remove or fix the problematic fields.

If this kind of error happens in a regular article, there are still some temporary workarounds available (for example, deleting the affected article and recreating it). However, I honestly can't imagine how one would recover if this were to happen on a fully built, large world's only World Homepage.

Based on this, I can think of a couple of possible improvements:

1. If switching the text editor fails, automatically revert to the previous state and show an error message prompting the user to check for problematic fields, until the issue is resolved.
2. In this case of an unrecoverable error, keep at least one alternative settings panel accessible that allows the user to revert the text editor setting. (Currently, when this happens on the World Homepage, the only settings panel that controls editor switching cannot be opened at all.)

Additionally, regarding the Athena World Homepage text editor settings, I'd like to mention a small usability issue as well:

In regular articles, changing the text editor is done via the settings opened from the gear icon at the bottom menu, using the left-side panel. In that context, the "Editor" indicator on the right side is just a message showing the current selection.

After getting used to this behavior, I tried to change the Editor on the World Homepage, but found that there was no Text Editor option in the same location:

…To be honest, I spent over an hour going back and forth through almost every menu and button — including the left sidebar — and still couldn't figure out how to change the Homepage text editor. In the end, I only realized where it was after rewatching the Athena launch tutorial video. It turns out that the setting is located in theright-side panel of the gear menu, a place that, in regular articles, is used purely as a "current selection display".

On top of that, the dropdown for this setting only appears on mouse hover, and before hovering there is no clear visual indication to show that it is interactive or configurable element. As a result, it looks almost identical to the non-interactive "selection display" shown in the article settings panel, making it very easy to overlook.:(

Hello,

The bug I reported previously still hasn't been fixed, and the World Homepage editing page still shows the same error.

Is there any way to recover the Homepage and make it editable again, or is deleting this World and starting over my only option?

Thank you!