Jump to content


Hosting Developers Payment Shipping Accounting Templates Marketing Books

Our Partners


Latest News: (loading..)

- - - - -

Contribution Tracker

Started by lildog, Jan 21 2007 09:34 PM

  • Please log in to reply
259 replies to this topic

#221   yaoi

yaoi
  • Members
  • 32 posts
  • Real Name:TJ

Posted 15 April 2009 - 06:23 AM

View Postalba, on Mar 31 2009, 12:26 AM, said:

actually i stand corrected... its stopped working again with the same error :(

It appears the rsscache/contrib_rss.html file causes the problem

It gets deleted by the script and is not re-written

I manually went in and recreated a blank contrib_rss.html file and chmod it to 777 again and the admin page loads again

only problem is as soon as i try and add or edit it deletes that file and we are back to square one again with the same error


i did the same .. and am also having the same problem. did you solve it and if so .. how

#222   Clau123

Clau123
  • Members
  • 90 posts
  • Real Name:Claudia
  • Gender:Female
  • Location:Netherlands

Posted 15 April 2009 - 09:19 AM

View Postkbking, on Nov 27 2008, 01:28 PM, said:

Hi,

Thanks for all the work you put into this useful contribution!

I installed the latest build today of 26 Nov 2008.

I'm on php 5 and MySQL 5.

fopen is not allowed.

curl is enabled.

allow_call_time_pass_reference = on.

I guess these settings would qualify for a successful install, yet I get an error message from admin/contrib_tracker.php saying: could not open XML input

I have almost the same thing but then from the catalog. It worked perfect with me, but since 10 april 2009 it suddenly stopped. I started getting mails from Uptime@alal.com that they couldn't reach catalog/contrib_tracker anymore. And also the mail from my shop with could not open XML input

I checked the rsscache and it's still on writing.

I do get an admin page, where I can see the contributions. The rss feed from OScommerce is working.

My versions:
Database version : MySQL 5.0.77
PHP Version: 5.2.9-1 (Zend: 2.2.0)

I don't know what's wrong. Someone any idea's?

#223   SteveDallas

SteveDallas
  • Members
  • 720 posts
  • Real Name:Glen
  • Gender:Male
  • Location:Alabama, US

Posted 24 May 2009 - 09:21 PM

I haven't been using the cron job and wasn't subscribed to this topic, so I missed all the recent problems that people have experienced.  I have started using the cron job and have made some updates to catalog/config_tracker.php that I will detail below.

The XML errors appear to be due to something in the RSS feed from osCommerce, so I'll have to wait until we get some bogus data in the feed again.  If anyone saved a copy of their rsscache/contrib_rss.html file when they were getting errors, please send me a PM because I'd like to have a look at it.  It's just a local copy of the RSS feed from osC, so there isn't any private data in it.

I discovered independently the problem that alba described on 30 Mar where the local cache of the RSS feed wasn't being created (references to DIR_WS_CATALOG instead of DIR_FS_CATALOG) and fixed that.  I also added a little bit of HTML to make the page output conform to the HTML 4.01 Transitional DTD.  (Nobody cares about this bit, but I'm obsessive about details.)  Lastly, I cleaned up the notification message and created a configuration key for it.  The first time you run the new version of catalog/contrib_tracker.php, it will create a new item in Configuration->E-Mail called "Contrib Tracker Notification email" with a default value of 'false'.  Set it to 'true' to get email notifications sent to the store owner.  Editing of the file is no longer necessary.

The new version will be uploaded shortly as v1.7.15.

--Glen

#224   decapper

decapper
  • Members
  • 102 posts
  • Real Name:John Howard
  • Gender:Male
  • Location:Australia

Posted 26 May 2009 - 11:18 AM

No update docs from v1.7.14 to v1.7.15

Thanks

#225   SteveDallas

SteveDallas
  • Members
  • 720 posts
  • Real Name:Glen
  • Gender:Male
  • Location:Alabama, US

Posted 26 May 2009 - 01:16 PM

View Postdecapper, on May 26 2009, 06:18 AM, said:

