Comments/Ratings for a Single Item

If you need greater width only at the bottom of your document, you may be
able to get it by closing the ARTICLE and MAIN tags before the code for
your design wizard. Technically, the sidebars do not run all the way down the article. They are both closed in the HTML before MAIN and ARTICLE even appear. They only appear to go all the way down, because MAIN is given a width that fits it between the sidebars.

I have not experimented with this, but the CSS file defines a float style for the side bars, suggesting that the text would drape around the ads, if it were not for the setting of the margin. So perhaps there isn't any need to hide the ASIDE elements, if I just want more space at the bottom, and an I just reduce the marginLeft and increase the maxWidth of the MAIN element.

I did it for you, and I noticed what seemed to be side effects. The text
was going over the inner nav bar, and the wizard wasn't working. So I undid
it, but the text continued to go over the nav bar, and the wizard still
didn't work. So it didn't cause those effects, but they are something you
want to fix. In general, closing the ARTICLE and MAIN tags is just a matter
of inserting the HTML for closing these in your code. This will leave you
with some unexpected tags for closing ARTICLE and MAIN further on in the
document, but the page should still work. Unlike BODY, ARTICLE and MAIN are
completely optional in HTML documents, and you are free to place code
outside of them. It is just that headers and footers are set up here so
that MAIN and ARTICLE get opened in the header and closed in the footer,
which places the main content of a page between the two ARTICLE tags, which
are inside the two MAIN tags.

All escape codes for the less-than sign seem to be gone again, so that HTML tags that should have appeared as literals in the text now again are interpreted as active HTML tags.

Whatever you did, can you please undo it?

It is worse than ever. This time all I get is a blank page, when trying to edit index information not just on that page but on any page of mine.

H. G., when you mentioned the PRE tags, that clued me in on what happened.
It was treating it as a submission that doesn't use HTML. The problem was
that there were some mismatched variable names between two scripts, which
caused checking the box for using HTML to have no effect. So I fixed that
and closed the ARTICLE and MAIN tags just before your wizard.

Charles, I have temporarily listed myself as the author of Commedia dell'Arte Chess to debug the scripts.

Charles, I have finished debugging the scripts, and I have relisted you as
the author of your page. I added a note at the end as a demonstration that
the scripts are now working.

OK, I see what you are doing: you just put an unbalanced closing tag for MAIN and ARTICLE in the submitted text, and this will locate part of that text (in this case the Design Wizard, which initially is hidden) behind those elements. The fact that the display script still adds another {/MAIN} and {/ARTICLE} behind the Wizard does not matter; these are simply ignored by the browser.

With the screen width I have (enough for adding the left ad side bar), this makes the "fineprint" end up partly behind the article text, and mostly in the left side bar below the ad, however. This is a bit ugly.

I did find a work-around for that, which is structuring the submitted text as:

{DIV class="middle"}
{ASIDE class="leftcol"}ad image{/ASIDE}
{ASIDE class="leftcol"}ad image{/ASIDE}
{MAIN}
{ARTICLE}
------------------------------------------
Normal article text
{/ARTICLE}
{/MAIN}
{/DIV}

{div style="display:none"}
Design Wizard
{/div}

{DIV class="middle"}
{MAIN}
{ARTICLE}
-------------------------------------------
{p}{hr}{div class="fineprint"}This 'user-submitted' page...{/div}
{/ARTICLE}
{/MAIN}
{/DIV}

Only caveat is that it is against HTML regulations to have multiple MAIN and ARTICLE elements.

No, the script did not change again. It was brought to my attention that
the changes I previously made were affecting the display of other pages.
(See the Decima page for details). To correct this, I did a search and
replace on the MemberSubmissions table. When I was doing a search and
replace for the Notes field, I did see your page get caught up in it. So
before I went through with the replacements, I opened another tab with the
entry for your page in it, and after I made the replacements, I changed the
value of Notes back to what it was. But Notes was the last field, and maybe
your page got caught in the search and replace earlier. All it changed were
HTML entities for less-than and greater-than signs. You can fix your page
by putting HTML entities back where they belong.