Hi. I'd like to start a discussion of what the next version of XML Sitemap might include. I know Darren has some grand plan to which we are not yet privy, but I figure he might not have thought of everythign that everyone else has, so I'm kicking off this thread for brainstorming.
My main ideas at this point are:
* Integrate with the WIJI module/protocol: http://drupal.org/project/wiji
* Consider the possibility of using an XML view when the SoC project is finished: http://code.google.com/soc/2008/drupal/appinfo.html?csaid=5C74EF3C2E7B0A9A
* More optimisation: http://drupal.org/node/252846#6
Of course, none of this can happen until 6.x-1.4 (or 1.5) is released ( http://drupal.org/node/157533 ), which requires internationalisation and multisite functionality, so those ideas will already have happened by the time we get to 2.x.
But that doesn't stop brainstorming. Ideas anyone?
Comments
Comment #1
wayland76 commentedOops, correct the optimisation link to: http://drupal.org/node/252846#comment-827908
Comment #2
darren ohI guess it is time to put all our ideas in one place. I will be back to actively developing this project soon. My priorities are 1) to simplify the code and move extra features into add-on modules so it will be easier for people to add their own features and 2) to improve our ability to index large or complicated sites.
The first priority is mostly done now that the code for adding links and submitting site maps to search engines has been moved to add-on modules. We now need a module to add menu items to the site map. This will fulfill the need to include views in site maps.
Using Views for generating the main site map would cause problems because many links are not node-based, and it would create an unnecessary dependency on Views. However, XML Sitemap would be a logical place for plugins that could output views in XML Sitemap format.
Comment #3
wayland76 commentedOk, thanks Darren. Your comment above has considered the possibility, so that's one thing we can tick off the list :).
Comment #4
jonli447 commentedI swear I posted an issue about this in 5.x, but I cannot find it (maybe I posted in the forums). :-)
Here's what was happening on a 5.x site of mine which I hope to have fixed in my 6.x site. I have a large site that serves pages over both http and https. Specifically, I secured my webforms and the Administrative backend (don't ask why I didn't just run the entire site over https .... it would take much time to explain).
The problem with XML Sitemap was that because I had secured the Administrative backend, it assumed that all my links were secured and thus it would index http only pages as https. I could tweak my site a bit (the securePages module) to ensure that the sitemap file was accessible over http, rather than https, however I would have the opposite problem ... https links would all be indexed as http.
I can imagine that it would take some significant code to fix this issue. However, I do think it would be great if XML Sitemap 6.x-2.x could include a feature that would determine if a page is SSL only or http only, and index the pages accordingly (perhaps by detecting the Apache Rewrites that rewrite https urls to http and vice versa).
It's just my two cents. I think this module is awesome and I look forward to playing with it on my 6.x site.
Cheers
Comment #5
darren ohIt's much easier to deal with individual issues. Most of the things in this issue are already done or have open issues.