|
Page 1 of 1
|
Hans
Joined: August 2011
Posts: 120
Location:  n43, w86
|
 Possible Bug - Icy-2.0 News Ticker Not Displaying On FF.
I noticed that the news tickers does not display the links on FireFox, seems to work fine with Chrome though.
I guess that's what it looks like. Just wanted to let you all know.
|
#1 Thu 02 Feb, 2012 03:39 |
|
Sponsors

|
Icy Phoenix is an open source project, you can show your appreciation and support future development by donating to the project.
|
|
Joshua203 
Joshua 203
Dutch A Go Go

Joined: August 2008
Posts: 1754
Location:  Earth, Europe, the Netherlands, Rotterdam
|
 Re: Possible Bug - Icy-2.0 News Ticker Not Displaying On FF.
I have taken a look on TheSteffen's test board and I can not see the problem there Hans, however on your forum it seems to show for a second (or less) on refresh on both nightly and FF ..all other main browsers look just fine (opera, safari, explorer 64/32)
PS .. if i start clicking fast before they apear where I expect them to apear for this short time with FF I can even go to a random news link
Maybe you have a modification causing this?
____________ www.DutchaGoGo.com (development/under construction ...Forever?¿?)
|
#2 Thu 02 Feb, 2012 07:39 |
|
Joshua203 
Joshua 203
Dutch A Go Go

Joined: August 2008
Posts: 1754
Location:  Earth, Europe, the Netherlands, Rotterdam
|
 Re: Possible Bug - Icy-2.0 News Ticker Not Displaying On FF.
