i am not sure when or why this happens but the base url set in xsm settings is mydomain.com, and when i rebuild links and look at sitemap.xml is correct. But google is reporting that the domain used to submit does not match domain in map links... so i go to check it and sure enough the sitemap links have now changed to use www.mydomain.com

is it possible that the routine used by cron does not match the routine used by manual rebuild links?

Comments

liquidcms’s picture

liquidcms commented

i actually made sure cron was updating sitemap and compared it to rebuild links one.. and it is still fine.. so there must be a 3rd way the sitemap is being built.. very odd.

liquidcms’s picture

liquidcms commented
Priority: Critical » Normal

i set base url in settings.php and it seems to have fixed my issue.. although pretty sure this is still a bug as there is a setting in the xmlsitemap admin to set the base url it is using for links in the sitemap; and it isn't (always) picking this up.

rayray’s picture

rayray commented

Yeah, I finally got mine to generate after reinstalling, and everything looked fine. Submitted it to Google after half the links were generated, a-ok.

Then I returned a few hours later to find that Google had rejected all 2000 links because the URLs had *changed* from having the proper domain name to having the server's IP address. So all the links were rejected.

I verified that the domain name is correctly set in the plugin, but couldn't find the "settings.php" file referenced above, nor any other way to fix this problem.

Anonymous’s picture

Anonymous (not verified) commented

@rayray: The settings.php file is either in sites/default/ or sites/DOMAIN where DOMAIN is based on your site name. I'm curious as to why this is "change" is occurring but have no clue if your always regenerating the file from cron with the proper domain name set. Give us your site URL so we can take a look.

liquidcms’s picture

liquidcms commented

@rayray - your settings.php file is in /sites/youdomainname/ and if not there possibly in /sites/default/ (but shouldnt be there)

but this is still a bug as it should require the $base_url var to be set in settings.php.

gorod1277’s picture

gorod1277 commented

Hello,

I have a similar problem. When cron run, the sitemap changes and all adresses get extra "index.php". Like xxx.xxx/index.php? instead of normal xxx.xxx/?

Deleting sitemap manually and creating new one provides correct addresses ... till the next cron task.

Would anybody help, where should I look for the problem. Probably in cron or aliases in hostings? (Site base is fixed properly, including settings.php).

Anonymous’s picture

Anonymous (not verified) commented

Re: #6 - It is expected that you're using "clean URL" mode.

Anonymous’s picture

Anonymous (not verified) commented

Re: #6 - It is expected that you're using "clean URL" mode.

gorod1277’s picture

gorod1277 commented

Re: #6 - It is expected that you're using "clean URL" mode.

Thank you for reply, earnie. Would you, please, explain a little bit more? Yes, I do not use clean URL. However for old version of module, everything was fine. I just do not understand where to look for solution, if this is a hosting aliases-cron problems, or the result of a module bug.

Anonymous’s picture

Anonymous (not verified) commented

I'll point you to the documentation at http://drupal.org/node/482550 but I don't see your exception listed. You'll need to wait for Dave Reed to chime in; I'm not coding 2.x.

gorod1277’s picture

gorod1277 commented

Concerning the advice to read a documentation... I did it many times, of course. Maybe I do not understand basics ideas, or miss something important.

Could not find a solution even now... I tried to look for different sites and forums. Though people basically repeat the same instructions on how to install the module. In all cases, I think that is a specific problem of my site - private file system, 301 redirect from index.php to root, etc. So the problem is not global.

Maybe these points may be important in my case?
1 The operation "Update cached files" gives correct addresses, i.e. without index.php. Immediate cron.php task (right after updating cached files) again results in proper adresses in the sitemap. The same result is after re-installing module and first run.
2 The file in the directory "xmlsitemap" have 644 permission. Changing its permission to 755 gives nothing. After a planned cron job that is again 644.
3 I have a 301 redirect via .htaccess from all adresses "sitename/index.php?q* "to "sitename/?q*"

If somebody have a guess (or can just point out a direction) how to handle a problem of wrong adresses generating I would be very happy to hear any advice. After struggling for a weeks with that module I do not see other ways than just deleting it. From the other side I do not see alternatives except for a manual handling...

Update. The problem was resolved. In my case it was related (probably) with the permission for a file.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.