No update docs from v1.7.14 to v1.7.15

Thanks

I didn't create a line by line change file for this version.  The only file changed is catalog/contrib_tracker.php.  

--Glen

#226   oldschoo

oldschoo
  • Members
  • 163 posts
  • Real Name:beth marquardt

Posted 16 June 2009 - 01:46 PM

I installed the new update 1.7.15 but I am still getting the xml error.  XML error: not well-formed (invalid token) at line 127

In the rsscache/contrib_rss.html this is what is shown after the error:  
 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>302 Found</title>
</head><body>
<h1>Found</h1>
<p>The document has moved <a href="http://feedproxy.feedburner.com/osCommerce_Contributions?format=xml">here</a>.</p>
</body></html>

This site is on MS2.2

I have another site that is rc2 and I get the same error message:  XML error: not well-formed (invalid token) at line 127, but nothing in the rsscache file.

#227   Clau123

Clau123
  • Members
  • 90 posts
  • Real Name:Claudia
  • Gender:Female
  • Location:Netherlands

Posted 21 July 2009 - 08:57 AM

My host updated to php version 5.2.10. Since then I get the following warning above the contribution tracker:

Quote

Warning: Call-time pass-by-reference has been deprecated in D:\www\goodlivesbeads.nl\www\winkelen2\catalog\admin\includes\classes\rdf_class.php on line 344

Line 344 on rdf_class.php shows:

Quote

xml_set_object($this->xml_parser,&$this);

