XML sitemap 6.x-2.x-dev progress

Yay, very exciting. Thanks Dave!

xmlsitemap.module, xmlsitemap_node.module, and xmlsitemap_menu.module have been added to CVS. Once the 6.x-2.x-dev release is repackaged, I'll show it on the project page. Working on getting the xmlsitemap_engines.module converted...

The build has been officially packaged!
http://drupal.org/node/449710

AWESOME! But no one is watching this thread! What's wrong with everyone!? A working version, a real, working version! I'm so excited. Great job Dave. We'll be working on deploying this next week, so get you patch applying hat on. ;-)

@quicksketch: Thanks. :) I'll be looking forward to any followups.

A big note to anyone else reading this: Upgrading from any other version to 6.x-2.x-dev is NOT currently supported. To use this version you MUST disable and uninstall any current XML Sitemap modules.

woot subscribe!

Quick update: xmlsitemap_engines is almost ready and the test suite is making good progress as well.

A quick update on the timeline for 6.x-2.x:
5/10-5/16: Add _engines. Polish and test _node and _menu.
5/17-5/23: Add _taxonomy and _user. Polish and test _engines.
5/24-5/30: Polish and write remaining tests. Add documentation (adv_help).
5/31: Beta release?

Also please read http://blog.davereid.net/content/state-of-drupal-xml-sitemap-2009 for ways to help support the rewrite.

The _engines module has been added to CVS.

Got a little behind schedule for _taxonomy and _user because of #472598: Architectual problem: Mass updating links. In the meantime as a bonus, I managed to get multilingual support added in #470602: Support for multilingual sites.

This isn't a support request, it's a task. I'm the one that originally created the issue.

Dave, thanks for your great work. 2.x is fast!

I hope it won't be impolite if I ask about taxonmy...?

... :/ :) :*

Szy.

count me in for using 6.x-2.x-dev.. gime 5 minutes. just found this thread,
I've been running one from 6 months ago..lol

EDIT ...This works really nice...no fuss, no patching, no back dating cus it don't work..
Your a hero !!
thanks Dave

Major update committed today. xmlsitemap_taxonomy has finally been included. Rejoice!

Side note: for maximum xmlsitemap settings page enjoyment, download and install the Vertical tabs module.

Great! subscribe.

Subscribing. Nice work. Need this very soon for www.kpbj.com.

Subscribing!

Thumbs up, thnx Dave!

For those of you waiting to install this.. lol. here goes
Do it NOW !
It works very nice.... even has a style sheet option, neat
see one at http://buckeyelake.org/sitemap.xml

Yes, but will it handle 6300 nodes?

lol.. give me a little time and i will run a test on that.. should we up that number a few notches? -maybe so, we don't want any limits. 'scalable'. how many links do you want on each page. 1000 or less. be back later w/answer

I've tested it with over 50,000 nodes, and 25,000 taxonomy terms and users. It takes a bit to help 'import' all the old content into the sitemap on cron like it's designed to do (just like the search.module). You can use admin/settings/xmlsitemap/rebuild with a large site to get all your content indexed right away, but it will take a while.

The 6.x-2.x version was written specifically to be stable and scale to large sites.

yep, i did 9000 nodes, with comments and taxonomy.. here is what it spit out, one index page and 2 sitemap list pages.. i had it do 5000 at a cron

Totally awesome. Works FAST and WELL. :-) Thank You!

Yup. I tested this on a local machine that mirrors the server. More than 50,000 nodes and it works great with a small footprint.

I guess that I can finally replace the November 8 version that is currently installed.

I could really use some input and feedback on the one last remaining architectural problem in the 6.x-2.x version: #512216: Last architectural problem: override a link's status in the sitemap (inclusion/exclusion).

@Dave - Thank you for the excellent rewrite. As per our (obviously) brief twitter conversation, we're going to start include 2.x dev in our shop's base Drupal install (the basis for all production sites). I'll report back if there are any issues. Should I assume that once #512216: Last architectural problem: override a link's status in the sitemap (inclusion/exclusion) is closed a beta release will be rolled? Running "dev" code in production is always scary, no matter how stable and improved.

I've started tagging the issues that I consider 6.x-2.0 alpha blockers:
http://drupal.org/project/issues/search/xmlsitemap?issue_tags=6.x-2.0-al...

A kind of pre-alpha release has been made: 6.x-2.0-unstable1. For all intensive purposes, it's basically an alpha release, but needs some testing to make sure all the latest big changes work just fine. We are back on track to get an actual alpha out soon if we get lots of testers, and onwards toward a 6.x-2.0!

I'm intending that someone on our team will get to it within a few days, then hopefully we'll have plenty of time to rock 'n roll :)

I assume the newest dev version is ok for test run too.. it's in there.lol

@dbeall: Yeah, it's basically the same code now that the nightly snapshot has been regenerated.

Subscribe. Very excited about this - it comes just about the time when I need it.

6.x-2.0-unstable2 is now available which fixes a few annoying, but minor bugs from unstable1.
http://drupal.org/node/554996

I like a daily upgrade, shows rapid development progress..lol . I think Dave Reid deserves a vacation after this.

I must admit... loading a version labeled "unstable" is a lot more scary than even an "alpha" version. Shouldn't this be an alpha? :-)

I rather like this warning from a year ago.(can't remember where in Drupal it was.)

Totally a super alpha release that just barely works. It'll probably break your site, crash your server and burn down your house so
MAKE A BACK UP OF YOUR FILES DIRECTORY AND YOUR DATABASE!

edit: or maybe this one..lol
This is experimental software meant for advanced users; assume nothing works, and you may be pleasantly surprised. And when it breaks, throw the broken bits at the issue queue.

@gregarios: I'm doing unstable releases right now since:
1. Following the same pattern as Drupal 7 since they're also creating unstable releases before we go into alpha where it's just bug fixes and working on translations only.
2. Not finished writing planned features for 6.x-2.0. But there is not much more left. Alpha is close.

I'd prefer to start getting people off using the 'dev' releases now that we have unstable releases because I can have control when the unstable releases are made. The 'dev' builds are just automatically packaged every 12 hours from CVS. I may be half-way through a feature and commit my progress to CVS, and it gets packaged while it doesn't work and incomplete. Plus this gives people using the update status core module an easy way to tell when there is an update. The only way to do it with the 6.x-2.x-dev version is if you use the cvs_deploy module.

Because of the way that 6.x-2.x is being written, its very stable already. Lots of people have been using 6.x-2.x-dev and liking it. Use whatever you're comfortable with.

*good info on the auto packing of dev, didn't know that.
Every 6.x-2.x release I have installed to date has worked very well. If there was any issues, I didn't find them.

Just tested unstable2. Seems to be working quite well so far. It's so great to finally have a working XML Sitemap module for Drupal!

I'll let know if I run into any issues.

6.x-2.0-unstable3 will be available shortly and I'm proud to announce it has full-multilingual support and integrates very well with i18n. Voilà! Your French XML sitemap could only contain French content, etc.

Only two remaining issues that are blocking the alpha:
http://drupal.org/project/issues/search/xmlsitemap?issue_tags=6.x-2.0-al...

I wish there was a better way to subscribe...subscribing.

subscribe

subscribing. sorry ;)