Looking a bit deeper on your page...
W3C can not check the url
W3C wrote: Sorry, I am unable to validate this document because on line 288 it contained one or more bytes that I cannot interpret as utf-8 (in other words, the bytes found are not valid values in the specified Character Encoding). Please check both the content of the file and the character encoding indication.
The error was: utf8 "\xD7" does not map to Unicode
Line 288 just happens to be the ticker!
Now if I copy your source code and paste it to W3C I get these results:
Validation Output: 19 Errors
Line 173, Column 18: document type does not allow element "br" heremenu1[0] = '<br /><div class="center-block-text"> <form action="http://www…
?
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 173, Column 49: document type does not allow element "div" here… '<br /><div class="center-block-text"> <form action="http://www.gplforum…
?
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 174, Column 96: document type does not allow element "a" here…gplforum.com/./search.php" title="Search inside the Site">Advanced Search</a>';
?
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 177, Column 114: document type does not allow element "a" here…rch.php?search_id=newposts" title="View posts since last visit">New Posts</a>';
?
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 189, Column 169: document type does not allow element "div" here…+ ';" onmouseover="clearhidemenu();" onmouseout="dynamichide(event);"></div>');
?
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 288, Column 20: there is no attribute "name" <marquee name="news_ticker_3" id="news_ticker_3" behavior="scroll" directi…
?
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 288, Column 39: there is no attribute "id" <marquee name="news_ticker_3" id="news_ticker_3" behavior="scroll" directi…
?
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 288, Column 64: there is no attribute "behavior"…ticker_3" id="news_ticker_3" behavior="scroll" direction="left" scrollamount="…
?
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 288, Column 83: there is no attribute "direction"…ticker_3" behavior="scroll" direction="left" scrollamount="" loop="true" onmou…
?
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 288, Column 103: there is no attribute "scrollamount"…scroll" direction="left" scrollamount="" loop="true" onmouseover="this.stop()"…
?
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 288, Column 111: there is no attribute "loop"…direction="left" scrollamount="" loop="true" onmouseover="this.stop()" onmouse…
?
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 288, Column 130: there is no attribute "onmouseover"…rollamount="" loop="true" onmouseover="this.stop()" onmouseout="this.start()">…
?
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 288, Column 155: there is no attribute "onmouseout"… onmouseover="this.stop()" onmouseout="this.start()"><a href="http://feedproxy…
?
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 288, Column 169: element "marquee" undefined…this.stop()" onmouseout="this.start()"><a href="http://feedproxy.google.com/~r…
?
You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
•incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
•by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
•by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
Line 338, Column 89: character "&" is the first character of a delimiter but occurred as data…k" href="viewforum.php?f=23">Hardware & General Computer Related</a></span><br…
?
This message may appear in several cases:
•You tried to include the "<" character in your page: you should escape it as "<"
•You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
•Another possibility is that you forgot to close quotes in a previous tag.
Line 357, Column 91: character "&" is the first character of a delimiter but occurred as data…ss="forumlink" href="viewforum.php?f=13">Networking & Internet</a></span><br />
?
This message may appear in several cases:
•You tried to include the "<" character in your page: you should escape it as "<"
•You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
•Another possibility is that you forgot to close quotes in a previous tag.
Line 798, Column 100: character "&" is the first character of a delimiter but occurred as data…link" href="viewforum.php?f=15">Front Page Articles & Feedback</a></span><br />
?
This message may appear in several cases:
•You tried to include the "<" character in your page: you should escape it as "<"
•You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
•Another possibility is that you forgot to close quotes in a previous tag.
Line 897, Column 73: there is no attribute "width"…avior="scroll" direction="left" width="90%" height="12" scrolldelay="100" scro…
?
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 897, Column 86: there is no attribute "height"…" direction="left" width="90%" height="12" scrolldelay="100" scrollamount="4" …
?
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 897, Column 103: there is no attribute "scrolldelay"…" width="90%" height="12" scrolldelay="100" scrollamount="4" loop="true" onmou…
?
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 897, Column 189: element "marquee" undefined…ollamount="4" loop="true" onmouseover="this.stop()" onmouseout="this.start()">|
?
You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
•incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
•by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
•by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
Line 1011, Column 3: document type does not allow element "p" here<p><a href="http://mirror.hfase.com">mirror.hfase.com</a> <a href="http://…
?
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
As you can see in this last error report this same line 288 pops up quite alot.
I hope this helps a little
EDIT:
Personally I would start by removing the funny sign in:
Kingston HyperX Genesis 4�4 GB DDR3-2133 RAM Review
____________ www.DutchaGoGo.com (development/under construction ...Forever?¿?)
Edited by Joshua203, Thu 02 Feb, 2012 08:11: typo corrections Edited by Joshua203, Thu 02 Feb, 2012 08:14: more typo's |
#3 Thu 02 Feb, 2012 08:10 |
|
Hans
Joined: August 2011
Posts: 120
Location:  n43, w86
|
 Re: Possible Bug - Icy-2.0 News Ticker Not Displaying On FF.
