Jump to content

sitemap.xml


Recommended Posts

Can't get the sitemap.xml working via the module gsitemap

 

Using prestashop 1.5.4.1 and install the gsitemap module and click on generate sitemap and get the following error:

An error occured while trying to check your file permissions. Please adjust your permissions to allow PrestaShop to write a file in your root directory.

 

If I create the file myself and use 755 en 777 permissions still no go, also set this:

chown apache:apache

Link to comment
Share on other sites

are you running a multishop?

 

for multishop sitemap.xml will point to new/created files sitemap-1.xml sitemap-2.xml etc...

 

for non-multishop then there is no sitemap.xml, it will be something like 1_index_sitemap.xml which will point to another file.

 

you should contact your hosting company if you are unable to have your website create files in root directory

Link to comment
Share on other sites

this is very odd...and somewhat complicated...in that it's more of an issue with your OS than PS. You should check to see how your website is defined in say linux, user/owner etc...I've seen some websites (not often) whose websites did not run as user of the domain...they could not create any files outside of using ftp...they were a mess because they could not even run a module install...

 

I don't know you particular setup...you will need to use ssh to burrow into this domain to check the file permissions/users/groups/owners...these are best learned obviously in either a linux or windows (please tell me not windows) forum.

Link to comment
Share on other sites

No windows indeed :), it's a centos 6 server.

I have installed some modules that I have copied and they are owned by root. all the default files/folders are owned by apache

But even if I set the sitemap.xml as chown apache or chmod 777, still no go.

 

Strange thing is that via the advanced parameters -> configuration information its says when the file is not present:

  • Set write permissions for the "sitemap.xml" file. And this notification disappears when i manually create the sitemap.xml, so it detects the file is present but cannot use it.

Link to comment
Share on other sites

omg...that is the most convoluted installation method I have ever seen...

 

do you have ftp?

 

if so and you are just installing ps, then delete the files in the web space using your hosting control panel and then the db using phpmyadmin, then create a db using phpmyadmin (note the db connect/name/pwd

 

then simply download the latest ps, unzip it, using ftp upload it.

 

navigate to your root files and run the ps install...

 

btw: when I reviewed the video, I noticed that (as you said above) chown -r apache, this IMHO should have been chown -r yoururl:yoururlgroup:path to your root files...

Link to comment
Share on other sites

it is not the easiest way I admit :)

but i dont have cpanel just shell and winscp.

 

And my shop is already populated with products and all, so dont want to reinstall everything.

 

I will check the chown settings, but hopefully this will not brake something else

Link to comment
Share on other sites

let us know how you get on....

 

this is the code I use in a shell exec that changes the ownership post copy..

 

$cmd_grp = 'chown -R '.$etiendaurl.':'.$group.' '.$doc_root.'/httpdocs/*';

 

Works like a charm.

 

you should consider getting cpanel/plesk or some other hosting control panel. SSH is so 70's. :)

Link to comment
Share on other sites

yeah well I figured only for the setup you use cpanel, once PS runs you only need the admin part of PS and leave the server be.

So why spent money on plesk (i'm dutch :) )

 

I dont understand your shell script, but I was wondering if I create my sitemap.xml via http://www.xml-sitemaps.com/ once a while, will this have the same result for google?

Link to comment
Share on other sites

you are not saving any money well of course assuming your time is worth something....

 

anyway...I don't see why one would set their webspace permissions to apache as your website does not run 'as' apache, but as an application on top of apache...

 

so it goes...

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...