Statblock From Advanced Dropdown In Athena Obscures Whole Published Article

closed
· Articles & templates ·
By AuraGuard on 12/02/2025
· Assigned to katerinach
· Waiting for Response

I have recently been using the Athena manager/editor's Advanced Options dropdown to assign statblocks to some articles. For the articles that are not yet published, there was no issue. But for the published article above, the name bar of the statblock is covering the entirety of the article, making it impossible to read the body of the article, the full-length footer of the article, the name of the article, or even access the WA menu bar above the article.

At first, as I had put the statblock in as a block in the body of the article itself, I'd thought it was a simple conflict between the statblock being in two places in the same article. So I removed the statblock from the article body, removed the statblock in Advanced Options and then re-added it, and the issue remains.

The unpublished drafts that are unaffected do not have anything written in the body or the footer, while the affected published article does have text in both the body and the footer. Both unaffected and affected articles have text in the sidebar to some degree or other, though the unaffected articles have some default headers/dropdowns used, and the affected article has fully custom text and Key::Value pairs (sole exception being usage of the Geographic Distribution dropdown, which is consistent across both unaffected and affected articles).

As it stands, this feature is actively preventing a published article from being read. While I could revert to what I'd originally had, that would render the statblock part of Advanced Options in Athena entirely pointless and nonfunctional for my needs. Until I am told otherwise, I'll be keeping the article as it is, so that it can be viewed in its full, bugged state for troubleshooting purposes.

Steps to Reproduce

I'm not sure how to reproduce it, as I'm unwilling to publish stub drafts to try forcing it (no unpublished stub draft has the issue, but none of them have much text either). However, the apparent steps (which created the issue in the affected article), are:

  • Put fully custom text in the body, full-width footer, and top content panel sidebar (with Key::Value pairs in the sidebar) of the Species article template, without using any of the default headings or dropdowns (except for Geographic Distribution - select three entries in the Geographic Distribution dropdown). Include the table of contents BBCode in the bottom sidebar (below the bottom content panel sidebar). Use BBCode throughout the article, no CSS anywhere. Do this in the Old Version Edit (as the affected article predates the new version).
  • View the article (from the Old Version Edit) without publishing it or using the preview. Make the Geographic Distribution header invisible to the public (click the Eye icon).
  • Put a statblock sharing the name of the species of the article, plus its italicized, bracketed binomial (genus+epithet) in said statblock's name. Also in the Old Version Edit.
  • Now publish the article. Also in the Old Version Edit.
  • In the New Version Edit, give the article a colour background splash from the default options, some tags, and a fa-dragon article icon. Let this update/save.
  • In the new version edit, after having done the above, go to Advanced Options and select the same statblock as mentioned before. Let this update/save.
  • This is where the article first developed this issue. Removing the statblock from the article footer - in the New Version Edit - did not resolve the issue. Neither did removing and re-implementing the statblock in Advanced Options.

Operating System

Android

Browser

Google Chrome

Related Entity

The affected article: the buffy-streaked tatzelwurm. Issue persists across both Android mobile (smartphone), ChromeOS (Chromebook), and Windows (on a 2025 new computer). It also persists across both Google Chrome and Microsoft Edge browsers.

History

AuraGuard @ 02 Dec, 2025 12:11:01

Why does your bug report allow linking in BBCode if it just destroys it upon sending the bug report? Here's the url of the affected article:


Edit: Apparently the comments section won't let me post urls at all. This makes it really difficult to direct anyone to an affected article in bug reports, you know.

Maybe this'll work: h t t p s : / / w w w . worldanvil . com / w / elementus-2F-ackhanarr-auraguard/a/buffy-streaked-tatzelwurm-species

mikolaszko @ 02 Dec, 2025 02:51:21 Developer
Assigned katerinach
katerinach @ 09 Dec, 2025 11:02:39 Assignee
katerinach Added tag Under Investigation
katerinach @ 09 Dec, 2025 11:45:24 Assignee

Hey, so it turns out that this weird style override of your statblock is really caused by the BBCode you've written in the sidebar content bottom field, which is malformed.

This is how it should look like:

To be on par with its correct formatting as shown here :

Make this fix and check again how the presentation of this article looks like and if the problem has been resolved!

katerinach @ 09 Dec, 2025 11:45:30 Assignee
katerinach Added tag Waiting for Response
katerinach @ 09 Dec, 2025 11:45:38 Assignee
Removed tag Under Investigation
AuraGuard @ 11 Dec, 2025 05:04:11

Well, it's working now - though I'm guessing someone fixed something? Because fixing the sidebar bottom content panel alone still resulted in the same bug at first - the links in the sidebar panel top were also triggering the issue (did some troubleshooting after your solution still left me with the same issue, including just leaving the sidebar bottom content panel blank for a bit).

Then as I was putting everything back in, the issue...resolved itself? I'm using the centering (which is formatting, I wouldn't call it "style", personally - to me, "style" is things like WA's themed skins) you recommended (sans the "\r\ n" [space mine to make it actually show up] bit, which I have absolutely no idea what that's supposed to do, and the "\r" bit doesn't seem to be supported anyway [just shows up as text on the article sidebar itself]).

In any case, thank you for your time. I'm not sure exactly what happened, but the article is readable now.

katerinach @ 12 Dec, 2025 08:07:39 Assignee
set this bug to closed