Xml Sitemaps pligg module v0.9
Thanks for visiting! If you're new here, you may want to subscribe to my RSS feed. This blog posts regular information about web development, unix/linux, How-tos and patches. Go ahead, subscribe to my feed! You can also receive updates via email, instant messenger, skype or tweeter.
This one is a quick release just like the previous one that fixes just one thing.
All previous versions had this problem that the urls were not urlencoded so those urls that contained special characters like those with an accent or diacritics were invalid and of course google would show an error on those sitemaps.
Version 0.9 makes escapes those urls so now those of you with such special characters in the urls can finally enjoy this module.
It seems like the modules is getting closer to version 1.0 . If you have any suggestion about some feature you would like in 1.0 or you found some other bug that needs fixed, don't hesitate to let me know about it.
Hello.
When I set up the plugin on link:
http://www.chevauxduweb.com/admin_config.php?page=XmlSitemaps
I’ve on page only:
nothing found
Some Idea ?
On pligg 9.9… Thanks
Hello,
For me don t work, i install the module, i insert the cod in htaccess, and when i run the sitemap i riceve this message:
…
http://www.pligg.ro/module.php?modul…ow_sitemap&i=1
2008-05-18T18:10:28+03:00
…
this doesn’t mean it’s not working . It’s working it’s just not using friendly urls. You have to make sure you have activated these types of urls in the Xml sitemaps config.
also make sure you delete the cache is you use it.
thanks, you can tell me how and where to config the xml sitemaps..
i modificated in admin with TRUE friendly ulr, i delete the files from cache and i insert the line in httaccess, but the url is the same..
the value has to be ‘true’ not ‘TRUE’ … this is case sensitive
yes is true not TRUE
The XML Sitemaps module has been excellent; however, I recently ran into a problem with assigning the correct priority value.
Google returned the following Warning message:
All the URLs in your Sitemap are set to the same priority (not the default priority). Priority indicates the importance of a particular URL relative to other URLs on your site, and doesn’t impact your site’s performance in search results. If all URLs have the same priority, Google can’t tell which are more important.
Does anyone know how to correct this?
Any guidance will be appreciated!!
The module computes the priority based on the link age, number of comments, number of votes, and the last time when it was updated.
This is the exact formula at xml_sitemaps_main.php line 154:
$v=(time()-$link->date)/60;
$pri=max(0.0001,(( $link->comments /$v ) * 30 + ( $link->votes * 10 / $v ) + ( 100 / max(100,time()-$link->modified) ) * 60 )/ 100 );
my idea was that the number of comments it got since it was created should account for 30% of the priority, the number of votes for 10% and the time when it was last updated ( commented, voted, modified ) for 60%
I guess this isn’t perfect for all sites, so just change it till you get it right for your site.
Thank you for such a prompt response! One more quick question… For about half of my generated sitemaps, every entry will have a priority set to: 0.0001.
I can definitely tinker with the formula you pointed out.
I am using the RSS Import module and it randomizes the votes. Everything else will probably be close to constant values. It worked perfectly for a long time until recently.
Maybe I should shift the weight of your formula toward the number of votes since the update or # of comments is typically constant.
Thank you for your guidance!
0.0001 is used for all links that have a priority that is less then 0.0001 . If all your links have that then maybe they all have a priority less then 0.0001
as you can see from the formula, the number of votes and comments are divided by the link age ( in minutes ) . So for really old links that were not updated recently, with few comments and few votes the priority is very likely to be under 0.0001
And the fact that you are using the RSS import module makes it worse because it assigns votes randomly but all at the same time. So the link is only updated once when it it posted but then not updated unless someone comments on it.
Also if you are caching the sitemap you will almost never have ( depending on how long you decide to cache it ) an updated sitemap right after a link was posted ( when it should have the highest priority because it was updated very recently, and has a lot of votes)
Thank you for the thorough explanation. I now understand the exact problem. In result, using the RSS import will definitely cause me to experience this problem as time passes.
Do you suggest that I completele re-arrange the formula to ensure that it is divided by the # of votes? Also, what do you suggest in terms of an appropriate cache time?
I don’t see how dividing by # of votes would help or what is the logic in that since you’re assigning votes randomly, unless all you are trying to get is different / variable / random priority for each link, but I see no point in this.
I have cache set to one day for a site that also uses the RSS import module. I don’t think less then a day would make much sense cause I doubt google or other search engines would try to download your sitemap more then once a day and even if they do they would not start fetching your new links so soon…but it’s just a guess..I may be wrong…
Hi Mihai
Here is the warning I receive according to Google Sitemaps:
“All the URLs in your Sitemap are set to the same priority (not the default priority). Priority indicates the importance of a particular URL relative to other URLs on your site, and doesn’t impact your site’s performance in search results. If all URLs have the same priority, Google can’t tell which are more important.”
In result, if i divide by the # of votes, then i will have a better chance of receiving a unique priority. Is that correct? Am I overlooking something?