Hi David,
Hope all is well,
Wondering if you might be able to help.
We have set up a cron job to import the datafeeds, we're using the following in fetch.sh :
-----------------------------------------------------
{code saved}
------------------------------------------------
The feeds are being registered in the admin are - but the data files are empty.
Here is the cron command:
cd /home/mydomain.com/public_html/custom-includes/;/bin/sh fetch.sh
Any idea what is happening here?
Many Thanks
Stew
Hi David,
Thanks for the reply, I've deleted all of the files within the /feeds/ folder, and then re-run the cron job.
The same thing happens, the files appear in the /feeds/ folder but are empty.
When I visit the feed urls in a browser and download the data - all the data seems to be there.
Any ideas?
Many Thanks
Stew
Hi Stew,
Are the feed(s) causing the problem being unzipped or ungzipped (as per the job configuration)?
Cheers,
David.
--
PriceTapestry.com
Hi David,
Am not entirely sure to be honest - is there anywhere that gives an output of the process?
Many Thanks
Stew
Hi Stew,
It's whether you have / need it enabled in the job configuration - click Edit alongside one of your jobs and see if Unzip? is set to Yes or No..
Could you also copy one of your feed URLs into your reply (i'll remove before publishing) and i'll check it out on my test server...
Thanks;
David.
--
PriceTapestry.com
Hi David,
Im using cPanel & WHM 11.32 for Linux for the cron job.
When I click edit next to it I only have options to change the 'command':
cd /home/example.com/public_html/custom-includes/;/bin/sh fetch.sh
and then just hour/minute/day/week.
Feed URL is:
{link saved}
Many Thanks
Stew
My apologies Stew I had got cross-threaded! Please could you email me a copy of your fetch.sh and i'll check it all over - sorry about that!
Thanks,
David.
--
PriceTapestry.com
Hello Stew,
One reason i've seen for what you describe on more than one occasion is where files of the same name (uncompressed) already exist in the /feeds/ folder but having been created under a different system user. This could occur if the feeds were initially uploaded manually for the first time before setting up automation.
Try deleting the files completely to make sure that any files being downloaded and decompressed by fetch.sh do not exist in the /feeds/ folder before running for the first time - that might be all it is...
Cheers,
David.
--
PriceTapestry.com