RSS2 Feed Contribution

Hello Andrew,

Just updated to latest release. I have a few validation errors, but I remember they disappeared in a previous release, but in feed validator they show up again. Here are the first ones anyhow:-

line 4, column 0: Use of unknown namespace: http://base.google.com/cns/1.0 [help]

<rss version="2.0" line 12, column 89: Self reference doesn't match document location [help]

... rel="self" type="application/rss+xml" /> ^line 17, column 50: Implausible date: Mon, 01 Dec 2008 17:17:00 +1100 [help]

<lastBuildDate>Mon, 01 Dec 2008 17:17:00 +1100</lastBuildDate>

Many thanks in advance,

Heathenmagic

Hello Andrew,

I have updated the software that uses the rss, and all works fine now, so you can ignore my post.

All the best,

Heathenmagic :smile:

vitalwares:

these are errors related to the RSS feed contribution
Are you sure?

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.

Anyone? Thank you in advance.

Anyone have trouble with their feeds updating after installing the latest version (2.1.4)? I installed it a few days ago and everything seemed okay, but I added new products and some new specials last night. Nothing is updating in the feed.

This is why I loathe upgrading something that I had working fine. :frusty:

Hi,

******** Issue: Getting price to show up in the feed

Thanks Andrew for a great contribution. Have got it working great with everything except: Price. Have read all 33 pages of the forum and found a lot of posts on here about getting the price field to show up, but can't work out from these about how to actually make prices show up.

Can anyone who has got the price to show up in their RSS feed to PLEASE help by explaining how they got it to work?

Using Google Reader as the preferred RSS reader and the latest version of the contribution (11 March 2008). Zen cart 1.37.

Thanks so much in advance!

brianosc:

Hi,

******** Issue: Getting price to show up in the feed
Can anyone who has got the price to show up in their RSS feed to PLEASE help by explaining how they got it to work?

Using Google Reader as the preferred RSS reader and the latest version of the contribution (11 March 2008). Zen cart 1.37.

Same here... can't get price or images to show up in Google Reader either. Images show up in Yahoo's reader, but no prices.

Forgot about price, images and any other additional tags if you use Google Reader or any another reader, that don't support it!!! RTFM!!!!!!!!!!!!!!!!!!!!!!!!!!!

a_berezin:

Are you sure?

No Andrew I am not sure (it did seem like it thought!), I have already insalled the latest google analytics you see and I am getting new validation errors with that.

Please help...

a_berezin:

Forgot about price, images and any other additional tags if you use Google Reader or any another reader, that don't support it!!! RTFM!!!!!!!!!!!!!!!!!!!!!!!!!!!
Andrew, can you recommend a reader then that does support price, images etc et?
:smile:

a_berezin:

RTFM!!!!!!!!!!!!!!!!!!!!!!!!!!!

Which one? If you are referring to your readme, I didn't see anything about those things not working with Google Reader, etc.

And you don't need to be rude. If you are getting that frustrated with our questions, maybe contributing things isn't for you.

craftzombie:

Which one? If you are referring to your readme, I didn't see anything about those things not working with Google Reader, etc.I suspect that Andrew may be referring to the Google Reader, etc. documentation. Although his readme can realistically be expected to cover the major points of this mod, it wouldn't be reasonable to expect him to document its impact on every conceivable reader in use now and in the future that people might use. So rather like for browsers, you need to work out what your visitors might use and familiarise yourself with them and their limitations and likely interactions with this mod.

craftzombie:

And you don't need to be rude. If you are getting that frustrated with our questions, maybe contributing things isn't for you.Andrew can sometimes get a bit hot under the collar. But hey, so do many of us who contribute regularly and feel that we're taking flack for users own installation mistakes, misunderstandings about what mods are supposed to do, or other things that are obviously out of our control, or just being asked the same question for the umpteenth time by somebody who clearly hasn't searched the thread.

I stress, craftzombie, that I'm not saying that this is the case here, just that this frustration tends to build up, and needs to be released from time-to-time. I guess you were in the wrong place when Andrew needed to release his.

Stepping back from that, Andrew has made a huge contribution to the mods available for Zen Cart - not only those with his name on, but also several that have been taken forward by other people building on his foundations. So even if he sometimes gets a tetchy at times, were to take your advice this community would be impoverished by his absence.

kuroi:

Although his readme can realistically be expected to cover the major points of this mod, it wouldn't be reasonable to expect him to document its impact on every conceivable reader in use now and in the future that people might use.