I can't update the status of the contribs anymore when I'm editing them (with the 0 or 1 nrs  in the editing . I can only click the green or red dots in the contrib listing.
Maybe that's because of the call-time error.

Who knows how I can solve this problem?

#228   Clau123

Clau123
  • Members
  • 90 posts
  • Real Name:Claudia
  • Gender:Female
  • Location:Netherlands

Posted 21 July 2009 - 09:07 AM

I think I solved my problem.

I googled it again, but now with the line that was giving me the trouble. The solution that I found was:

Change:

Quote

xml_set_object($this->xml_parser,&$this);

to

Quote

xml_set_object($this->xml_parser,$this);

So deleting the & before $this

The warning is gone and I can edit again.

Edited by Clau123, 21 July 2009 - 09:08 AM.

#229   necrovore1984

necrovore1984
  • Members
  • 8 posts
  • Real Name:Lee

Posted 27 July 2009 - 12:26 AM

When going to admin/contrib_tracker.php i am getting the dreaded:
could not open XML input

I have the following settings
PHP Version 5.2.10
cURL support enabled
cURL Information libcurl/7.15.5 OpenSSL/0.9.8c zlib/1.2.3 libidn/0.6.5
allow_url_fopen Off Off

Tried installing versions 1.7.16 and 1.7.15. If anyone has a solution let me know.

#230   blr044

blr044
  • Members
  • 1,009 posts
  • Real Name:Bennett
  • Gender:Male
  • Location:USA

Posted 14 August 2009 - 05:50 PM

Get this error also:

XML error: not well-formed (invalid token) at line 92

have tried 1.7.15 and 1.7.16

This is line 91 and 92:

		if (extension_loaded('curl')== 1 && file_exists(DIR_WS_CATALOG. 'rsscache/contrib_rss.html')){
		unlink(DIR_FS_CATALOG. 'rsscache/contrib_rss.html');

Location of the file is:  /public_html/rsscache/contrib_rss.html

Bennett

#231   blr044

blr044
  • Members
  • 1,009 posts
  • Real Name:Bennett
  • Gender:Male
  • Location:USA

Posted 18 August 2009 - 02:50 PM

Has anyone been able to get this contribution to work?  Still getting the error even after searching google and through support forum.

XML error: not well-formed (invalid token) at line 216

#232   SteveDallas

SteveDallas
  • Members
  • 720 posts
  • Real Name:Glen
  • Gender:Male
  • Location:Alabama, US

Posted 28 August 2009 - 09:03 AM

View Postblr044, on Aug 18 2009, 09:50 AM, said:

Has anyone been able to get this contribution to work?  Still getting the error even after searching google and through support forum.

XML error: not well-formed (invalid token) at line 216

It always works on some servers (1&1, for instance) and on others, it fails only when there are accented characters in the content of the RSS feed.  This seems to be caused by a disagreement between the character set declaration in the header of the file and the actual content.  (Header contains 'encoding="ISO-8859-1"', while accented characters in the article titles are encoded as UTF-8.) Some PHP XML parsers choke on this and cause the error.  

A "correct" fix would be to repair the feed so that the article titles are either (a) encoded with ISO 8859-1, or (b) the accented characters are converted to HTML entities, as is already done with the article descriptions.  I wrote to hpdl a while back on this, but never received a response, and the feed is still broken.

Because I only have access to a server that always works, it has been difficult to create a workaround to this problem.  If someone can give me read/write access to a test installation on a server that is known to fail, I can probably come up with a fix.  PM me if you can do so.

--Glen

Edited by SteveDallas, 28 August 2009 - 09:07 AM.

#233   necrovore1984

necrovore1984
  • Members
  • 8 posts
  • Real Name:Lee

Posted 05 September 2009 - 02:47 AM

View PostSteveDallas, on Aug 28 2009, 09:03 AM, said:

It always works on some servers (1&1, for instance) and on others, it fails only when there are accented characters in the content of the RSS feed.  This seems to be caused by a disagreement between the character set declaration in the header of the file and the actual content.  (Header contains 'encoding="ISO-8859-1"', while accented characters in the article titles are encoded as UTF-8.) Some PHP XML parsers choke on this and cause the error.  

A "correct" fix would be to repair the feed so that the article titles are either (a) encoded with ISO 8859-1, or (B) the accented characters are converted to HTML entities, as is already done with the article descriptions.  I wrote to hpdl a while back on this, but never received a response, and the feed is still broken.

Because I only have access to a server that always works, it has been difficult to create a workaround to this problem.  If someone can give me read/write access to a test installation on a server that is known to fail, I can probably come up with a fix.  PM me if you can do so.

--Glen

I beg to differ with you. I have been using 1and1 for my sites for six years and have never been able to get this contribution to work. Always gives the error "could not open XML input".

#234   SteveDallas

SteveDallas
  • Members
  • 720 posts
  • Real Name:Glen
  • Gender:Male
  • Location:Alabama, US

Posted 05 September 2009 - 05:00 AM

View Postnecrovore1984, on Sep 4 2009, 09:47 PM, said:

I beg to differ with you. I have been using 1and1 for my sites for six years and have never been able to get this contribution to work. Always gives the error "could not open XML input".

Then you're dealing with a different problem from the one that others are having.  I run it daily on 1and1.  The others have intermittent problems opening the page; it fails to load when there are accented characters in the contribution titles.

Is your store running under PHP5?  I was able to duplicate your issue on 1and1 when I set my test store to use PHP5.  The workaround for this is to create a contrib_rss.html file as outlined in the installation instructions.  There are some issues with the code in contrib_tracker that decides whether to open the RDF feed as a file or create a local cache, so I am uploading a fix shortly.  This error occurs because PHP5 is usually configured to disallow opening a URL as a file.  This is the case with 1and1.

--Glen

#235   SteveDallas

SteveDallas
  • Members
  • 720 posts
  • Real Name:Glen
  • Gender:Male
  • Location:Alabama, US

Posted 05 September 2009 - 11:57 PM

I have just posted v1.7.17 of Contribution Tracker with the following changes:

Version 1.7.17
Revised installation instructions - rsscache directory no longer used
+ Rewrote XML parser - no longer uses rdf_class.php
+ Rewrote RDF file handling code - no longer caches feed in contrib_rss.php, works with PHP5 as if cURL is available
+ Revised email notification now only reports once per update, not every time the cron job is executed
+ three files no longer needed:
   /catalog/includes/classes/rdf_file.php
   /catalog/includes/functions/contrib_tracker.php
   /admin/includes/classes/rdf_file.php

This version should fix both the intermittent error of corrupt XML files when there are accented characters in the names of some of the contributions, as well as problems associated with PHP5 when allow_url_fopen is set to 'off', which is the default setting.  As a result of this, I no longer cache the feed to the local server, which may slow some users down when doing a lot of updates on the Contrib Tracker admin page.  I will probably change this to cache the feed for up to an hour when the page is reloaded.

I also made changes that make the email notifications both less annoying (only one message per update, instead once each time the cron job is run while the contribution is on the list) and more useful (name and link of updated contribution in message body).

As usual, please let me know of any problems you experience with this release.  

--Glen

Edited by SteveDallas, 06 September 2009 - 12:01 AM.

#236   Clau123

Clau123
  • Members
  • 90 posts
  • Real Name:Claudia
  • Gender:Female
  • Location:Netherlands

Posted 10 September 2009 - 02:31 PM

Hello Glen,

I updated to version 1.1.17 and everything seems to work fine, So thank you, because this is a very handy Contribution.

However I have 1 question. Every time I update a contribution and click on "Last integrated in store" :today, also the "last official update" changes into the same date as the date I did the update.  For example I have updated this Contribution today, so now I see:
Last integrated in store: 2009-09-10 15:00:00
Last official update: 2009-09-10 15:54:27

While the official update dat is: 2009-09-05

Do you have this too? If you have, is it possible to change this? It would be nice if you can see the official update date of the Contrib after you update it into your store.

greetings Claudia

#237   SteveDallas

SteveDallas
  • Members
  • 720 posts
  • Real Name:Glen
  • Gender:Male
  • Location:Alabama, US

Posted 10 September 2009 - 03:19 PM

View PostClau123, on Sep 10 2009, 09:31 AM, said:

Hello Glen,

I updated to version 1.1.17 and everything seems to work fine, So thank you, because this is a very handy Contribution.

However I have 1 question. Every time I update a contribution and click on "Last integrated in store" :today, also the "last official update" changes into the same date as the date I did the update.  For example I have updated this Contribution today, so now I see:
Last integrated in store: 2009-09-10 15:00:00
Last official update: 2009-09-10 15:54:27

While the official update dat is: 2009-09-05

Do you have this too? If you have, is it possible to change this? It would be nice if you can see the official update date of the Contrib after you update it into your store.

greetings Claudia

Claudia,
You're correct.  I'll look into this and fix it shortly.

--Glen

#238   Clau123

Clau123
  • Members
  • 90 posts
  • Real Name:Claudia
  • Gender:Female
  • Location:Netherlands

Posted 24 September 2009 - 09:46 AM

Since this morning I get this error:

Warning: Invalid argument supplied for foreach() in catalog\admin\contrib_tracker.php on line 119

Now i don't see the latest OSc updates anymore

I asked my provider, but they say they didn't change anything

Anyone else experiencing this thing?

#239   Clau123

Clau123
  • Members
  • 90 posts
  • Real Name:Claudia
  • Gender:Female
  • Location:Netherlands

Posted 24 September 2009 - 10:31 AM

I tried some thing that I found on other forums for other Contribs (see my blog) I don't write them down here, because I don't know if I did the right thing.

What I see now is after "Latest OSC Contributions" is: ERROR: Could not open RDF feed

#240   SteveDallas

SteveDallas
  • Members
  • 720 posts
  • Real Name:Glen
  • Gender:Male
  • Location:Alabama, US

Posted 24 September 2009 - 12:20 PM

View PostClau123, on Sep 24 2009, 05:31 AM, said:

I tried some thing that I found on other forums for other Contribs (see my blog) I don't write them down here, because I don't know if I did the right thing.

What I see now is after "Latest OSC Contributions" is: ERROR: Could not open RDF feed

"ERROR: Could not open RDF feed" is "normal" if we cannot get the file from Feedburner for any reason.

I read your blog entry.   Can you post a reference to where you found those changes?

Thanks,
Glen
Back to Add-Ons Development


  1. osCommerce Support Forum
  2. → osCommerce Online Merchant v2.x
  3. → Add-Ons
  4. → Add-Ons Development
  5. Privacy Policy
  6. Forum Rules ·