Generating a Sitemap

Permalink 1 user found helpful
Hi All,

Could really do with some help from you guys! When I run installed jobs, 2 work fine, but the other (Generate Sitemap File) gives me this error:

The file /kunden/homepages/20/d451766558/htdocs/app451766540/sitemap.xml is not writable

Because of this, I have no sitemap and 'Google doesn't know me very well'

Can anyone advise?? (in simple terms if possible, because I'm very new to all of this)

Many thanks

 
Arequal replied on at Permalink Reply
Arequal
I thought it was a subforum for Jobs, not for technical issues
JohntheFish replied on at Permalink Reply
JohntheFish
Well, there are Jobs and there are c5 Jobs. May as well keep going here.

The problem is that your c5 root level foleder (where index.php is) is not writeable by the web/apache linux 'user' (not the same as a c5 user). Check the permissions on that folder. 0755 is usually OK (don't risk 777 as that could open up big security holes).

You should be able to change the permissions with an FTP client. On 1&1 you may also be able to do it with their webspace explorer (not sure).
torbaytesting replied on at Permalink Reply
Hi John,

Many thanks for your response. Even though your reply was succinct, it's still beyond me I'm afraid. I've been ferreting around on my c5 dashboard, but I can't find any reference to index.php, so I'm unable to check permissions, less still change them.

Had a look at the 1 and 1 webspace explorer as you suggested but, if anything, that was even more baffling. Huge number of files with various 3 digit permission codes, but no trace of the elusive index.

If you can find a couple of minutes to give me a very simple steer I'd be obliged.
JohntheFish replied on at Permalink Reply
JohntheFish
You won't find it in the c5 dashboard.

In the webspace, via either the webspace explorer or an ftp program, the directory you want will be very near the top of the tree (if not at the top, it all depends on your install).

The directory will contain subdirectories for all the parts of concrete5 and your site.
/blocks
/config
/concrete
/files
/updates
(and lots more)

Also in this directory will be index.php, and it is this directory that you need the 755 permissions on. To do that, once you have found the directory, go up into the containing directory (its parent), select the directory you just came from, and do whatever is needed to change the permissions (which depends on what you are using to view it)
torbaytesting replied on at Permalink Reply
Many thanks to John and Tooq, your advice is much appreciated.

Unfortunately (due to an unrelated issue) I've had to go back to square one and recreate my site from scratch. I will be referring back to this thread once I've rebuilt, as I expect I will encounter the same issue.

Thanks again gentlemen.
TooqInc replied on at Permalink Reply
TooqInc
I had a similar issue on a site just last week, but the permission were not the issue. I ended up having to recreate the sitemap.xml file and remove the old one. I didn't report it at the time as I thought it was just a one off issue.

Anyways, the site has been working fine since. This might be an issue with the latest release (5.6.1.2).

The fix was pretty simple:
1. Log into Cpanel and navigate to your site's file structure
2. Rename "sitemap.xml' to 'sitemap2.xml'
3. Create a new file called "sitemap.xml" and set the permissions to 755
4. Run the automated jobs from the C5 dashboard
5. Viewhttp://yoursitename.com/sitemap.xml...
6. If the sitemap has been generated, go back to Cpanel and delete the old sitemap ("sitemap2.xml")

If you need some more help, send me a PM with a name, email address, and phone number.
jshannon replied on at Permalink Reply
jshannon
Still sounds like a permission issue to me...

But this is a much better way to fix it than making / writable.
torbaytesting replied on at Permalink Reply
Many thanks to John and Tooq, your advice is much appreciated.

Unfortunately (due to an unrelated issue) I've had to go back to square one and recreate my site from scratch. I will be referring back to this thread once I've rebuilt, as I expect I will encounter the same issue.

Thanks again gentlemen.