archived MarkupSitemap

[uiui]

11 hours ago, Mike Rockett said:

 

@uiui – The module supports sites with the multisite and language support modules installed. I haven't tested it it in a while, so if you have any issues, please let me know. ? 

I didn't see any issues with my multi-language site. But I don't see an option to configure it for multiple domains so that it can be "domainname.fr" for the french-speaking pages and "domainname.de" for the german-speaking ones.

[Mike Rockett]

@uiui Ah you're quite right. Unfortunately, I don't have enough time to implement this right now... If you (or anyone else) would like to take a stab at it, please feel free to submit a PR to the repo. If I find some time, I'll take a look. ?

[JayGee]

I have installed this module on a site that uses URL segments on the home page. I don't seem to be able to access /sitemap.xml - it just redirects back to the homepage, presumably the path is being treated as URL segment. Is this expected behaviour or do I have something set up incorrectly?

[xportde]

Hi @Mike Rockett,

first of all many thanks for this useful module!

I have a language related question: Would it be possible in the near future to exclude certain languages from sitemap via modules config page? We have many customers, who want to prepare other languages in the backend, so the languages have to be enabled and active, e.g. for having preview option. But the languages should not be shown in sitemap, until the translations etc. are finished. 

Thanks in advance,

Thomas.

[Mike Rockett]

@xportde Hi Thomas, I'm quite sure it's possible, but I don't quite know how useful that will be as Google will likely find the page and index it anyway…

 

[xportde]

@Mike Rockett Hi Mike, Google should index those pages, but only in one language. To achieve this, we simply leave out all language related metatags, this is no problem. Corresponding to this, the sitemap should also be monolingual, even if all languages are activated in the backend for being edited and previewed.

[zoeck]

I have a problem with the module.
On a page with 3 languages, the sitemap displays only the default language.

The site works without problems, I can switch the languages:
domain.ext/ (german)
domain.ext/en/ (english)
domain.ext/fr/ (french)

Is there something else that needs to be set so that the other languages are also displayed?

 

Oh, i found my problem... i still had the old sitemap module installed... ? 

[PWaddict]

I'm getting hundreds of PHP notices and 1 warning when visiting sitemap.xml url with debug enabled. With debug disabled everything seems ok. 

Using PW 3.0.165 and PHP 7.4.9.

Notice: Trying to access array offset on value of type null in C:\laragon\www\mysite\site\assets\cache\FileCompiler\site\modules\MarkupSitemap\MarkupSitemap.module.php on line 413

Notice: Trying to access array offset on value of type null in C:\laragon\www\mysite\site\assets\cache\FileCompiler\site\modules\MarkupSitemap\MarkupSitemap.module.php on line 417

Notice: Trying to access array offset on value of type null in C:\laragon\www\mysite\site\assets\cache\FileCompiler\site\modules\MarkupSitemap\MarkupSitemap.module.php on line 427

Notice: Trying to access array offset on value of type null in C:\laragon\www\mysite\site\assets\cache\FileCompiler\site\modules\MarkupSitemap\MarkupSitemap.module.php on line 353

Warning: Cannot modify header information - headers already sent by (output started at C:\laragon\www\mysite\site\assets\cache\FileCompiler\site\modules\MarkupSitemap\MarkupSitemap.module.php:427) in C:\laragon\www\mysite\site\assets\cache\FileCompiler\site\modules\MarkupSitemap\MarkupSitemap.module.php on line 192

 

[Mike Rockett]

@PWaddict – Sorry for the delay in getting back to you. From looking at the lines affected there, it seems like the sitemap configuration saved for each page vanished. Note entirely sure what could have caused that, though. Will give it a look-see on Sunday.

[Marco Ro]

Hi @Mike Rockett,

First thank you for your modulo.

I notice this error on the Search Console: 

The sitemap can be read, but it has errors.
The sitemap is in HTML format
It appears that your sitemap is an HTML page. Use a supported sitemap format.

Examples
Row 1 Tag: html

At the moment it doesn't load me any links in the search console. What can I do?

[Mike Rockett]

Hi @Marco Ro – Thanks, I'll need to look into this. It isn't the first time it's happened. Internally, I use a package that generates the sitemap using a 'fluent' interface, and this issue has crept up with that package a few times in the past.

[Frank Vèssia]

On 5/12/2020 at 7:31 PM, Guy Incognito said:

