Hello,

I have the plugin installed on our ZenCart site - it shows up properly on all of the pages but doesn't seem to generate the feed itself properly for anything except for the primary 'base' feed.

For example:

myzencart/index.php?main_page=rss_feed&feed=new_products

Shows a blank page, but the base rss_feed page shows the proper feed, ie:

myzencart/index.php?main_page=rss_feed

Any ideas why the feed wouldn't be working for any subcategories or other pages other than the base feed url?

craftzombie:

look in includes/templates/template_default/common/html_header.php. Once you make the changes, save the file in includes/templates/your_template/common/html_header.php so that it won't be overridden during a zencart upgrade. (your_template = the name of the template you are using)

I did that, thanks. It is now set correctly, though I am not sure what exactly it is supposed to do. Thanks.

elishama3:

I understand from reading the thread that this is due to spaces at the end of certain language files. I went through a whole bunch of them and deleted any spaces at the end, but there are so many I would love it if someone could narrow it down for me. Is it a space at the end of any language file, or certain types?

Thanks

I have taken out all the blank lines in all of my language files, all my sidebox files, and a few random others. Still getting the error message.

Any help here would be much appreciated.

Again, the error message is: XML Parsing Error: xml declaration not at start of external entity
Location: http://www.phoenixflightpublications.com/index.php?main_page=rss_feed&feed=products
Line Number 2, Column 1:<?xml version="1.0" encoding="iso-8859-1"?>

elishama3:

I did that, thanks. It is now set correctly, though I am not sure what exactly it is supposed to do. Thanks.

Now that it is installed correctly, in Firefox you should see the orange RSS icon in the address bar at the top of the browser. In IE, there should be an orange RSS icon next to your tabs on the right, underneath the address bar.

craftzombie:

Now that it is installed correctly, in Firefox you should see the orange RSS icon in the address bar at the top of the browser. In IE, there should be an orange RSS icon next to your tabs on the right, underneath the address bar.

Nifty! It is there!

Is there a way I can configure which feeds I want/don't want? I really only want to have one, maybe two types of feeds for the site.

elishama3:

Nifty! It is there!

Is there a way I can configure which feeds I want/don't want? I really only want to have one, maybe two types of feeds for the site.

When I first installed this mod, I figured out how to do that. I only wanted to use the New Products and Specials feeds and I was successful in removing the other ones. When I installed an updated version of the mod, I couldn't for the life of me remember where I made those changes. I haven't really had any time to look around in the files though. When I have time and figure it out, I'll let you know.

or if anyone else knows.....

BTW, I found two bugs in the includes/classes/rss_feed.php file:
lines 406-407 are:

$in[] = '@&(mdash);@i'; $out[] = '?;

$in[] = '@&(reg);@i'; $out[] = '?';
but they should be:

$in[] = '@&(mdash);@i'; $out[] = '?';

$in[] = '@&(reg);@i'; $out[] = '?';

and lines 429-430 are:

$st_in[] = '@<li>@i'; $st_out[] = "\n?.chr(160);

$st_in[] = '@<h\d>@i'; $st_out[] = "\n\n";
but they should be:

$st_in[] = '@<li>@i'; $st_out[] = "\n?.chr(160)";

$st_in[] = '@<h\d>@i'; $st_out[] = "\n\n";

hope this helps someone.

elishama3:

BTW, I found two bugs in the includes/classes/rss_feed.php file:
lines 406-407 are:

$in[] = '@&(mdash);@i'; $out[] = '?;

$in[] = '@&(reg);@i'; $out[] = '?';
but they should be:

$in[] = '@&(mdash);@i'; $out[] = '?';

$in[] = '@&(reg);@i'; $out[] = '?';

and lines 429-430 are:

$st_in[] = '@<li>@i'; $st_out[] = "\n?.chr(160);

$st_in[] = '@<h\d>@i'; $st_out[] = "\n\n";
but they should be:

$st_in[] = '@<li>@i'; $st_out[] = "\n?.chr(160)";

$st_in[] = '@<h\d>@i'; $st_out[] = "\n\n";

hope this helps someone.

the code is my file is....

$in[] = '@&(mdash);@i'; $out[] = '—';
$in[] = '@&(reg);@i'; $out[] = '®';

$st_in[] = '@<li>@i'; $st_out[] = "\n•".chr(160);
$st_in[] = '@<h\d>@i'; $st_out[] = "\n\n";

Well...I added a bunch of products yesterday...and then I deleted the RSS file that showed up in my root.....

Now my new products feed doesn't work at all.

Okay...let me start from the beginning and go to the end of this issue...maybe someone can tell me where I screwed up.

I installed 2.1.3 and it worked fine except it filled my root folder with the RSS_(randomnumbers) files....

I saw that a_berezin created an upgrade. Colemanpa said that it fixed the issue for him....so I downloaded the upgrade...overwrote the files and ran the 2.1.3_upgrade file. I got an SQL error.

I ran the 2.1.4 Full install .sql file as Colemanpa said, it seemed to work fine, however I was wrong. It didn't update the new_products feed. I noticed that there were RSS_(randomnumbers) files back in my root directory. I deleted them and the new_products feed updated.

Last night I deleted them again to get the new_products feed to update again, however...instead it just deleted EVERYTHING from the new_products feed. I uninstalled 2.1.4 (deleted all the files and ran the uninstall.sql file)

I reinstalled 2.1.4 and it didn't fix it at all. So I decided to go back to 2.1.3 and that's not even working now. So now I've uninstalled 2.1.3 and I've reinstalled 2.1.4....

I'm not a coder whatsoever, but I'm assuming there is something that got screwed up when I tried to upgrade the first time. I backed my database up back then...but since then I've added a bunch of new products and some new customers....I don't want to lose all of that work. What can I do to fix this?

For now I've changed the default feed to Specials because any feed with the word products in it (new_products, products) will not work.

NFM:

For now I've changed the default feed to Specials because any feed with the word products in it (new_products, products) will not work.

This is the link to my New Products feed. Take a look at the source code...I think there's something wrong in there.

NFM:

This is the link to my New Products feed. Take a look at the source code...I think there's something wrong in there.

I just tested your New Products feed in Google Reader and it works for me....

craftzombie:

I just tested your New Products feed in Google Reader and it works for me....

I'm getting a blank page. It's also not updating at any of the sites that I send the feed to.

I just tested it in Google Reader too...and oddly...it IS working there. But nowhere else that I want it to work...lol

Got it! Thanks to Microsoft...lol...Internet Explorer told me what the problem was...and as I figured it was my fault. One of my products had an invalid character that was screwing up the xml....apparently Google Reader was the only thing having no issues with it.

Hi,

Really grateful for this contribution, thank you.

I do have a few validation errors I need help with:

Line 111, 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 112, 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 113, 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 114, 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 115, 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).

Thanks in advance..

Line 111, 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 112, 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 113, 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 114, 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 115, 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).

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.

Quick bugfix! Run this sql

UPDATE configuration SET set_function=NULL WHERE configuration_key = 'RSS_CACHE_TIME';

vitalwares:

I do have a few validation errors I need help with:
Use last version Google Analitics Integration module.

a_berezin:

Use last version Google Analitics Integration module.

Hi Andrew,

Not sure what this has to do with Google analytics, these are errors related to the RSS feed contribution but I I have installed the latest google analytics and
now I have new errors :(

Please look at this post in the analytics forum (also still have a few validation errors with the RSS code):

http://www.zen-cart.com/forum/showpost.php?p=526880&postcount=379

Regards,
Prashant.