issues and wishlist

[vivrana]

Hi,

I came across the following issue a few days ago: I wanted to test the sitemap when I'm in development mode without pinging. I appreciate the fact that you've created an option to control pinging, but I noticed that the following line of code in sitemap_generator.rb doesn't allow me to test my model specific code in development mode: if Rails.env == 'production' I temporarily changed it to 'development' but that's not too convenient every time I want make some changes. Would be great if there was a clean way of testing the sitemap generation code in development mode.

Any good way of generating the sitemap entry for our static pages like the home page? Currently I had to include it in my model specific generation code.

Documentation addition: You need to copy over the sitemap-generator/sitemap.xsl file to their public directory for viewing the xml in the browser.

I'm also having a bit of trouble figuring out how to account for cases where the model may not have changed but the front-end interface to the model may have changed. For example, a product model may not have had data changes but the front-end interface may have changed to include say a GTIN where it didn't before. Now this might make the product pages crawl worthy. Any nice & clean way of figuring this out using the plugin to update the last modification date?

Wish list: Specialized Sitemaps for Video, Images, etc (or if its already possible to do the following, please let me know how): http://www.google.com/support/webmasters/bin/topic.py?hl=en&topic=20986

Thanks a ton!

[christianhellsten]

Thanks for all the suggestions. I'll definitely add support for video and image sitemaps in the future.

Currently, the only way of including, for example, the homepage in the sitemap is to create a custom sitemap. This and many other things will change in a future rewrite I have planned.

In the latest version there's no need to comment out the if Rails.env == production.