Joomla Templates Club 406,261 posts

[mattstahl Friend mattstahlJoin date: April 2006Posts: 38Downloads:0Uploads:2]

#117321

Hi,

I’m perplexed, and just need a sharp mind and set of eyeballs to help set me straight. Could someone check the link that immediately follows and tell me why I get the listed XTML validation error on my JA Regulus template when viewing this page (and the event calendar page for that matter), but don’t have the problem on my home page or standard Joomla component pages.

Link to problem page: http://lisms.org/index.php?option=com_jaddresses&Itemid=48

W3C error for this page:

Below are the results of checking this document for XML well-formedness and validity.

Error Line 260 column 6: end tag for “div” omitted, but OMITTAG NO was specified.
</body>

You may have neglected to close an element, or perhaps you meant to “self-close” an element, that is, ending it with “/>” instead of “>”.

Info Line 41 column 0: start tag was here.
<div id=”ja-container”>

My attempted but unsuccessful fix:

If I add add an additional </div> before </body>, the action clears up the XHTML error on the two problem pages, but creates a duplicate DIV tag error on the homepage and blows CSS validation. There has to be something simple I’m missing here. Where’s the guru with the 1,000 point IQ who can tell me what that is?

Please excuse my temporarily overly extended menus, I haven’t consolidated them using split menu just yet.

[Hieu Nguyen Admin Hieu NguyenJoin date: November 2005Posts: 678Downloads:36Uploads:0 Thanks: 69 Thanked: 61 times in 1 posts]

#210817

Hi,

I think you should put the </div> before the comment <!– BEGIN: FOOTER –>. It will closed the <div id=”ja-container”> and your pages will be validated.

Hope it helps! 😉

[mattstahl Friend mattstahlJoin date: April 2006Posts: 38Downloads:0Uploads:2]

#210819

Yes, that too solves the xhtml error on that page, but like I said, it creates the following XHTML error on all standard Joomla pages and the CSS error that follows it on ALL pages, so what you’re suggesting makes the problem WORSE. Could you please take another look? I’d think you could fairly easily come up with the answer for this.

XHTML Error on standard pages when new </div> added

Below are the results of checking this document for XML well-formedness and validity.

Error Line 538 column 5: end tag for element “div” which is not open.
</div>

New CSS error on pages when new </div> tag is added

Line 538

Column 3

The element type “body” must be terminated by the matching end-tag “</body>”.

I noted that you can successfully self-close ja-container with a /> tag, but that still results in the same CSS error.

[Hieu Nguyen Admin Hieu NguyenJoin date: November 2005Posts: 678Downloads:36Uploads:0 Thanks: 69 Thanked: 61 times in 1 posts]

#210824

Hi mattstahl,

I guess that you have modified the “ja_regulus/index.php“. If you didn’t, the problem might come from these 3rd party modules that you installed on your homepage.

To find and fix the bug, please provide me your “index.php” file. BTW, you may try to re-install the Regulus template, and unpublish some 3rd party modules to see if the problems is gone.

Hope to help you soon! 🙂

[mattstahl Friend mattstahlJoin date: April 2006Posts: 38Downloads:0Uploads:2]

#210827

Hieu,

Thanks for volunteering the eyeball. Index file is attached.

Yes, you are correct in your assumption that the index file has been modified. Changes were made to the template to solve the often-cited footer problem of this template described in the Joomlart thread found at http://www.joomlart.com/forums/topic/ja-regulus-footer-fix/ that you folk have been unable to resolve so far. If you can fix what this one comparatively minor error I’m having here, I’d suggest that you could use it as a basis for posting a correction to the footer problem many of your Regulus, Regulus Extra, and Spica purchasers have repeatedly been complaining about, so there’s a potential benefit to everyone effort here. Going back to your stock template would only reintroduce the former, and more problematic — from a display standpoint — footer problem.

Thank you for your time. My modified Index.php (renamed as index.txt) file is attached. Can’t wait to see what wisdom you can offer.

---

Attachments:

1. index.txt

[Hieu Nguyen Admin Hieu NguyenJoin date: November 2005Posts: 678Downloads:36Uploads:0 Thanks: 69 Thanked: 61 times in 1 posts]

#210842

Hi,

Finally I find the bug 🙂 . The problem is from here:

<?php if ( mosCountModules( 'right' ) || mosCountModules( 'user2' ) ) { ?>
<!-- BEGIN: RIGHT SIDE -->

<div id="ja-rightcol">
<?php mosLoadModules ( 'user2',-2 );
mosLoadModules ( 'right',-2 ); ?>
</div>
</div>

<!-- END: RIGHT SIDE -->
<?php } ?>
</div>


So on the frontpage with three columns, the close </div> is there. But on the other pages with two or one column, the close </div> will be wipped off. 😉

To fix the problem, please change the code above to:

<?php if ( mosCountModules( 'right' ) || mosCountModules( 'user2' ) ) { ?>
<!-- BEGIN: RIGHT SIDE -->
<div id="ja-rightcol">
<?php mosLoadModules ( 'user2',-2 );
mosLoadModules ( 'right',-2 ); ?>
</div>
<!-- END: RIGHT SIDE -->
<?php } ?>

</div>
</div>

Hope it help!

[mattstahl Friend mattstahlJoin date: April 2006Posts: 38Downloads:0Uploads:2]

#210849

That solves it Hieu. The problem was certainly hard to track down, but looking at your solution, it all looks easy in hindsight. If I could volunteer a suggestion, I’d post a patch, forum sticky and/or updated template file for Regulus/Regulus Extra that incorporates your </div error fix and my footer mods. You’d make a lot of previous purchasers happy, and save yourself some gripes going forward.

Thanks for the genius.

[Author]

Posts