It also wouldn't be reasonable for me to be expected to read the manuals of every reader available to see if this mod is compatible with them. Instead of the whole RTFM statement, he could have just said that they weren't compatible. Its that kind of attitude that I'm sick of around here. We aren't all programmers. We don't know, so we come here to ask. The people who do know don't need to be so damn condescending.

kuroi:

Andrew can sometimes get a bit hot under the collar. But hey, so do many of us who contribute regularly and feel that we're taking flack for users own installation mistakes, misunderstandings about what mods are supposed to do, or other things that are obviously out of our control, or just being asked the same question for the umpteenth time by somebody who clearly hasn't searched the thread.

As someone who answers questions all the time, many of them the same questions over and over, I've never once felt the need to act like a jerk. Maybe its just me, but I understand that most of the people here are not programmers or even that proficient with HTML & CSS. My point in making that statement is that if you are even thinking about contributing something here, you should know that you ARE going to be asked questions. Its like the guy with the bad attitude working the drive-thru at McDonalds.... no one is forcing you to work there. If you are that unhappy to the point where you have to be a jerk to everyone, THEN DON'T WORK THERE. If you aren't ready for answering the same questions over and over, etc. then why bother? Do you really think people are going to read through pages and pages of forum posts? (I'm sure posts like this, clogging up the threads, doesn't help either, but you know.... I just HAD to reply.)

kuroi:

Stepping back from that, Andrew has made a huge contribution to the mods available for Zen Cart - not only those with his name on, but also several that have been taken forward by other people building on his foundations. So even if he sometimes gets a tetchy at times, were to take your advice this community would be impoverished by his absence.

Although I appreciate his work and the work of others, which I have stated many times and I have also donated, that doesn't give any mod contributor the right to take out frustrations on us. Buy a punching bag or go scream in your pillow. If thats the price I have to pay for a free mod, well... I'd rather pay money for real support without attitude problems and insults.

You know, I really really love Zen Cart. Even out of all of the paid carts I've seen, it is the best. Its just a shame that I have to be treated like the biggest moron on earth every time I come here to ask a question. (okay, not EVERY time, but many times.)

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 "<"
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 103, Column 151: document type does not allow element "link" here.
…in_page=rss_feed&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&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&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&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&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).

craftzombie:

If thats the price I have to pay for a free mod, well... I'd rather pay money for real support without attitude problems and insults.

Just in my own experience, I have gotten insults, condescention, and exasperation from plenty of paid support over the years. I think this is a condition of working with humans, not a condition of whether you pay the humans.

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 "<"
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 103, Column 151: document type does not allow element "link" here.
…in_page=rss_feed&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&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&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&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&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).

Andrew or others please help...

After upgrading to the latest version, I could not get my feeds to update. After taking a closer look, I noticed that the new products feed is main_page=rss_feed&feed=new_products. The problem is that the actual new products page is not new_products, but rather products_new. When I made this change in my browser, the feed updated. I have changed the link on my EZ-Page which lists all of my feeds, but.... what about the RSS icon in the address bar in Firefox (or in IE)? Are there other files that need to be changed? For instance, in includes\functions\extra_functions\rss_feed.php, there are many references to "new_products". Do they all need to be changed to "products_new"? What about the SQL? I don't know if I am barking up the wrong tree and these things don't matter, but I could not get my feed to update without changing it. Any thoughts?

craftzombie:

For instance, in includes\functions\extra_functions\rss_feed.php, there are many references to "new_products". Do they all need to be changed to "products_new"?

For anyone who is having the same trouble... not sure if this is what is supposed to be done, but I did it and it is working.... I went ahead and changed every instance of "new_products" to "products_new" in includes\functions\extra_functions\rss_feed.php and it corrects the problem with the RSS icon in the address bar.

But please, don't take my word for it. I am not an RSS expert and I'd rather have Andrew approve/disapprove of everything I am saying here before you go and mess anything up.

(there are also instances of it in includes\modules\pages\rss_feed\header_php.php, but I was reluctant to mess with it since the changes to the other file are working.)

craftzombie,

I'm not going to make the changes yet...but I did look to see if my products were updated on the products_new and "some" of the new ones are there....but not all of them....and they are taking a lot longer to update I noticed. So....I'm not quite sure it's an actual fix. For now I just delete the cache files that keep appearing in my root folder and it automatically updates my new_products feed

craft,

Just a quick glance.....look at the differences

new_products

products_new

It's actually skipped a few products in the products_new link