Xml Sitemaps pligg module v0.9

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.

download v 0.9 from the module's page

65 thoughts on “Xml Sitemaps pligg module v0.9

  1. 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.

  2. 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..

  3. 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!! πŸ™‚

    1. 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:
      $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.

      1. I think, for sites using cache and the RSS importer or sites that don’t have much traffic or many active users voting all the time it would be a good idea to modify the script like this:
        on line 154:
        instead of $v=(time()-$link->date)/60;
        use $v=(time()-$link->date)/3600;

        you should clear the cache if you use it and resubmit the sitemap to google after this modification.
        IF you still get warnings just increase the divisor ( 3600 ) until it’s ok
        I’m guessing that if you use a cache set for 1 day 3600 should be ok, if not you could go higher

  4. 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!

    1. 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)

  5. 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?

  6. 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…

  7. 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?

  8. I’m getting the same error on my Google’s sitemap. Any patch on the formula?

    It looks like G now is very strict in using a sitemap. I haven’t had no errors before, the erroors just appeared recently. Any idea to fix it. It is not actually errors but WARNINGS.

  9. Wouldnt we be able to just submit sitemapindex.xml and let google find the other sitemaps using that xml?

      1. Okay great. I think you should have something somewhere where this is noted. It was a pain in the butt to figure where to find the sitemap pages and index. Maybe you can update the original sitemap post here, or even update the modules index page so it notes it from within the admin area.


  10. Today I see new error in Google Webmaster Tools

    ” Invalid tag value
    This XML tag has an invalid value. Please fix it and resubmit. ”

    I have 6 sitemap sitemap-0.xml – sitemap-6.xml

    This error only for sitemap-6.xml

    Before I have other error and I fix it by you siad

    ” $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 ); ”

    ” on line 154:
    instead of $v=(time()-$link->date)/60;
    use $v=(time()-$link->date)/3600; ”

    and error disappear but yesturday I upgrade pligg to 9.5.5 so I see this new error (before I use 9.8.2)

  11. this more detail

    79 Invalid tag value
    This XML tag has an invalid value. Please fix it and resubmit. Help Help Parent tag:
    Found: url
    Aug 8, 2008
    Details 31 Invalid tag value
    This XML tag has an invalid value. Please fix it and resubmit. Help Help
    Parent tag:
    Found: url
    Aug 8, 2008
    Details 19 Invalid tag value
    This XML tag has an invalid value. Please fix it and resubmit. Help Help
    Parent tag:
    Found: url
    Aug 8, 2008
    Details 13 Invalid tag value
    This XML tag has an invalid value. Please fix it and resubmit. Help Help
    Parent tag:
    Found: url
    Aug 8, 2008
    Details 7 Invalid tag value
    This XML tag has an invalid value. Please fix it and resubmit. Help Help
    Parent tag:
    Found: url
    Aug 8, 2008

    1. the fact that you divided by 3600 gives the priority more decimals … maybe too many… And I think google doesn’t like that

      use : $v=round((time()-$link->date)/3600,3);
      instead of what you used before and let me know if you still have a problem

      1. When I use

        some priority go high 2.0 or 3.0 like that and error agian

        so now I change back to the original

        $pri=max(0.0001,(( $link->comments /$v ) * 5 + ( $link->votes * 35 / $v ) + ( 100 / max(100,time()-$link->modified) ) * 60 )/ 100 );

        and no error now, the highest priority are around 0.4 or 0.5 in new story on sitemap but sometime I got warning “All the URLs in your Sitemap have the same priority. ” in some sitemap again in sitemap-1.xml (I have 6 sitemap) but sometime no warings

        sitemap-1 to sitemap-5 all priority same 0.0001 but only sitemap-6 (the latest) have 0.1 0.2 0.3 like that

        I like you plugin because this is only one sitemap plugin for pligg no more out there so I love it but I don’t like to always go to check in Webmaster Tools that my pligg sitemap will okay or not? Sometime ok sometime not. sometime priority go higher that 1.0 sometime all same 0.0001

        I understand your formula a bit but it very hard for me or other people to understand and fix it, Can you make it easier.

        I have some example very good sitemap plugin for wordpress
        “XML Sitemap Generator for WordPress ”
        Very easy to config and nothing to do after that, no error

        I like the option that let people set priority (see picture below)

        Can you make Xml Sitemaps pligg module has option like that, If you can do that I think no more problem about Google Webmaster Tools and priority issues again

        Xml Sitemaps pligg module is the Best, Cheers


  12. Same as above (Pligg 9.9.5)

    “Invalid tag value
    This XML tag has an invalid value. Please fix it and resubmit. ”

  13. Is there any way this formula can be rewritten to give votes at least 60% input to priority and have the lowest priority value greater than 0.1? I have all my priorities 0.00000x (E-5 in xml) and they all reset to 0.001 (the min function) making them all the same. I have 40,000 links and the older a link gets the lower this formula makes the value. can the lowest priority be greater than 0.1?

    1. You can rewrite the formula as you wish. but if you have 40000 links and the votes range is small how is giving the votes 60% going to improve the uniqueness of the priority ?

    1. That’s not your sitemap. It’s the sitemap index. IT only contains links to other sitemaps. Go to the links in it and you’ll see the actual sitemaps.

  14. Mihal cold you please help me with my question above? i have sitemap-0.xml up to sitemap-76.xml and everything from 0-75 all have the same priority in webmaster tools. πŸ™

    1. Temi, please look at the discussions above about changing the formula if you really care about turning off those warnings.

      You should also read google help that says that a waring is just that … it’s not an error and it doesn’t mean they will not process your sitemap if you have those warnings. The only problem is they don’t know which is more important to you.

  15. I have read the discussions but when I make changes to the formula some of my priorities go above 1.0 and 75 out of 76 sitemaps all have 0.001 priority. does anyone know how to change the formula so the priority relies solely on votes + comments and will still stay between 0 and 1.0 ?

    1. That sitemap is just the one for pages like main mage, upcomming, categories and maybe others. It doesn’t seem like it’s missing anything but there are more sitemaps that you have to send to google. The other sitemaps will be named sitemap-x.xml ( where x is a number starting with 1 )
      like this one: http://www.santabarbara.net/sitemap-0.xml
      You will have to send a sitemap index to google ( http://www.santabarbara.net/sitemapindex.xml ) . The sitemap index will contain links to all those sitemaps.

  16. I have installed this module, submit a new story…. and I don’t know where to go from here. There’s no sitemapindex.xml that was created. Where can I found it?

  17. Hi! Come here again, I'm Sara –> http://patchlog.com/php/xml-sitemaps-pligg-modu

    When XML Sitemap Version 1.0 release?

    I'm waitting for that, so many problem here everytime when I get warning in google webmaster tools, I feel google temporaly stop index my pligg site

    I find fomula that suit my site but no one suit my site, some over (1+), some less (0.0001) and I dont know much about math or this formula so I just random change the number and variable to see sitemap are okay or not

    Now I get my own formula and remove $time variable because $time is the main variable that make priority change

    $pri=max(0.0001,(( $link->comments /20 ) * 38 + ( $link->votes * 2 / 2 ) + ( 100 / max(100,$link->modified) ) * 60 )/ 100 );

    I dont know what the meaning of number i put in there,I just put and see sitemap okay or not?

    I dont care which story submit first or submit later I only want the sitemap that work proprely with google webmaster tools and let google index faster and faster, no time to wait, no time to check sitemap first before index.

    Ex. If new sitemap error, Google won't index a new story that have priority problem, Google will wait until prioty or sitemap okay.

    This can't wait. In real world we can't wait , who can index faster is the winner

    Before my pligg site get index after submit around 15-60 minute but now after oftenly have problem with sitemap I have to wait for about 5-12 hours so people(other pligg site) go indexd first and when people searching my story will drop lower that other site in SERPs

    And the last I still want XML Sitemap Version 1.0 and still want features something like this (see picture below)


  18. Sry that double comment.

    When version 1.0 release could you notify me by email (see email in comment)

    And your new comment system look very nice!!

    ٩(-̮̮̃•̃)۶ ٩(̾●̮̮̃̾•̃̾)۶. .. Cheers: Xml Sitemaps v1.0 ٩(-̮̮̃•̃)۶ ٩(̾●̮̮̃̾•̃̾)۶.

  19. if you really don't care about which page has higher priority and you just want variety then this will work for you:
    replace those two lines with this one:

    Having an interface where you could have better control would be nice but I don't have the time to do that right now.

  20. Hi Mihai,

    I installed xml_sitemaps 1.0. and feeds (rss.php) stopped working. my pligg 1.0.2.
    What do you think might be happening.


    1. I never released xml_sitemaps 1.0 so I don’t know what you installed. Latest version of my module is 0.9 if someone else released a version 1.0 they should have renamed it so people know it’s not the same as my module and you should contact them for support.

        1. I tried it with 1.0.0 or 1.0.1 can’t remember exactly which but it worked.
          It probably works in 1.0.2 as no major changes should occur between minor versions.
          The module shouldn’t have anything to do with the rss feeds so maybe your problem is somewhere else.

          1. Mihai,

            Worked very well and the feeds are working well.
            The problem is the version of Yankidank (pligg).

            Google webmaster:

            sitemap sitemap-0.xml OK 05/12/2009
            sitemap sitemap-pages.xml OK 05/12/2009

            That’s right? 0.000445612042099

            Thank you very much

            Sorry my English

          2. Ah now I noticed they releases a new version based on mine. I cannot support something I didn’t do. So please wait for a response from that thread

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.