Page 1 of 1

Unable to get SitemapMgr working

Posted: Mon Mar 01, 2021 4:03 pm
by Robin01
So I believe the issue I'm having is likely an easy fix and hoping someone could help.
I've been following this guide https://cmscanbesimple.org/blog/how-to-use-sitemapmgr to setup the sitemapmgr for a client's site.

Server is a Apache 2.4 + PHP 7.2 environment, the site itself is cmsms version 2.2.13

1. I've added the following lines to config.php

Code: Select all

$config['permissive_smarty'] = 1;
$config['root_url'] = 'https://www.blabla.com/';
2. I've uploaded SitemapMgr-1.7.xml to the modules manager and installed it.

3. I go to the Site Admin -> SitemapMGR page and select the pages tab and submit the standard sitemap which is already made.
However I encounter an error saying :
Sitemap file has not yet been created.
First create a new module template as described in the documentation.
Update the Name and Module Tag as you need it!
A new sitemap(-index) file will be created after submit.
Image of admin SitemapMGR page: http://prntscr.com/10aiw5m

Now there are some older guides that seem to mention the need to create the template files for the SitemapMGR yourself, however they already seem to have been created as see in the following link: http://prntscr.com/10aj37q and the template itself here: http://prntscr.com/10aj4i3 .

Now my main question is what am I doing wrong ?
The sitemap won't publish because it claims it's missing a template that (as far as I can see) is clearly there.

Re: Unable to get SitemapMgr working

Posted: Mon Mar 01, 2021 5:23 pm
by DIGI3
I'm guessing it's having trouble writing the file, and the message about the template might be a red herring. Check your php error logs (check in /admin too if you have per-directory error logs), the CMSMS Admin log, and the system info page to see if anything jumps out.

Re: Unable to get SitemapMgr working

Posted: Mon Mar 01, 2021 7:08 pm
by Rolf
Are the robots.txt and sitemap.xml files created?

Re: Unable to get SitemapMgr working

Posted: Thu Mar 04, 2021 10:42 am
by Robin01
I am unable to detect any meaningful error in the php error / admin logs.
The main sitemap.xml IS generated, it's just pages one that isn't.

Re: Unable to get SitemapMgr working

Posted: Thu Mar 04, 2021 12:10 pm
by Rolf
It may be a folder/file permission thing in the /assets folder.
Or some error occurs when generating the pages sitemap.
Otherwise I am out of ideas...

Re: Unable to get SitemapMgr working

Posted: Thu Mar 04, 2021 6:18 pm
by Rolf
I might have found a site with similar issues, will be back if I have some news

Re: Unable to get SitemapMgr working

Posted: Thu Mar 04, 2021 7:28 pm
by Rolf
@Robin01
Can you check if the /assets/sitemaps/ folder is created and still present

Re: Unable to get SitemapMgr working

Posted: Fri Mar 05, 2021 12:34 pm
by Robin01
Yes the folder is created and present.

Re: Unable to get SitemapMgr working

Posted: Fri Mar 05, 2021 3:32 pm
by Rolf
Robin01 wrote: Fri Mar 05, 2021 12:34 pmYes the folder is created and present.
Okay, then I really don't know...
The one site where I could reproduce it, had that folder missing. I did a fix for that in SVN. But it won't help you.

Try to uninstall the module, delete the files and reinstall it. Maybe something went wrong there in your install.

Re: Unable to get SitemapMgr working

Posted: Mon Mar 08, 2021 7:12 pm
by Rolf
@Robin01
Your hosting has cPanel?
Check Metrics >> Errors section >> "Latest web server error log messages"
Something like "access_compat:error" and "AH01797: client denied by server configuration" there?

Re: Unable to get SitemapMgr working

Posted: Wed Mar 10, 2021 1:40 pm
by Rolf
the site itself is cmsms version 2.2.13
In CMSMS 2.2.15 we did fixes for HTTP2 in cms_http_request. SitemapMgr uses this too. Might be also related to your problem. Try to upgrade cms to latest and try again!

Re: Unable to get SitemapMgr working

Posted: Mon Mar 15, 2021 1:07 pm
by Robin01
Thank you for the advise, we will try updating first.
The environment it currently runs on does not offer direct error logs although I can turn error_reporting on client side, this does not seem to yield any strange permission related errors.

Will report back after update.