That character is just from the feed being displayed, I will change the feed for you to something that will show up correctly.
Only modifications done to the original 1.3.27.80 (2.0 beta 2) are in the following two files.
templates/default/overall_footer.tpl
<!-- IF S_LOFI -->
<!-- IF S_LOFI_BOTS -->
<!-- INCLUDE ../common/lofi/bots/lofi_bots_footer.tpl -->
<!-- ELSE -->
<!-- INCLUDE ../common/lofi/lofi_footer.tpl -->
<!-- ENDIF -->
<!-- ELSE -->
<!-- INCLUDE overall_inc_footer.tpl -->
<tr>
<td colspan="3">
<div id="bottom_logo_ext">
{IMG_TBL}
<div id="bottom_logo">
<table class="empty-table" width="100%" cellspacing="0" cellpadding="0" border="0">
<tr>
<td nowrap="nowrap" class="min250" align="left"><span class="copyright">{COPYRIGHT_LINK}{TRANSLATION_INFO}</span></td>
<td nowrap="nowrap" align="center">
<div style="text-align: center;">
<span class="generation"><b>{LOFI}</b></span><br />
<!-- IF S_GENERATION_TIME -->
<span class="generation">{PAGE_GEN_TIME} <b>{GENERATION_TIME}s</b> (PHP: {PHP_PART}% SQL: {SQL_PART}%){MEMORY_USAGE}</span><br />
<span class="generation">{SQL_QUERIES}: {NUMBER_QUERIES} - {DEBUG_TEXT} - {GZIP_TEXT}</span>
<!-- ENDIF -->
</div>
</td>
<td nowrap="nowrap" class="min250" align="right">{TEMPLATE_COPYRIGHT_LINK}</td>
</tr>
</table>
</div>
{IMG_TBR}
</div>
</td>
</tr>
</table>
{PAGE_END}
<!-- IF GF_BLOCK --><!-- BEGIN gfooter_blocks_row -->{gfooter_blocks_row.CMS_BLOCK}<!-- END gfooter_blocks_row --><!-- ENDIF -->
{BOTTOM_HTML_BLOCK}
<span><a name="bottom"></a></span>
<!-- IF not S_BOT -->{RUN_CRON_TASK}<!-- ENDIF -->
</div>
{GOOGLE_ANALYTICS}
</div>
</body>
<p><a href="http://mirror.hfase.com">mirror.hfase.com</a> <a href="http://www.gplforum.com">www.gplforum.com</a> <a href="http://hfase.com">hfase.com</a></p>
</html>
<!-- ENDIF -->
&
templates/default/overall_header.tpl
<!-- IF S_LOFI -->
<!-- IF S_LOFI_BOTS -->
<!-- INCLUDE ../common/lofi/bots/lofi_bots_header.tpl -->
<!-- ELSE -->
<!-- INCLUDE ../common/lofi/lofi_header.tpl -->
<!-- ENDIF -->
<!-- ELSE -->
{DOCTYPE_HTML}
<head>
<!-- INCLUDE overall_inc_header.tpl -->
{EXTRA_CSS_JS}
<!-- IF S_HEADER_DROPDOWN -->
<script type="text/javascript">
/***********************************************
* AnyLink Drop Down Menu- � Dynamic Drive (www.dynamicdrive.com)
* This notice MUST stay intact for legal use
* Visit http://www.dynamicdrive.com/ for full source code
***********************************************/
//Contents for menu 1
var menu1 = new Array();
menu1[0] = '<br /><div class="center-block-text"> <form action="{FULL_SITE_PATH}{U_SEARCH}" method="post"><input name="search_keywords" type="text" class="post" style="width: 150px;" /> <input type="submit" class="mainoption" value="{L_SEARCH}" /> <br /></form></div>';
menu1[1] = ' <a href="{FULL_SITE_PATH}{U_SEARCH}" title="{L_SEARCH_EXPLAIN}">{L_ADV_SEARCH}</a>';
//Contents for menu 2
var menu2 = new Array();
menu2[0] = '<a href="{FULL_SITE_PATH}{U_SEARCH_NEW}" title="{L_SEARCH_NEW}">{L_SEARCH_NEW2}</a>';
menu2[1] = '{L_DISPLAY_UNREAD}';
menu2[2] = '{L_DISPLAY_MARKED}';
menu2[3] = '{L_DISPLAY_PERMANENT}';
var menuwidth = '180px'; //default menu width
var disappeardelay = 250; //menu disappear speed onMouseout (in miliseconds)
var hidemenu_onclick = "no"; //hide menu when user clicks within menu?
/////No further editing needed
if (ie4 || ns6)
{
document.write('<div id="dropmenudiv" class="row1" style="visibility: hidden; width:' + menuwidth + ';" onmouseover="clearhidemenu();" onmouseout="dynamichide(event);"></div>');
}
</script>
<script type="text/javascript" src="{FULL_SITE_PATH}{T_COMMON_TPL_PATH}js/ddmenu.js"></script>
<script type="text/javascript">
if (hidemenu_onclick == "yes")
{
document.onclick = hidemenu;
}
</script>
<!-- ENDIF -->
</head>
<body>
<div align="center">
<div id="global-wrapper" style="width: 99%; text-align: left;">
<span><a name="top"></a></span>
{TOP_HTML_BLOCK}
<!-- IF GH_BLOCK --><!-- BEGIN gheader_blocks_row -->{gheader_blocks_row.CMS_BLOCK}<!-- END gheader_blocks_row --><!-- ENDIF -->
<!-- IF PROFILE_VIEW --><script type="text/javascript">window.open('{U_PROFILE_VIEW}','_blank','height=800,width=250,resizable=yes');</script><!-- ENDIF -->
{PAGE_BEGIN}
<table id="forumtable" cellspacing="0" cellpadding="0">
<!-- IF GT_BLOCK -->
<tr><td width="100%" colspan="3"><!-- BEGIN ghtop_blocks_row -->{ghtop_blocks_row.CMS_BLOCK}<!-- END ghtop_blocks_row --></td></tr>
<!-- ENDIF -->
<tr>
<td width="100%" colspan="3" valign="top">
<div id="top_logo">
<table class="" width="100%" cellspacing="0" cellpadding="0" border="0">
<tr>
<td align="left" height="100%" valign="middle">
<!-- IF GL_BLOCK -->
<!-- BEGIN ghleft_blocks_row -->{ghleft_blocks_row.OUTPUT}<!-- END ghleft_blocks_row -->
<!-- ELSE -->
<div id="logo-img"><a href="{FULL_SITE_PATH}{U_PORTAL}" title="{L_HOME}"><img src="{FULL_SITE_PATH}{SITELOGO}" alt="{L_HOME}" title="{L_HOME}" /></a></div>
<!-- ENDIF -->
</td>
<td align="center" valign="middle"><!-- IF S_HEADER_BANNER --><center><br />{HEADER_BANNER_CODE}</center><!-- ELSE --> <!-- ENDIF --></td>
<td align="right" valign="middle">
<!-- <div class="sitedes"><h1>{SITENAME}</h1><h2>{SITE_DESCRIPTION}</h2></div> -->
<!-- IF GR_BLOCK -->
<!-- BEGIN ghright_blocks_row -->{ghright_blocks_row.OUTPUT}<!-- END ghright_blocks_row -->
<!-- ELSE -->
<!-- IF S_LOGGED_IN --> <!-- ELSE --> <!-- ENDIF -->
<!-- ENDIF -->
</td>
</tr>
</table>
</div>
</td>
</tr>
<!-- IF GB_BLOCK -->
<tr><td width="100%" colspan="3"><!-- BEGIN ghbottom_blocks_row -->{ghbottom_blocks_row.CMS_BLOCK}<!-- END ghbottom_blocks_row --></td></tr>
<!-- ELSE -->
<tr>
<td width="100%" class="forum-buttons" colspan="3">
<a href="{FULL_SITE_PATH}{U_PORTAL}">{L_HOME}</a> <img src="{FULL_SITE_PATH}{IMG_MENU_SEP}" alt="" />
<a href="{FULL_SITE_PATH}{U_INDEX}">{L_INDEX}</a> <img src="{FULL_SITE_PATH}{IMG_MENU_SEP}" alt="" />
<!-- BEGIN switch_upi2db_off -->
<a href="{FULL_SITE_PATH}{U_SEARCH_NEW}">{L_NEW2}</a> <img src="{FULL_SITE_PATH}{IMG_MENU_SEP}" alt="" />
<!-- END switch_upi2db_off -->
<!-- BEGIN switch_upi2db_on -->
<span style="vertical-align: top;">{L_POSTS}: </span><a href="{FULL_SITE_PATH}{U_SEARCH_NEW}">{L_NEW2}</a><span style="vertical-align: top;"> • </span>{L_DISPLAY_U}<span style="vertical-align: top;"> • </span>{L_DISPLAY_M}<span style="vertical-align: top;"> • </span>{L_DISPLAY_P} <img src="{FULL_SITE_PATH}{IMG_MENU_SEP}" alt="" />
<!-- END switch_upi2db_on -->
<!-- IF S_LOGGED_IN -->
<a href="{FULL_SITE_PATH}{U_PROFILE}">{L_PROFILE}</a> <img src="{FULL_SITE_PATH}{IMG_MENU_SEP}" alt="" />
<!-- ENDIF -->
<!-- IF S_HEADER_DROPDOWN -->
<a href="{FULL_SITE_PATH}{U_SEARCH}" onmouseover="dropdownmenu(this, event, menu1, '250px');" onmouseout="delayhidemenu();">{L_SEARCH}</a> <img src="{FULL_SITE_PATH}{IMG_MENU_SEP}" alt="" />
<!-- ELSE -->
<a href="{FULL_SITE_PATH}{U_SEARCH}">{L_SEARCH}</a> <img src="{FULL_SITE_PATH}{IMG_MENU_SEP}" alt="" />
<!-- ENDIF -->
<a href="{FULL_SITE_PATH}{U_FAQ}">{L_FAQ}</a> <img src="{FULL_SITE_PATH}{IMG_MENU_SEP}" alt="" />
<!-- IF not S_LOGGED_IN -->
<a href="{FULL_SITE_PATH}{U_REGISTER}">{L_REGISTER}</a> <img src="{FULL_SITE_PATH}{IMG_MENU_SEP}" alt="" />
<!-- ENDIF -->
<a href="{FULL_SITE_PATH}{U_LOGIN_LOGOUT}">{L_LOGIN_LOGOUT2}</a>
</td>
</tr>
<!-- ENDIF -->
<!-- IF S_PAGE_NAV --><tr><td width="100%" colspan="3"><div style="margin-left: 7px; margin-right: 7px;"><!-- INCLUDE breadcrumbs_main.tpl --></div></td></tr><!-- ENDIF -->
<!-- INCLUDE overall_inc_body.tpl -->
<!-- ENDIF -->
Reason for the edits in those files in this thread. http://www.icyphoenix.com/viewtopic.php?f=3&p=55093#p55093
Also I added the links at the very bottom of the page
Ok, I changed the feed that is being displayed. this is what the settings look like.
And just so you know, this is not a problem for me, I am just reporting errors that I find.
EDIT: (inc. side-by-side Chrome FF)
|
#4 Thu 02 Feb, 2012 12:05 |
|
Joshua203 
Joshua 203
Dutch A Go Go

