Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

All other Modules

Discuss all other Modules here.

Moderators: martimiz, Sean, biapar, Willr, Ingo, swaiba, simon_w

Google Sitemaps on 3.1 minor issue? maybe?


5 Posts   511 Views


19 April 2013 at 10:49am Community Member, 145 Posts

I'm using SS3.1 and the Google Sitemaps module, but there seems to be a space in the 'loc' url

<sitemapindex xmlns="">
<loc> sitemap.xml/sitemap/SiteTree/1

So just before 'sitemap.xml', there is a space. When I try and copy the URL into web browser, it inserts %20 and I wind up with a page not found. When I remove the space, I can get to my sitemap. How to remove the space? Or is that not an issue for Google since it is probably just using a robot? Or is it because I am developing the site in a subdirectory?

Thanks for any help....


19 April 2013 at 8:02pm Forum Moderator, 5511 Posts

Do you have a space in your sites BaseHref?

Haven't tested the latest 3.1 but the early betas worked fine.


20 April 2013 at 7:10am Community Member, 145 Posts

Hi Will,

Thanks for the response. I don't know why, but $BaseHref is indeed returning the URL with a space at the end. If I replace '{$BaseHref}' in with the URL, it works great.

I don't ever touch the framework so I don't know where I would have changed anything that had to do with BaseHref.

Anyway, it works now, good enough for me :-)

Thank you


20 April 2013 at 10:46am Forum Moderator, 5511 Posts

You can set your base href from your _config.php file - perhaps double check that for a space.


20 April 2013 at 1:00pm Community Member, 145 Posts

I checked and I did not change it in _config.php. It's such an odd little issue, but at least it is working with a hard coded URL. I'll see if I can get to the bottom of it, I'm just learning about installing with Composer which is way cool so I am going to do yet another installation to see how that works and I will install the sitemaps module to see if I have the same issue. The site in question has some custom pages etc, nothing too fancy, but I am not ruling out that I goofed something up.

Thanks for your help again.