RSS2 Feed Contribution

[vitalwares]

Hi,

Can someone help me with these...

Line 49, Column 31: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified.
document.write("<script id=__ie_onload defer><\/script>");✉
Line 49, Column 48: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified.
document.write("<script id=__ie_onload defer><\/script>");✉
"VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

Line 49, Column 48: required attribute "type" not specified.
document.write("<script id=__ie_onload defer><\/script>");✉
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Line 49, Column 48: document type does not allow element "script" here.
document.write("<script id=__ie_onload defer><\/script>");✉
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 49, Column 49: character "<" is the first character of a delimiter but occurred as data.
document.write("<script id=__ie_onload defer><\/script>");✉
This message may appear in several cases:

You tried to include the "<" character in your page: you should escape it as "&lt;"
You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
Another possibility is that you forgot to close quotes in a previous tag.

Line 103, Column 151: document type does not allow element "link" here.
…in_page=rss_feed&amp;feed=specials" />✉
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 104, Column 159: document type does not allow element "link" here.
…age=rss_feed&amp;feed=new_products" />✉
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 105, Column 151: document type does not allow element "link" here.
…in_page=rss_feed&amp;feed=upcoming" />✉
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 106, Column 151: document type does not allow element "link" here.
…in_page=rss_feed&amp;feed=featured" />✉
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 107, Column 155: document type does not allow element "link" here.
…age=rss_feed&amp;feed=best_sellers" />✉
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).

Am I the only one with validation errors on this forum ? Did I install something incorrectly ?

Someone please help

[a_berezin]

Goodbye

Thank you for having finally been freed from the continuous flood

[a_berezin]

Is this compatible with v 1.3.7 ?

Yes. It compatible with 1.3.7 and 1.3.8.

Affected files
==============
/includes/templates/YOUR_TEMPLATE/common/html_header.php
/includes/templates/YOUR_TEMPLATE/common/tpl_footer.php

...but no common folder in the package.

You have to adjust himself these files:

4. You can add to html_header.php somewhere beetwen <head> and </head> tags:
<?php echo rss_feed_link_alternate(); // RSS Feed ?>
5. You can add to tpl_footer.php or where you want:
<!--bof RSS Feed -->
<div id="RSSFeedLink"><?php echo rss_feed_link(RSS_ICON); ?></div>
<!--eof RSS Feed -->

[a_berezin]

No problem.. onwards to learn more about creating
my own then.

Where do you want to use it? I made a parser for xoops, ExpressionEngine and WordPress. Maybe add these parsers in contribute?

And what you think about:
Include a description of the product price? As it is done with a picture.

[a_berezin]

Am I the only one with validation errors on this forum ? Did I install something incorrectly ?

Someone please help

Remove /jscript/jscript_googleanalytics_outgoing.php and validate it once more.

[elishama3]

I am still fruitlessly trying to track down the source of the xml parsing error. I am not sure if this is related or not, but in the rss.css and rss.xls files are the following wording:

The CSS/XLS files are sent to the browser in this order: (and alphabetically within each case of more than one match):

rss*.css // are always loaded and at least ONE should contain site-wide properties.
rss*.xls // are always loaded and at least ONE should contain site-wide properties.

Do I need to input something here to make it work, and if so, what? I am not sure what site-wide properties would be appropriate for an rss feed.

Please help.

I have been going over this at length and still cannot figure out which files have the extra space at the bottom line that is a problem. Just to recap, I am getting this error when clicking on the rss button:

XML Parsing Error: xml declaration not at start of external entity
Location: http://www.phoenixflightpublications...&feed=products
Line Number 2, Column 1:<?xml version="1.0" encoding="iso-8859-1"?>

All help is much appreciated,

Thank you in advance.

[vitalwares]

Remove /jscript/jscript_googleanalytics_outgoing.php and validate it once more.

Yes Andrew, removing the file has removed the errors I mentioned but won't removing this file break the module ?

[a_berezin]

XML Parsing Error: xml declaration not at start of external entity

Ok. Use this /rss_feed/tpl_main_page.php (for debug only!!!):

<?php
/**
 * rss_feed tpl_main_page.php
 *
 * @package rss feed
 * @copyright Copyright 2004-2007 Andrew Berezin eCommerce-Service.com
 * @copyright Portions Copyright 2003-2006 Zen Cart Development Team
 * @copyright Portions Copyright 2003 osCommerce
 * @license http://www.zen-cart.com/license/2_0.txt GNU Public License V2.0
 * @version $Id: tpl_main_page.php, v 2.1.4 14.02.2008 15:26 Andrew Berezin $
 */

if(headers_sent($filename, $linenum)) {
  echo "Headers already sent in $filename on line $linenum";
  exit;
}

  $rss->rss_feed_out();

  require(DIR_WS_INCLUDES . 'application_bottom.php');

  zen_exit();
?>

[a_berezin]

Yes Andrew, removing the file has removed the errors I mentioned but won't removing this file break the module ?

Please wait. In a few days, will be a new google analitycs version.

And new version RSS Feed

P.S. Try this http://www.zen-cart.com/forum/showpo...&postcount=385

[vitalwares]

Please wait. In a few days, will be a new google analitycs version.

And new version RSS Feed

P.S. Try this http://www.zen-cart.com/forum/showpo...&postcount=385

Thanks Andrew you are a big help! I will be waiting for the modules!