Page 1 of 2

Problem with SitemapMgr – has somebody same problem?

Posted: Fri Aug 18, 2017 9:28 am
by reinhardmohr
Hi,
first I wanted to thank Rolf for making the module SitemapMgr. It is really great and helpful. But after upgrading my site to CMSms 2.2.2 and SitmapMgr to 1.5.1 I experienced problems.
In the forge I issued a bug report but Rolf, the developer, couldn't reproduce the problem and suggested to post the problem in the forum – maybe someone could have the same problem? And provide additional data?
Thanks for helping!

Here is the problem:
SitemapMgr worked very well until I updated it to the latest version (I think from 1.3.1, but not sure). Then I got an error report from Google that my sitemap was missing. Now I looked it up and got an error
report from SitemapMgr with a big yellow panel that said
"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."
I uninstalled and reinstalled but couldn't get it to work. I tried the module tag as "{Navigator template='cms_template:Sitemap Pages'}" and as "{cms_module module='Navigator' template='cms_template:Sitemap Pages'}" but it didn't work.
Then I switched back to SitemapMgr 1.4 – this worked – and then updated again. Same error!
Now I am back to v 1.4 and it works – but 1.5.1 does not work. Here is the error panel:
Bildschirmfoto 2017-08-16 um 13.58.09.png
Thanks for helping

Reinhard

Here is my configuration:
----------------------------------------------
Cms Version: 2.2.2
Installed Modules:
AceEditor2: 1.05
AdminSearch: 1.0.4
AdvancedContent: 0.9.4.3
CGBlog: 1.14.4
CGExtensions: 1.56.2
CGExtensions: 1.56.2
CGJobMgr: 1.3.6
CGSharedContent: 1.0.1
CGSimpleSmarty: 2.1.6
CMSContentManager: 1.1.5
CMSMailer: 6.2.14
CmsJobManager: 0.1
CustomContent: 1.10
DesignManager: 1.1.3
ExaExternalizer: 0.6
FileBackup: 0.5
FileManager: 1.6.3
FilePicker: 1.0
FormBuilder: 0.8.1.6
FrontEndUsers: 2.5.1
Gallery: 1.4.1
JM_Forum: 1.0.27.b
JQueryTools: 1.4.0.3
LISE: 1.3.1
LISEReinhardsAkkordeon: 1.3.1
LISESEOAkkordeon: 1.3.1
MenuManager: 1.50.3
MicroTiny: 2.2
ModuleManager: 2.1.1
MysqlDump: 1.4.0
Navigator: 1.0.7
News: 2.51.2
Quotes2: 1.1.0
Search: 1.51.2
Showtime2: 3.5.4
SitemapMgr: 1.4
TemplateExternalizer: 2.1.6
ThemeManager: 1.1.8
TinyMCE: 3.2-beta3
btAdminer: 4.2.5

Config Information:
php_memory_limit:
max_upload_size: 50000000
url_rewriting: mod_rewrite
page_extension: .html
query_var: page
auto_alias_content: true
locale: de_DE.UTF-8
set_names: true
timezone: Europe/Berlin
permissive_smarty: true

Php Information:
phpversion: 7.1.6
md5_function: An (Ja)
json_function: An (Ja)
gd_version: 2
tempnam_function: An (Ja)
magic_quotes_runtime: Aus (Nein)
E_ALL: 4433
E_STRICT: 0
E_DEPRECATED: 0
test_file_timedifference: No time difference found
test_db_timedifference: No time difference found
create_dir_and_file: 1
memory_limit: 128M
max_execution_time: 180
register_globals: Aus (Nein)
output_buffering: 0
disable_functions:
open_basedir:
test_remote_url: Erfolgreich abgeschlossen
file_uploads: An (Ja)
post_max_size: 51M
upload_max_filesize: 50M
session_save_path: /tmp (1777)
session_use_cookies: An (Ja)
xml_function: An (Ja)
xmlreader_class: An (Ja)
check_ini_set: An (Ja)
curl: An

Performance Information:
allow_browser_cache: An (Ja)
browser_cache_expiry: 60
php_opcache: An (Ja)
smarty_cache: Aus (Nein)
smarty_compilecheck: Aus (Nein)
auto_clear_cache_age: An (Ja)
Server Information:
Server Software: Apache
Server Api: cgi-fcgi
Server Os: Linux 4.4.71-9.1.x86_64 An x86_64
Server Db Type: MySQL (mysqli)
Server Db Version: 5.5.52
Server Db Grants: „Alles gewähren“-Anweisung gefunden, die als geeignet scheint

Permission Information:
tmp: /pages/81/e2/d0013149/home/htdocs/tmp (0755)
tmp_cache: /pages/81/e2/d0013149/home/htdocs/tmp/cache (0755)
templates_c: /pages/81/e2/d0013149/home/htdocs/tmp/templates_c (0755)
modules: /pages/81/e2/d0013149/home/htdocs/modules (0755)
uploads: /pages/81/e2/d0013149/home/htdocs/uploads (0755)
Maske zum Erstellen von Dateien (umask): /pages/81/e2/d0013149/home/htdocs/tmp/cache (0755)
config_file: 0444
----------------------------------------------

Re: Problem with SitemapMgr – has somebody same problem?

Posted: Fri Aug 18, 2017 10:41 am
by PinkElephant
Hi
reinhardmohr wrote:after upgrading my site to CMSms 2.2.2 [...] "{Navigator template='cms_template:Sitemap Pages'}"
I've not used the module (I'm looking now) but a quick, loose, not-likely to-be-helpful thought -- could it be the space in the template name? Using underscores has been required in other contexts, after certain upgrades.

The only other oddity I've seen on 2.* upgrade is weird behaviour under admin - with missing javascript functions or files - on both occasions this was solved by clearing the (Firefox) browser cache. Again, it's not likely to help here.