I have installed this module on a site that uses URL segments on the home page. I don't seem to be able to access /sitemap.xml - it just redirects back to the homepage, presumably the path is being treated as URL segment. Is this expected behaviour or do I have something set up incorrectly?

Hi, did you solved this issue? I have the same problem and even removing the segmentation from home page the issue persists.

[d'Hinnisdaël]

1 minute ago, Sevarf2 said:

Hi, did you solved this issue? I have the same problem and even removing the segmentation from home page the issue persists.

There's two ways I've tried in the past that worked:

1. Use a regex for your allowed url segments so it won't match "sitemap.xml"

2. Trigger a 404 manually from your homepage template file if the first input segment is "sitemap.xml"

[adrian]

I have URL segments enabled on the home template and have:

regex:^[0-9A-Za-z-_]+$

as the regex for the allowed segments. Everything works as expected.

[JayGee]

11 hours ago, Sevarf2 said:

Hi, did you solved this issue? I have the same problem and even removing the segmentation from home page the issue persists.

You know what - I can't even remember now if/how I resolved this! ?. But the answers from @d'Hinnisdaël and @adrian are cool for future reference as I had never even noticed you could use regex in the allowed URL segments so that's great to know.

[Sascha Nos]

Thank you for this awesome module, @Mike Rockett!

[Mike Rockett]

@Sascha Nos You're very welcome! ?

[Mike Rockett]

I'm about to release 0.7.0, which has the following changes:

• Bumps PHP minimum version to 7.1 (should be 7.2, but I'll do that next year)
• Bumps PW minimum version to 3.0.16
• Fixes an issue with regards to null configs
• Sitemap cache policies
• Sets the correct installer directory for Composer

 

[Mike Rockett]

Apologies guys, I seem to have skipped 0.6.0, which was sitting on develop for quite some time. That's fine though, because if there are no issues, I'd like to bump it to v1.0. Given that it's not there yet, I've marked the module as Beta.

If anyone does bump into funny stuff, let me know and I'll get it sorted as soon as I can.

[virtualgadjo]

Hi,

same kind of question as xportde with a little explanation why ?
i'm currently working on a website in three languages (fr, en, es) but, at first, only one will be fully functional and i'm wondering it's possible to exclude, say, en and es, and then only es from the sitemap, knowing that google won't see the pages from the website itself as there won't be any language switch, then, only fr/en and, when ready, fr/en/es

this would allow the customer to fill the fields in the alternate languages peacefully and only send the languages to the master of the world only when everything is ready ?

thanks a lot for any advice and, of course for the module itself that i use on all my websites ?

[skier46]

I'm a newbie
1) I have installed MarkupSitemapXML in my processwire 2.9 site.
Could not see site_name / sitemap.xml.
2) Also I can not add the MarkupSitemap module, although it seems to be available for Processwire 2.8.16 / 3.0.16+.
It seems that only for 2.8.16, but for 2.9 it is no longer ...
I looked through all the branches but did not find working advice.

[Marco Ro]

Hi, maybe it can be useful to someone.

I had a problem with the sitemap generated because Google, or a check tools, tell me that the page was an HTML code. And if I inspect the page it is actually encoded as an html page.

Inside the backend setting I have decheck the checkbox about the CSS, the one ask "Add a stylesheet to the sitemap". And this fix the problem. Now the page are render correctly. With tags: url, loc, xhtmal, image and so on... 
Now works so well!

 

[PWaddict]

5 minutes ago, Marco Ro said:

I had a problem with the sitemap generated because Google, or a check tools, tell me that the page was an HTML code. And if I inspect the page it is actually encoded as an html page.

I'm using the CSS option on few sites without a problem on Google. 

[Marco Ro]

 @PWaddict I know not everyone has this problem. Me too for a long time all works without problems, but after I get this error the only thing that worked was to disable css

[olafgleba]

On 9/15/2017 at 7:07 PM, Mike Rockett said:

Okay, I've set it up to use a custom ISO configuration option for the default language. It only works when the home page's default language name is empty (which is "home" when processed) and LanguageSupportPageName's useHomeSegment is set to false.

First thanks for your effort building this module.

The hreflang for the default language (de) is always empty within the sitemap, e.g. is not populated with the given ISO  Code (de) from the module options, s. screenshots. But even though i don't set an ISO Code in the module options at all, i don't get a false hreflang="home" (something like that), but a empty attribute string also.

Hopefully i plain doing it wrong. Maybe some someone have a hint for me...  Thanks in advance.