Google SEO 1.1.11

[frostschutz]

URLs must be unique. When two threads have a similar title that results in the same URL (e.g. title is identical or differs only in filtered punctuation), that's a collision and it will be resolved by applying the uniquifier. The default uniquifier is {$url}{$separator}{$separator}{$id}, i.e. it will be Thread-URL--1234. When there is a collision, the item with the lower ID (so usually the item that was there first) wins, and the item with the higher id (that was created later) get the uniquified URL.

If you write a new thread and you see that your thread ends up with a --number postfix in the URL, you can just remove --number from the URL to see what the original thread with the same title was. Then you can consider wether you want to keep the thread you just made, or wether to make it a reply to the other thread, or wether to give your own thread another name.

Usually thread titles are unique, it's only stupid thread titles like the zillionth installment of the "help me" thread that gets a --postfix.

While we're on this topic, I just found a small bug with the uniquifier / collision handling when something collides with an already deleted thread. I'll fix it in the next version.

[Zash]

A great future release is that we should somehow be allowed to change up the permalinks. I know an IPB plugin does this by getting the permalink structure from an XML file.

[frostschutz]

Sorry, not sure I get what you mean. What links do you want to change up? You can already change the URL scheme and there are many other options that affect how URLs are generated from the item name (filtering of punctuation, character translation, max length etc).

If you want to be able to give items an URL that does not reflect their name at all, I won't do that. The whole point of these talkative URLs is that they do reflect the item they represent.

[aglioeolio]

I see that permisions is not considered to sitemap, so threads in private Forums will be listed in sitemap too.

Is there any problem with "access denied" message to bots?

This plugin is amazing, I´m testing now and it´s looking awesome, no problems at all

[frostschutz]

Actually, permissions should be considered properly in the Sitemap already.

However if you browse the sitemap yourself while you're logged in as user with the permissions, you will see the links in the sitemap too. It's dynamically generated based on the permissions of the current user. Try browsing your own sitemap as guest (if the search engine has the same permissions as a guest on your site, which is the default setting).

If you see something as a guest that guests are not able to see, please give a detailed report (which item was linked, and what permissions are set where to prevent guests from seeing that item). Thank you.

And to answer your question in regards to bots: If you have links in a sitemap that google isn't actually allowed to access, it will display a warning for your sitemap in Google Webdev Tools - but it will still index all links of your sitemap that it can access. Nevertheless there shouldnt be any inaccessible links in the sitemap that Google sees.

[aglioeolio]

hmm... it´s perfect accordly to its permissions.
I forgot to configure access to registered users only before checking "sitemap-threads.xml?page=1" as an guest

Thanks frostschutz

[Bey Brad]

Frostschutz, how much of a practical impact do you think this plugin will have in terms of PR?

[frostschutz]

42

does that answer make you happy?

I'm really not sure, I'm not a PR person.

[Zash]

(03-11-2009 08:31 PM)frostschutz Wrote:  Sorry, not sure I get what you mean. What links do you want to change up? You can already change the URL scheme and there are many other options that affect how URLs are generated from the item name (filtering of punctuation, character translation, max length etc).

Oh, that's already available? Cool, sorry, I didn't actually download.

[Bey Brad]

(03-12-2009 12:21 AM)frostschutz Wrote:  42

does that answer make you happy?

I'm really not sure, I'm not a PR person.

PR ... Page Rank. I would hope that would be the point of this plugin.