• hi,

    great plugin, used for years! got a tiny problem with the user interface though, using latest v3.16. whenever i try to set an additional page to priority 1 and save my options, the plugin refreshes the page and suddenly displays that page to have a priority of 0. apparently, the value of 1 gets stored properly in the db, but somehow when passed via js into the html select, the decimal place .0 behind the 1 forces it to go to default 0. probably something to do with the way my browser’s javascript interpreter is simplifying the 0 decimal (using ff2/ff3, havent tried other browsers).

    in any case, changing

    number_format($v->getPriority(),1,".","")

    to

    (intval($v->getPriority())!==1 ? number_format($v->getPriority(),1,".","") : $v->getPriority())

    on line 854 of sitemap-ui.php fixes this problem with the least amount of intrusion into existing code and shouldnt have any unwanted effects since it’s only messing with the output of the ui. that’s my guess anyways. regardless, verification on this by a person of some authority on the subject would be greatly appreciated. ?? for future releases it might be good to get this (probably cross-browser) javascript discrepancy more properly addressed. until then my quick fix works for me.

    with warm regards,
    -rob

Viewing 2 replies - 1 through 2 (of 2 total)
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘[Plugin: Google XML Sitemaps] Problem setting additional page priority to 1’ is closed to new replies.