I just upgraded from 5.77 to 6.0.0 and it appears that the token [TRACKBACKURL] is no longer supported in Item.Listing as it shows up now.

< Another Plug >

Any chance that you can work on the xhtml/html compliance as part of some of these fixes? Some of us have sites where W3C compliance is important to us. I would use News Articles in several mor places if I didn't have to give up xhtml compliance on those pages. I am willing to give up W3C compliance on my blog page for News Article's functionality, but not on my home page just to replace the html/text module and only gain a little more functionality.

Most of the issues are Case and and quoting and other simple fixes. There many be a couple that are a little harder to address.

< / End Plug >

I love News Articles great functionality,

/DaveS

When I relized that Lee Sykes was using News Articles and some of his site was compliant, I took a second look and he avoids using several parts of News Articles.

I have have a site running DNN 4.8.0 where a good many of the pages are xhtml compliant. I not only have had to create skins and containers, I even have had to use PageBlaster's regex-replacement rules to do some "fix-up" of parts of DNN and module output that I can't easily fix.

For News Articles I created a set of templates from your "blog", removed all table tags and stuffed  a div around each section, and a couple of br's when I needed vertical spacing.  There are still xhtml errors and they aren't coming from the templates.

On my production site I am still using a re-hash of your blog templates. I have fixed the Upper case and quotes etc, so that the templates produce compliant xhtml.

PS I checked and the TrackbackUrl problems actuall showed up in 5.79 and I missed it.

/DaveS

NewsArticles is the most compliant module out there for content management. The tokens that you use in the templates consist only of values and contain no html except for user input. Compliance is all in the templates. I have created many different templates for clients that are compliant and non-compliant (sometimes a client is adamant about you using points or pixels for text sizing and there's nothing you an do about it.). There's a book, Bulletproof Web Design by Dan Cederholm which is my bible that I use. It's the best book ever published on compliant xhtml and css for both look and acessibility.

Thank you for considering this.

/DaveS

I've seen a couple minor versions of News Articels.  Any word on making it more xhtml/html/css complant?

/DaveS

I spoke with Scott about this a couple of months ago -we are running quite a few site with completely div based templates, but they are slightly different.

I'll look at getthing these to Scott in the next couple of weeks.

Nina

Did any of the recent News Article minor releases do anything to the html/xhtml of the templates? Did Nina ever get her templates to you. I have made my templates completely  div based, but the actual html generated by the tokens appears to be the cause of the errors.

/DaveS

I just recieved the templates from Nina and they really don't address the xhtml issues.  My templates have removed all html except for a div around the whole thing and a couple of br's were I needed verticle space. The module is on a skin that passes W3C xhtml compliance on all pages with just Text/html modules. The non-compliant xhtml appears to be coming from the module and/or tokens.

I hope that you will have time to look iinto this soon.

/Dave Snow

Scott,

I just went back and looked at the blog templates included with NA 6.13 for xhtml compliance.  Many things are better but there are still a few issues and for the most part they are not part of the templates.

1.

< LINK id="Template_1790"    rel="stylesheet" type="text/css"

Problem: Uppercase and ID and “rel” not allowed for link.  I fix most of these with John Mitchel's PageBlaster V3 and rules that 

lower tags, close tags, delete crap, process image tags for the whole page this option isn't available on most DNN systems.

2.

ListingItem.html  & two other places  ---  target='[LINKTARGET]'    

Problem:  If LINKTARGET is null then this is non-compliant

I fixed this by deleteing target='[LINKTARGET]' from the templates, but the correct solution is to have LINKTARGET always evaluate to a meaningfull value.

3.

Problem:  # signs are allowed in Id’s

4.

disable=”disable”  in the “previous page | next Page”

W3C doesn’t understand disable=”disable”

I haven't found this in the templates.

5. There doesn't appear to be a templat for the "syndication" page and there are issues with this page having to do with .NormalBold.  My NormalBold has both a foreground and background color defined and becomes invisible on this page. If there was a template and we could tweak the layout and classes then this would be an easy fix.

I see 87 W3C errors on this page but haven't investigated since I have no template to work with.

Future suggestions:

1. Just like you have a syndication page a page for biographies and a help page would be great additions. Each with a template so that administrators could customize the layout.

Keep up the good work,

/DaveS

I don't see what the ID could be used for in either your code or DNN's. You can't got there with a hyperlink etc. but it doesn't cause a W3C error unless LINK is uppercase and therefor unrecognized.  If you look at my Blog page a W3C it. It passes while using the "list" templates. It fails when in the "view" templates because of pingpack and the #sign in the comment ID. adding the id="#Comment" to my delete crap list causes other serious problems, so I can't do it the easy way.

This is because I have tweaked the templates and page the use PageBlaster to do "fixup" of the html after DNN has generated it. I "lowercase tags", "close tags" and "delete crap" such as
(\btabindex="\-?\d+"| [Aa]utocomplete="off"| < /link > |align="absmiddle"|disabled="disabled")

Regards,

/DaveS

Thanks Scott, this has helped me out.  Another validation problem you might want to look at is when you try to validate CSS on a page with your module, you get a file not found error.  I'm guessing this stems from the naming convention you used for your folder (DnnForge - NewsArticles).  It doesn't like the extra spaces being in there.

Sorry! We found the following errors (1)