Joined: August 2008
Posts: 1754
Location:  Earth, Europe, the Netherlands, Rotterdam
|
 Re: Possible Bug - Icy-2.0 News Ticker Not Displaying On FF.
Well at least W3C is now accepting to test by url again (30 errors now) EDIT ..sorry (15 errors, 3 warnings)
I think it would pay if you would have a close look at those, for example...
this:
</body>
<p><a href="http://mirror.hfase.com">mirror.hfase.com</a> <a href="http://www.gplforum.com">www.gplforum.com</a> <a href="http://hfase.com">hfase.com</a></p>
</html>
can't be right can it?
Validating by url should be posible to get validated 100%, by pasting the source to W3C I'm not sure
____________ www.DutchaGoGo.com (development/under construction ...Forever?¿?)
|
#5 Thu 02 Feb, 2012 13:39 |
|
Hans
Joined: August 2011
Posts: 120
Location:  n43, w86
|
 Re: Possible Bug - Icy-2.0 News Ticker Not Displaying On FF.
 You caught me  I removed that piece of code, cleared cache.. Did not make a difference though, the scrolling links in the "news ticker" still disappear when viewed with FF.
So now the only modification to the original code is the one Mort had me do in the post contained in the following link. http://www.icyphoenix.com/show_post.php?p=55085
|
#6 Fri 03 Feb, 2012 09:42 |
|
Joshua203 
Joshua 203
Dutch A Go Go

