How do I get the data feeds to end up somewhere where google can retrieve them?
If I put a / for the directory it still ends up in httpdocs/var/files/1. How do I get it to write to straight to httpdocs?
How do I get the data feeds to end up somewhere where google can retrieve them?
If I put a / for the directory it still ends up in httpdocs/var/files/1. How do I get it to write to straight to httpdocs?
How do I get the data feeds to end up somewhere where google can retrieve them?
If I put a / for the directory it still ends up in httpdocs/var/files/1. How do I get it to write to straight to httpdocs?
You can specify full path to the httpdocs/ public_html there. The path depends on the server.
The easiest way to find it is to add the following code:
fn_print_r(dirname(__FILE__));
after this line:
require(dirname(__FILE__) . '/init.php');
in the index.php file. Then go to any store-front page. Full path will be displayed at the top
If I do that I get the same result as my hosting provider gave me i.e. /var/www/vhosts/xxx.co.uk/httpdocs, but if I put that path in it simply recreates the full path under the Private files directory.
It worked on our server. May be the issue is server or CS-Cart version related. Examination is required in any way
Is there anything else I can look at, is there a special character to use to force an absolute path instead of a relative one?
Is there anything else I can look at, is there a special character to use to force an absolute path instead of a relative one?
We suggest you to contact CS-Cart support team with this question
CS-Cart say the latest version will only ever export to /var/files/1 but as that's classed as 'Private Files' I don't see how Google will ever be able to pick it up.
The solution is to create an FTP user with a home directory of /httpdocs/var/files/1 then give google that ftp username and password and use the url ftp://example.co.uk/google_products.txt to get the file.
CS-Cart say the latest version will only ever export to /var/files/1
If that's the case, I wish this change had at least been made clearer on the feeds page; I was trying to figure out why the auto-script (calling it via a scheduled task call to PHP rather than the GUI) was no longer updating the google feeds file we'd specified (since the exact date we updated (#)) and even generating it manually via the GUI didn't make this obvious.
Perhaps it could add something to php-errors.log when it fails.
The solution is to create an FTP user with a home directory of /httpdocs/var/files/1 then give google that ftp username and password and use the url ftp://example.co.uk/google_products.txt to get the file.
That was one workaround I'd considered too, but I'd wanted to find out what the (apparent) problem with the permissions was first!
(#) Yes, for various reasons we'd not been able to update from 4.3.3 until recently, though to be fair I realised this was A Bad Thing and was unhappy about it...