[solved] IE7 issue with news module

[tonyg]

Hi,
  I am having an issue with the way ie7 is displaying my news detail page on my site.  It looks fine in firefox.  this is the url
http://wwwstage.ultra-fei.com/index.php?mact=News,cntnt01,detail,0&cntnt01articleid=12&cntnt01origid=61&cntnt01detailtemplate=FL%20News%20Detail&cntnt01returnid=101

the way i have this page built, i have a template with a content section, then i have a page with no content ()  finally, I call the news summary page this way:

Code: Select all

{news summarytemplate="FL Summary" number="3" detailpage="news_detail" detailtemplate="FL News Detail" category="Press Releases"}

I was under the impression that the news detail would be inserted into the content area...this seems to work on firefox, but not ie7 (look ok in ie6 btw)

Can anyone help me with this?  am I using the news module wrong?

thanks much

[pedes]

i looked to it with IE7 , Firefox , Opera ans Safari

i think Firefox and Safri are displaying it correct but for Opera and IE7 it gives a different view, text is black or that white box is not going far enough

How should it be?

Kind regards
Peter

[tonyg]

Hi,
  Yes, firefox looks right, ie looks wrong....any ideas?

[tophers]

Hi Tony,

It looks like the comment tag isn't enough to hold open the content in iE7. Try putting this into news_detail:
{news summarytemplate="FL Summary" number="3" detailtemplate="FL News Detail" category="Press Releases"}

It will still accept your call from the main news page. In fact, you don't really need the news-detail page at all - the module will show the detail in the same page. If you remove 'detailpage="news_detail" ' from the news page it should work as well.

[tonyg]

Topher,
  I tried your suggestion (thanks) and removed the call to a different page for detail.  same result.  it is now going back to that page, but not in the content area

any other idea's?

[tophers]

It looks like a missing '>' at the end of '<div id="subPageArticle" ' - in your template FL News.

[tonyg]

TADA!!!

Its funny how different browsers will react differently to mistakes.  I was relying on the 'web developer' addon bar (firefox) to validate...but that only validates the source sent over.....

humm


thanks AGAIN