Hopefully, someone who knows will be along soon...

Re: Problem with SitemapMgr – has somebody same problem?

Posted: Mon Oct 02, 2017 3:07 pm
by rvwilliams
I have exactly this problem on a brand new install of 2.2.3.1 and SitemapMgr 1.5.1. I tried the suggestion of downgrading to 1.4 and that works fine. Looking at the source code for the 2 versions, one major difference seems to be in the calling of the CreateSiteMap function. In 1.4 it is called directly but in 1.5 and 1.5.1 it is called via the DoFrontEndRequest function that is new for 1.5. Then the parameters for CreateSiteMap have also changed between the two versions.
I haven't progressed any further than that in debugging the problem.

Re: Problem with SitemapMgr – has somebody same problem?

Posted: Mon Oct 02, 2017 4:15 pm
by Rolf
@rvwilliams What PHP version are you using?

Re: Problem with SitemapMgr – has somebody same problem?

Posted: Mon Oct 02, 2017 4:24 pm
by rvwilliams
PHP 5.6.31

Re: Problem with SitemapMgr – has somebody same problem?

Posted: Mon Oct 09, 2017 4:49 pm
by Rolf
I am planning to do some work on SitemapMgr soon.
Please provide me info I can use to narrow down the cause of this. I might find something in the code that can prevent it.

-> Which sitemap is created and when is it gone?

@rvwilliams Correct, all admin requests are changed to frontend ones, because of a very minor vulnerability.

Re: Problem with SitemapMgr – has somebody same problem?

Posted: Mon Oct 09, 2017 6:56 pm
by reinhardmohr
Hi, Rolf,
in the meantime I am on CMSms 2.2.3.1 and did the latest module updates, too (CGExtensions, CGSimpleSmarty, …). So today I tried to reinstall SitemapMgr 1.5.1.
But I got the same errors as before – nothing has changed from the first time I had tried to install it.
I completetly deleted it and tried again – nothing helped. Then I tried SitemapMgr 1.5 – this could not even be installed properly.
Then I went back to SitemapMgr 1.4 – and it again worked like a charme.

I am on php 7.1.8.

Hope this helps a little bit.
Good luck and thank you for your work!
Reinhard

Re: Problem with SitemapMgr – has somebody same problem?

Posted: Thu Oct 12, 2017 10:06 am
by rvwilliams
I've done a bit more research. First I turned on debug. This showed the Frontend request URL. Next I modified action_update_sitemap.php and put a simple die('Starting update_sitemap) statement at the start of the module before any other instructions. This is never executed. However if I copy the Frontend request URL and put that in a browser, my die instruction is executed.
I've never written a module so I don't know how to change the DoFrontEndRequest function to make it call the update_sitemap action.

Re: Problem with SitemapMgr – has somebody same problem?

Posted: Mon Oct 16, 2017 8:43 pm
by Rolf
For your information, I have invested several hours on the SitemapMgr module. Did many improvements to module installation and the site map renewal task.

Haven’t found a real bug that explains your described problem but I think the module is more stable by these changes. It might solve your issue too (I hope!)

I’m now testing the new release at my own websites. Public release in a week or so I think.

Grtz Rolf

Re: Problem with SitemapMgr – has somebody same problem?

Posted: Tue Oct 17, 2017 8:26 am
by rvwilliams
Hi Rolf

You're using touch with a URL to make the link to the action and I haven't seen it used in that way before. Is that valid?

Re: Problem with SitemapMgr – has somebody same problem?

Posted: Tue Oct 17, 2017 10:14 am
by Rolf
rvwilliams wrote:You're using touch with a URL to make the link to the action and I haven't seen it used in that way before. Is that valid?
Do you have another solution? I am open for suggestions:)

Re: Problem with SitemapMgr – has somebody same problem?

Posted: Wed Oct 18, 2017 11:01 am
by rvwilliams
Hi Rolf

I've had a look at the page template and the PHP code. If you want a suggestion mine would be to split action.save_sitemap.php into two. The first part to do the business with the database and the second part to create the file. That way you would avoid the problems of trying to call a front-end action from the backend module. You would then have two separate actions, one for the create tab and the other for the update tab.

Re: Problem with SitemapMgr – has somebody same problem?

Posted: Thu Oct 19, 2017 5:06 pm
by Rolf
rvwilliams wrote:If you want a suggestion mine would be to split action.save_sitemap.php into two.
As far as I see now the problem occurs during the automatic sitemap renewal. Before that all existing files are deleted... and they are so it seems not recreated after that.
File action.save_sitemap.php isn't used in this process.

I still can't reproduce this issue, but I have done some code clean up and did a few improvements on the module. It is now running (still without problems) on a few of my sites at different servers. I will release it in a few days.

Re: Problem with SitemapMgr – has somebody same problem?

Posted: Sun Oct 22, 2017 5:18 pm
by Rolf
After *many* hours of testing and debugging I suspect the problem is caused by the protocoll less URI in previous core releases. Please upgrade your CMS and test again...
Or at least add $config['root_url'] = 'http://www.yourwebsite.com'; to you config file.

All my installs work flawless, and use of course the latest CMSMS release

PS. I now see Reinhard is already on 2.2.3.1... So can't be an URI problem
Going to release the new module tomorrow with mostly code cleanup and minor fixes. Haven't got a clue why it does not work at your sites... sorry.

Re: Problem with SitemapMgr – has somebody same problem?

Posted: Mon Oct 23, 2017 12:32 pm
by Rolf
SitemapMgr 1.5.2 is released. Will be in Module Manager in a few hours (max. 8 ) or so. You can also download it directly from the forge:
http://dev.cmsmadesimple.org/project/files/1392