The long answer is that some unexpected changes to the RapidWeaver API in v8.1 broke SiteMap+ and quite a list of other things as well. But the broken stuff has nothing to do with that setting in the Advanced section or the RapidWeaver project settings. I’m pretty sure that setting for turning off the RapidWeaver built-in sitemap is as old as SiteMap+. I think that both the RapidWeaver folks and LogHound came out with sitemap solutions at exactly the same time.
Small bugs like this come up from time to time, but normally a quick update makes them pretty pain free. The reason this has suddenly become a larger issue for so many users is that a whole bunch of people aren’t getting automatic updates for from old versions of SiteMap+ and PlusKit and the rest of the older LogHound plugins.
And why are so many people stuck on these older versions of LogHound plugins – after all, I released an update to EVERY ONE of the LogHound plugins almost exactly 2 YEARS ago.
The reason is that I don’t control the LogHound site where the updater files are hosted. John kept control of the LogHound name and website and just transferred ownership of the plugins to me. By the way that was a completely gentleman’s agreement – he just handed me the keys and asked me to take care of things – sometimes businesses can just be nice people and think of their customers first 😃
And I also don’t control the plugin updater – that’s part of the app.
I asked both RMS and John to redirect these update requests, but it was a low priority for everyone – and also apparently too low for me to remember to follow up about it.
The good news is that John has now picked up the dropped baton. Things are moving again and I think we’ll get it taken care of shortly once and for all.
There are still a ton of other broken plugins: Stacks (twice at least), Blocks, and the new version of PlusKit, RapidCart Pro, and every un-updated LogHound plugin.
I think currently only Blocks and RCP are still having some compatibility issues. Everything else has been updated. However it still feels like we haven’t quite found everything the API changes broke just yet.
There is a beta version of Stacks to fix the latest issue on our Slack channel (http://slack.yourhead.com is open to anyone who wants to run our beta stuff – get ready – Stacks 4 beta testing is not far off). Blocks is affected by that same change to the Styled Text API, but the fix there is quite a bit more complex than the Stacks variant – the problem is pretty esoteric, and mostly cosmetic, and Blocks is not very widely used anymore, so I’m taking it slowly and will update Blocks carefully (probably in a week or so).
If anyone has trouble with any of the YourHead (+LogHound) plugins just let me know.