1.5.2 upgrade destroyed site maps

  • Let me be clear, that is extremely frustrating. A heads-up would have been helpful telling users that the 1.5.2 update removes the user’s existing sitemap and requires updating settings and creating menus with the WordPress Menus feature. I appreciate the time and effort but this might have been marketed as a new product, not an upgrade. I’d gladly take back the last version. That was easy to use, customize, and filled a need. Presently, I am wondering what the benefit is, and how it is easier, using WP Realtime Sitemap when I have to build the menus myself and have to figure out what all the new settings are for. I could just stick the standard menu widget on a page and call it a sitemap. That would be easy.

    At present I do not suggest upgrading to 1.5.2 until the developer posts a step-by-step walkthrough of how to properly upgrade the plugin so that the existing sitemap and settings are not lost.

    In the meantime, has anyone successfully upgraded with custom CSS? Does the new sitemap use the old CSS or does it require being updated too?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Rincewind

    (@rincewind)

    Let me be clear, that you are a stupid idiot, do not make assumptions as to what my plugin does as all it has done is made an ass out of you!

    Why would I give people a heads-up on something that is not the case?!?!?!

    A user requested for the sitemap to be able to show the menu he had created with wordpress itself, this was implemented all the old functionality of the sitemap remains, if you perhaps took the time to go to the plugin settings page and set the order settings to what you wanted the sitemap would then display on your website.

    Calm down guys!

    Let’s keep a cool head about this. Aye, the functionality has changed; I got scared for a moment until I read the new instructions! (See, that’s why @rincewind bothers to write instructions! They are important!) And now it’s actually much easier to define how things appear, at least, if one has a single imagemap. Nice touch on adding a menu as well.

    The only question I have is how to have different sitemaps on different pages, since there is just one shortcode, and one option page to define what it does. For instance, one can have a sitemap just for categories 1-3 and another for categories 4-6 on a different post/page. This can sometimes be useful, although I guess it’s not overwhelmingly important for most people who just have one sitemap.

    Plugin Author Rincewind

    (@rincewind)

    I could change the shortcode to be [wp-realtime-sitemap id=”1″] instead of [wp-realtime-sitemap show=”all” this wont break things for when people upgrade as I would leave in the old code for 1 version to give people time to change over to the new shortcode.

    I could perhaps then include another option to choose what gets displayed with what id and in what order.

    My only concern is that it may make the settings page a little overwhelming to some people, its already pretty long as it is.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘1.5.2 upgrade destroyed site maps’ is closed to new replies.