Joined: August 2008
Posts: 1754
Location:  Earth, Europe, the Netherlands, Rotterdam
|
 Re: Possible Bug - Icy-2.0 News Ticker Not Displaying On FF.
Well it's not about catching you (but you know that) and I would not dare judging Mort's code suggestion (I can't run fast enough to get myself in a safe place  )
I also did not expect the removal to fix this issue but I just used it to point out the page isn't flawless
Still thinking ... "why doesn't he reply to validating the page and the errors that will pop up?"
It's probably not the case that you have to fix 15 errors ... often fixing one error will repair multiple (for example: when you forget to close a tag it will cause more errors after that piece of code)
I know you told me that you don't care about the ticker and it's not important but I can almost assure you this problem is only showing you that something is wrong somewhere and it may cause (or already is causing) other problems too.
W3C can be a pain at times but it most certainly is your friend for cleaning your code
____________ www.DutchaGoGo.com (development/under construction ...Forever?¿?)
|
#7 Fri 03 Feb, 2012 19:05 |
|
Hans
Joined: August 2011
Posts: 120
Location:  n43, w86
|
 Re: Possible Bug - Icy-2.0 News Ticker Not Displaying On FF.
Well it's not about catching you (but you know that) and I would not dare judging Mort's code suggestion (I can't run fast enough to get myself in a safe place  )
I also did not expect the removal to fix this issue but I just used it to point out the page isn't flawless
Still thinking ... "why doesn't he reply to validating the page and the errors that will pop up?"
It's probably not the case that you have to fix 15 errors ... often fixing one error will repair multiple (for example: when you forget to close a tag it will cause more errors after that piece of code)
I know you told me that you don't care about the ticker and it's not important but I can almost assure you this problem is only showing you that something is wrong somewhere and it may cause (or already is causing) other problems too.
W3C can be a pain at times but it most certainly is your friend for cleaning your code 
You are very correct, I don't mind this. In fact I loathe FireFox almost more than IE.
Mort brought up a very valid point recently though that we should look for errors in features that we don't use or may not think are important. With IcyPhoenix being the awesome piece of work that you all have contributed to I felt I should at least show the respect of saying something about this error.
I would have mentioned the validation, however the last couple days I have been busy re-building my Drupal site. (added way to much crap)
I am done with that though, along with compiling my-own coustom BFS Linux 3.0.0-14-server-ck kernel for my server,  Installed node.js and memcached and a few other naughty things.
I will go through the "forum.php" page and it's dependency's to chase off as many errors as I can though. I also did not think the links at the very bottom mattered, but I preach "scientific theory".
If I can get it to validate at least, my next step will be figuring out how to use GitHub. Right now I only have a vague understanding of how to develop using Git.
|
#8 Sat 04 Feb, 2012 07:04 |
|
Joshua203 
Joshua 203
Dutch A Go Go

Joined: August 2008
Posts: 1754
Location:  Earth, Europe, the Netherlands, Rotterdam
|
 Re: Possible Bug - Icy-2.0 News Ticker Not Displaying On FF.
In fact I loathe FireFox almost more than IE. 
Then you don't want to know I'm one of the few idiots who's using IE as main browser
Mort brought up a very valid point recently though that we should look for errors in features that we don't use or may not think are important.
True and yes he made some valid points but I also think he mentioned testing on clean installs
With IcyPhoenix being the awesome piece of work that you all have contributed to I felt I should at least show the respect of saying something about this error.
Very much appreciated Hans
I will go through the "forum.php" page and it's dependency's to chase off as many errors as I can though.
When you do, just try not to start at the top of the list but start (high up) with some obvious errors ( for example the not closed tags ), it could save you from trying to fix the consequences of other mistakes.
I also did not think the links at the very bottom mattered, but I preach "scientific theory".
I just noticed it was at a weird position, so it was an easy example
Goodluck chasing the bugs Hans, have a great weekend,
...Joshua203
PS .. about GIT ..I'm glad most of the time I can find the download button
____________ www.DutchaGoGo.com (development/under construction ...Forever?¿?)
|
#9 Sat 04 Feb, 2012 17:14 |
|
spydie 
Joined: December 2008
Posts: 1796
Location:  In the Boxes
|
 Re: Possible Bug - Icy-2.0 News Ticker Not Displaying On FF.
Maybe have a look at templates/default/overall_header.tpl , overall_inc_header.tpl and overall_inc_header_js.tpl
same with footer, to close off
____________ Out of Order
|
#10 Sat 04 Feb, 2012 18:10 |
|
Hans
Joined: August 2011
Posts: 120
Location:  n43, w86
|
 Re: Possible Bug - Icy-2.0 News Ticker Not Displaying On FF.
I will do that.
Been a little busy (fatal server user error) I about got my machine back to normal though...
Soon as my machine is normal again though I will check things out with a "fine tooth comb", I almost think I should get the hang of GitHub first though so I can just fork and apply any changes I find.
|
#11 Wed 15 Feb, 2012 08:35 |
|
mort 
 Spam Basher

Joined: August 2010
Posts: 998
Location:  Up a tree
|
 Re: Possible Bug - Icy-2.0 News Ticker Not Displaying On FF.
It is a BUG! But do read this whole post BEFORE you start changing things.
When you edit Edit existing XML News Feed It doesn't POST the info to the DB - In fact it strips the existing columns and leaves them empty.
Anyway, below should fix it until MG gets around to fixing the real problem of the script not being submitted.
#########################
default\blocks\xs_news_block.tpl
Line 30:
Find:
<marquee name="{news_ticker_row.XS_NEWS_TICKER_ID}" id="{news_ticker_row.XS_NEWS_TICKER_ID}" behavior="scroll" direction="{news_ticker_row.XS_NEWS_TICKER_SCROLL_DIR}" scrollamount="{news_ticker_row.XS_NEWS_TICKER_SPEED}" loop="true" onmouseover="this.stop()" onmouseout="this.start()">{news_ticker_row.XS_NEWS_TICKER_CONTENTS}</marquee>
Replace With: (Lets give it some height, width and speed).
<marquee name="{news_ticker_row.XS_NEWS_TICKER_ID}" id="{news_ticker_row.XS_NEWS_TICKER_ID}" behavior="scroll" direction="{news_ticker_row.XS_NEWS_TICKER_SCROLL_DIR}" scrolldelay="100" scrollamount="4" width="98%" height="12" loop="true" onmouseover="this.stop()" onmouseout="this.start()">{news_ticker_row.XS_NEWS_TICKER_CONTENTS}</marquee>
#########################
templates\default\xs_news_banner.tpl
Line 31:
Find:
<marquee name="{news_ticker_row.XS_NEWS_TICKER_ID}" id="{news_ticker_row.XS_NEWS_TICKER_ID}" behavior="scroll" direction="{news_ticker_row.XS_NEWS_TICKER_SCROLL_DIR}" scrollamount="{news_ticker_row.XS_NEWS_TICKER_SPEED}" loop="true" onmouseover="this.stop()" onmouseout="this.start()">{news_ticker_row.XS_NEWS_TICKER_CONTENTS}</marquee>
Replace With:
<marquee name="{news_ticker_row.XS_NEWS_TICKER_ID}" id="{news_ticker_row.XS_NEWS_TICKER_ID}" behavior="scroll" direction="{news_ticker_row.XS_NEWS_TICKER_SCROLL_DIR}" scrolldelay="100" scrollamount="4" width="98%" height="12" loop="true" onmouseover="this.stop()" onmouseout="this.start()">{news_ticker_row.XS_NEWS_TICKER_CONTENTS}</marquee>
#########################
OR JUST THIS ONE - - - - DON'T DO BOTH THIS AND THE TPL'S!
/adm/admin_xs_news_xml.php
Find:
case 'modxml':
// Modify a news ticker in the DB
$xml_feed = xsm_prepare_message($xml_feed);
$sql = "UPDATE " . XS_NEWS_XML_TABLE . "
SET xml_title = '" . $db->sql_escape(request_post_var($_POST['xml_title'], '', true)) . "', xml_show = " . intval($_POST['xml_show']) . ", xml_feed = '" . $db->sql_escape($xml_feed) . "', xml_is_feed = '" . intval($_POST['xml_is_feed']) . "', xml_width = '" . $db->sql_escape(request_post_var($_POST['xml_width'], '')). "', xml_height = '" . $db->sql_escape(request_post_var($_POST['xml_height'], '')). "', xml_font = '" . $db->sql_escape(request_post_var($_POST['xml_font'], '')). "', xml_speed = '" . $db->sql_escape(request_post_var($_POST['xml_speed'], '')). "', xml_direction = " . intval($_POST['xml_direction']). "
WHERE xml_id = " . intval($_POST['id']);
$result = $db->sql_query($sql);
$db->clear_cache('xs_');
$message = $lang['n_xml_news_updated'] . '<br /><br />' . sprintf($lang['n_xml_click_return_newslist'], '<a href="' . append_sid('admin_xs_news_xml.' . PHP_EXT) . '">', '</a>') . '<br /><br />' . sprintf($lang['Click_return_admin_index'], '<a href="' . append_sid('index.' . PHP_EXT . '?pane=right') . '">', '</a>');
message_die(GENERAL_MESSAGE, $message);
break;
Replace With:
case 'modxml':
// Modify a news ticker in the DB
$xml_feed = xsm_prepare_message($xml_feed);
$sql = "UPDATE " . XS_NEWS_XML_TABLE . "
SET xml_title = '" . $db->sql_escape($_POST['xml_title'], '', true) . "', xml_show = " . intval($_POST['xml_show']) . ", xml_feed = '" . $db->sql_escape($xml_feed) . "', xml_is_feed = '" . intval($_POST['xml_is_feed']) . "', xml_width = '" . $db->sql_escape($_POST['xml_width'], ''). "', xml_height = '" . $db->sql_escape($_POST['xml_height'], ''). "', xml_font = '" . $db->sql_escape($_POST['xml_font'], ''). "', xml_speed = '" . $db->sql_escape($_POST['xml_speed'], ''). "', xml_direction = " . intval($_POST['xml_direction']). "
WHERE xml_id = " . intval($_POST['id']);
$result = $db->sql_query($sql);
$db->clear_cache('xs_');
$message = $lang['n_xml_news_updated'] . '<br /><br />' . sprintf($lang['n_xml_click_return_newslist'], '<a href="' . append_sid('admin_xs_news_xml.' . PHP_EXT) . '">', '</a>') . '<br /><br />' . sprintf($lang['Click_return_admin_index'], '<a href="' . append_sid('index.' . PHP_EXT . '?pane=right') . '">', '</a>');
message_die(GENERAL_MESSAGE, $message);
break;
Then you will have to go to Admin and edit the News-Tickers for font size and speed.
########################
Also in the forum.php the html shows:
<p class="forum-buttons2" style="height: 17px; valign: middle;">
valign is not recognised in style/css.
<p class="forum-buttons2" style="height: 17px; vertical-align: middle;">
|
#12 Sat 03 Mar, 2012 06:39 |
|
|
Page 1 of 1
|
Was this topic useful?
Was this topic useful?
Link this topic |
URL |
|
BBCode |
|
HTML |
|
You cannot post new topics You cannot reply to topics You cannot edit your posts You cannot delete your posts You cannot vote in polls You cannot attach files You can download files You cannot post calendar events
|
|
|
|