I've installed 6.x-2.0-beta1 and when I go to the admin page, I see "No XML sitemaps available. Add a new XML sitemap", and then when I go to /admin/settings/xmlsitemaps/add, I get "There are currently no XML sitemap contexts available." I can't see any other options to change/activate.

So, how do I get this thing started?

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

bdwelle’s picture

...and if I click "Save" on the .../add page, I just end up back on /admin/settings/xmlsitemap with "No XML sitemaps available. Add a new XML sitemap" again.

Any help getting this running?

thx

Dave Reid’s picture

The module didn't create a default sitemap for you on install? That's odd.

I also don't have any problems saving the one and only new sitemap if there are no contexts (and that's totally fine because there isn't any contexts by default). I need to come up with something better to put because like you can attest, it seems wrong.

bdwelle’s picture

Assigned: Unassigned » bdwelle
Status: Active » Closed (fixed)

I think that my problem was due to an unclean upgrade from 6.x-1.2... I deleted all the xmlsitemap tables and variables and reinstalled 6.x-2.0-beta1, and now I have a sitemap listed on the admin page. Thx for replying!

marafa’s picture

hi
i just fixed this problem for myself

i disabled all xmlsitemap modules then uninstalled the modules.

and then i re enabled the modules. the sitemap was automatically generated. however it only had one link to my front page.
at least it works now!

huongle’s picture

Hi,

At Settings tab, click to items of Taxonomy, User, Content or Forum... and change Inclusion to Included, then rebuild your xmlsitemap.

Cheers,
SymphonyThemes.com

marafa’s picture

@huongle
thanks!

cdpapoulias’s picture

Assigned: bdwelle » Unassigned

Hi,

No matter what I do following suggestions in this post, I can't get this module to work. I've tried removing all the variables in the Drupal db, disabling/re-enabling - I made all my content was included - but whenever I go to Add a new sitemap, Drupal simple tells me that "There are currently no XML sitemap contexts available."

Any other possible suggestions?

Thanks all, very very much!

Dinos

Dave Reid’s picture

"There are currently no XML sitemap contexts available." is *not* an error message. Just continue to press Save and you'll get it to work.

cdpapoulias’s picture

Hello,

Unfortunately I haven't been able to get it to work still. I'd like to start from scratch - how can I start from the beginning as if I had never used the module before?

This is what I see so far:

1. disable the module itself
2. remove the cache files
3. remove all variables starting with "sitemap..." in the Drupal database table

then..

re-enable the module. Did I miss anything?

If I can contribute something in the process, I'd love to.

Thanks again,

Dinos

cdpapoulias’s picture

Status: Postponed (maintainer needs more info) » Closed (fixed)

Scratch that - I figured it out - got it too work having read a few more issue logs. Thanks again - and great module :-)

Anonymous’s picture

Status: Closed (fixed) » Postponed (maintainer needs more info)

Does the static sitemap.xml file still exist in your DocumentRoot directory?

cdpapoulias’s picture

Status: Closed (fixed) » Postponed (maintainer needs more info)

No, but I did get it working. Thanks again! Much appreciated.

Anonymous’s picture

Status: Postponed (maintainer needs more info) » Fixed
PaulWoodhead’s picture

Hi Dinos,
I've just been reading your forum posts: because I’m having a torrid time with the sitemap module. I feel like I’ve done everything humanly possible to make it generate a sitemap.xml file, but always to no effect. I can use external sitemap engines and everything is picked up, but the XML Sitemap module has no pages and no links, and when i try to create a new one, no contexts, and therefore no sitemap, and so ad infinitum. I would be sycophantically grateful if you could offer me some advice how to get this module to function.
Yours eagerly,
Paul

bradjones1’s picture

For what it's worth, I've found this to be a frustration myself after upgrading xml sitemap a few sub-versions, and here's what I did to correct this "error" message, plus the problem of having a sitemap with 0 pages, 0 links, and thus a 404 error on attempted load.

This module just didn't seem to upgrade properly for me, so along with drush I did a drush pm-disable xmlsitemap (which will take care of all the submodules too), then drush pm-uninstall, then drush en, which rebuilt the database tables. Also make sure your Web server's write access to files/xmlsitemap is correct. The pm-uninstall/enable routine seemed to shake it loose, and I couldn't find an uninstall option using the Web UI, it was only available (or only worked) through drush. Hope this helps.

PaulWoodhead’s picture

Cheers for that Brad, I've just gone back to the older xmlsitemap module for now....Working fine! Nice one for opening my eyes to drush also! When my frustration gland has settled down a bit, i'll try upgrading again. In the meantime I'm going to have a good look at drush.
Cheers,
Paul

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

alexharries’s picture

Status: Closed (fixed) » Active
FileSize
31.6 KB

Just installed this onto a clean install of UberDrupal and am also seeing "There are currently no XML sitemap contexts available."

Menus and nodes are included; here's the XML Sitemap main page (attached as a screen shot).

Any help would be greatly appreciated. I apologise but I don't have the time right now to look into this myself, otherwise I would try and find a way to suggest how the error message and handling itself could be improved, as this is also hugely frustrating.

Best regards,

Al

Dave Reid’s picture

Status: Active » Fixed

@alexharries And if you read this issue:

"There are currently no XML sitemap contexts available." is *not* an error message. Just continue to press Save and you'll get it to work.

According to your screenshot it looks like everything is working as expected. I'm working on improving that context message in the other context issues.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

AdamKlein’s picture

AdamKlein’s picture

Status: Closed (fixed) » Active

Hi Dave maybe you can help:::

I'm having the issue described above - /sitemap.xml returns "page not found" AND There are currently no XML sitemap contexts available

Here's what I've got configured:
*I don't have il8n submodule installed (not even on server, shows missing on module admin page)
*Element Module Installed
*I've tried rebuilding and updating cache pages
*Content set to Include

Debug at /sitemap?debug
Current context: Array ( )
Sitemap: Array ( [smid] => 1 [context_hash] => 40cd750bba9870f18aada2478b24840a [context] => Array ( ) [updated] => 1284493398 [links] => 0 [chunks] => 0 [uri] => Array ( [path] => sitemap.xml [options] => Array ( [absolute] => 1 [base_url] => http://pacificadvisors.com ) ) )
Chunk: 1
Cache file location: sites/pacificadvisors.com/files/xmlsitemap/40cd750bba9870f18aada2478b24840a/1.xml
Cache file exists: No

After I rebuild or update Cache:
warning: fopen() [function.fopen]: Unable to access sites/pacificadvisors.com/files/xmlsitemap/40cd750bba9870f18aada2478b24840a/1.xml in /var/www/vhosts/pacificadvisors.com/httpdocs/sites/all/modules/xmlsitemap/xmlsitemap.generate.inc on line 190.
warning: fopen(sites/pacificadvisors.com/files/xmlsitemap/40cd750bba9870f18aada2478b24840a/1.xml) [function.fopen]: failed to open stream: Success in /var/www/vhosts/pacificadvisors.com/httpdocs/sites/all/modules/xmlsitemap/xmlsitemap.generate.inc on line 190.
user notice: Could not open file sites/pacificadvisors.com/files/xmlsitemap/40cd750bba9870f18aada2478b24840a/1.xml for writing. in /var/www/vhosts/pacificadvisors.com/httpdocs/sites/all/modules/xmlsitemap/xmlsitemap.generate.inc on line 191.

There are no files located at /files/xmlsitemap/

WeRockYourWeb.com’s picture

Upgrade didn't work, fresh uninstall and re-install didn't work.

When I try and "add sitemap" I get the following error:

Fatal error: Cannot use object of type stdClass as array in /home/public_html/modules/xmlsitemap/xmlsitemap.admin.inc on line 232

Going back to 6.x-1.2 for now.

Dave Reid’s picture

@cwdnow: Which version of the module were you using? The latest 6.x-2.x-dev download from a couple days ago?

WeRockYourWeb.com’s picture

Hi Dave,

Yes, sorry - probably should have used the recommended beta. I went back and uninstalled and reinstalled using 6.x-2.0-beta1. However, I still could not get the sitemap added no matter what I tried (despite the above error no longer showing up), so I followed these steps (I've added comments in case anyone finds this useful):

0) Backup your DB (you should always do this)
1) Uninstall module and flush cache
2) Delete (after backing up) /files/xmlsitemap directory (you might need to adjust permissions to get it to delete)
3) Search (via phpMyAdmin/ mySQL) the database for any instances of "xmlsitemap" (I had been running 6.x-1.2) and delete them if they're old xmlsitemap entries (for example, there was a bunch in the "system" table)
4) Reinstall only the base module and run cron
5) Voila - the sitemap now shows up
6) Install the add-on modules

I really want the comment update feature added as well, but am not comfortable installing the latest dev, so for now I've simply made this simple change that changes the lastmod timestamp so pages are updated with comments.

Thanks for all your hard work Dave! Excellent (and very important) module.

jannalexx’s picture

There are currently no XML sitemap contexts available, even in dev.
Clean install (beta1 and dev)
No way to add new sitemap, no form to do that. A sitemap with the same context already exists. if u press save again and nothing happens, no way or form to add a new name in settings page (beta1 and ajax ui in dev).

Also, in editing default after install and only www.domain.name/sitemap.xml, errors if saving (without anything to change in page)
and if I delete default sitemap.xml there is no way to add it again. Any ideas?

error and backtrace in dev:

recoverable fatal error: Argument 1 passed to xmlsitemap_sitemap_save() must be an instance of stdClass, array given, called in /home/.../sites/all/modules/xmlsitemap/xmlsitemap.admin.inc on line 238 and defined in /home/.../sites/all/modules/xmlsitemap/xmlsitemap.module on line 381.
Backtrace:

xmlsitemap_sitemap_save(string)[xmlsitemap.admin.inc:238];
.xmlsitemap_sitemap_edit_form_submit(string)[form.inc:776];
..form_execute_handlers(string)[form.inc:239];
...ctools_process_form(string)[form.inc:101];
....ctools_build_form(string)[modal.inc:197];
.....ctools_modal_form_wrapper(string)[xmlsitemap_modal.module:33];
......xmlsitemap_modal_get_form(string)[?:?];
.......call_user_func_array(string)[menu.inc:348];
........menu_execute_active_handler(a:0:{})[index.php:34];
.........index.php
recoverable fatal error: Argument 1 passed to xmlsitemap_sitemap_get_context_hash() must be an array, null given, called in /home/.../sites/all/modules/xmlsitemap/xmlsitemap.module on line 386 and defined in /home/.../sites/all/modules/xmlsitemap/xmlsitemap.module on line 472.
Backtrace:
xmlsitemap_sitemap_get_context_hash(a:1:{i:0;N;})[xmlsitemap.module:386];
.xmlsitemap_sitemap_save(string)[xmlsitemap.admin.inc:238];
..xmlsitemap_sitemap_edit_form_submit(string)[form.inc:776];
...form_execute_handlers(string)[form.inc:239];
....ctools_process_form(string)[form.inc:101];
.....ctools_build_form(string)[modal.inc:197];
......ctools_modal_form_wrapper(string)[xmlsitemap_modal.module:33];
.......xmlsitemap_modal_get_form(string)[?:?];
........call_user_func_array(string)[menu.inc:348];
.........menu_execute_active_handler(a:0:{})[index.php:34];
..........index.php
warning: asort() expects parameter 1 to be array, null given in /home/.../sites/all/modules/xmlsitemap/xmlsitemap.module on line 473.
Backtrace:
asort(a:1:{i:0;N;})[xmlsitemap.module:473];
.xmlsitemap_sitemap_get_context_hash(a:1:{i:0;N;})[xmlsitemap.module:386];
..xmlsitemap_sitemap_save(string)[xmlsitemap.admin.inc:238];
...xmlsitemap_sitemap_edit_form_submit(string)[form.inc:776];
....form_execute_handlers(string)[form.inc:239];
.....ctools_process_form(string)[form.inc:101];
......ctools_build_form(string)[modal.inc:197];
.......ctools_modal_form_wrapper(string)[xmlsitemap_modal.module:33];
........xmlsitemap_modal_get_form(string)[?:?];
.........call_user_func_array(string)[menu.inc:348];
..........menu_execute_active_handler(a:0:{})[index.php:34];
...........index.php
warning: Attempt to assign property of non-object in /home/.../sites/all/modules/xmlsitemap/xmlsitemap.module on line 386.
Backtrace:
xmlsitemap_sitemap_save(string)[xmlsitemap.admin.inc:238];
.xmlsitemap_sitemap_edit_form_submit(string)[form.inc:776];
..form_execute_handlers(string)[form.inc:239];
...ctools_process_form(string)[form.inc:101];
....ctools_build_form(string)[modal.inc:197];
.....ctools_modal_form_wrapper(string)[xmlsitemap_modal.module:33];
......xmlsitemap_modal_get_form(string)[?:?];
.......call_user_func_array(string)[menu.inc:348];
........menu_execute_active_handler(a:0:{})[index.php:34];
.........index.php
Dave Reid’s picture

Status: Active » Postponed (maintainer needs more info)

The stdclass/array error messages have been fixed in #921644: add sitemap gives error and deletes existing sitemap.

@AdamKlein: Please visit admin/reports/status on your site and let me know if you see any red warnings. It sounds like your webserver cannot write to your files directory.

inforeto’s picture

The link "add new sitemap", what does it do?

admin/settings/xmlsitemap/add says:
"There are currently no XML sitemap contexts available."

Pressing save it says:
"A sitemap with the same context already exists."

What is a context?

Could not find these in the handbook pages for xmlsitemap nor by site search.

Looking to have a separate sitemap file for each multisite, so that each show links with the corresponding base_url.

Dave Reid’s picture

@inforeto: If you want XML sitemap on a multisite, you have to install it on each site. That's the way multisite works. If you are using the Domain access module, you should use the Domain XML sitemap integration.

Mandakini_Kumari’s picture

Not sure what's use of "Add new XML sitemap" and Edit/ Delete Operations ?
If I click on Edit Operation getting below result
There are currently no XML sitemap contexts available.
Cancel

I want to edit sitemap.xml because I am getting only front page link on
http://drupalwebdevelopment.info/sitemap.xml and http://www.ayushiinfotech.com/sitemap.xml

AlexisWilke’s picture

Category: support » bug
Priority: Normal » Critical
Status: Postponed (maintainer needs more info) » Active
FileSize
103.79 KB
91.2 KB
15.59 KB
99.54 KB

Hi guys,

How can this bug be marked as "closed" or "postponed" since until fixed the XML sitemap is pretty much empty?

Well... maybe you're using a menu, I did not try that one (although looking at the code there is no menu context either), but I wanted my nodes to appear in the XML sitemap. The <front> page appears, that's it.

In the code, there is clearly no context for all sub-types except one: i18n, which I do not use either. How can this possibly be considered working without the contexts? Is there some trick in the core XML sitemap module that is expected to find all the nodes and add them to the sitemap?

Again, I wouldn't mind to help, but I need direction and know whether you, on your end, have the code ready just did not release it yet?

At this this point, the XML sitemap module just doesn't work at all.

As proof, there are a few screenshots and the extended code of the node context:

// $Id: xmlsitemap_node.api.php,v 1.1.2.1 2010/04/29 04:42:29 davereid Exp $

/**
 * @file
 * Hooks provided by the XML sitemap node module.
 *
 * @ingroup xmlsitemap
 */

/**
 * @addtogroup hooks
 * @{
 */

/**
 * Alter user access rules when trying to view, edit or delete a node.
 *
 * Node access modules establish rules for user access to content.
 * hook_node_grants() defines permissions for a user to view, edit or delete
 * nodes by building a $grants array that indicates the permissions assigned to
 * the user by each node access module. This hook is called to allow modules to
 * modify the $grants array by reference, so the interaction of multiple node
 * access modules can be altered or advanced business logic can be applied.
 *
 * This is a backport of the hook with the same name in Drupal 7 core. If this
 * hook is invoked to determine if the anonymous user can access a node
 * regardless of context, the $account->xmlsitemap_node_access will be TRUE.
 *
 * @param &$grants
 *   The $grants array returned by hook_node_grants().
 * @param $account
 *   The user account requesting access to content.
 * @param $op
 *   The operation being performed, 'view', 'update' or 'delete'.
 *
 * @see hook_node_grants()
 */
function hook_node_grants_alter(&$grants, $account, $op) {
  if (!empty($account->xmlsitemap_node_access)) {
    unset($grants['vocabulary']);
  }
}

/**
 * @} End of "addtogroup hooks".
 */

Screenshot.png -- shows that there is 1 link/page in the XML sitemap, I ran cron.php 4 times

Screenshot-1.png -- here we can see the actual xmlsitemap, just and only the front page

Screenshot-2.png -- there is the list of nodes that I want to see in the XML sitemap, but there is no node context...

Screenshot-3.png -- here I show the status, all is just fine, and it shows you that the CRON process was run very recently -- further down the XML sitemap is said to be generated and ready, and it is indeed downloadable, it's just pretty much useless at this point...

Please, let me know whether a helping hand would be welcome and what should be worked on so this 2.x version becomes a working version. 8-)

Thank you.
Alexis Wilke

AlexisWilke’s picture

Version: 6.x-2.0-beta1 » 6.x-2.x-dev

Just in case, I change the version too, although from what I read here, 2.x and 2.0-beta1 have the exact same problem.

Thank you.
Alexis

Dave Reid’s picture

Status: Active » Postponed (maintainer needs more info)

Well even though #31/32 aren't actually related to this issue, I'll bite.

Please take a screenshot of your admin/settings/xmlsitemap/settings page and the 'node' fieldset. Are all of your content types excluded?

AlexisWilke’s picture

Okay, so I guess I'm an idiot 8-)

Now, the old behavior, if I recall, was for all the node types to be enabled by default... So big surprise! Agreed that #31/32 are not directly linked with this issue.

This being said, which module is supposed to give you a way to name the sitemap you Add? Or are all sitemaps expected to be named sitemap.xml?

At this point we cannot create a new sitemap... there is no context (unless you have i18n) and no way to name the sitemap or when you edit to rename an existing sitemap.

As mentioned by someone here, I tried the Delete to try to track this very problem on a Save of a new sitemap. The smid is considered an integer which did not work with the current version.

  • warning: pg_query() [function.pg-query]: Query failed: ERROR: operator does not exist: character varying = integer LINE 1: DELETE FROM xmlsitemap_sitemap WHERE smid IN (0) ^ HINT: No operator matches the given name and argument type(s). You might need to add explicit type casts. in /usr/clients/www_html/new.m2osw.com/public_html/includes/database.pgsql.inc on line 189.
  • user warning: query: DELETE FROM xmlsitemap_sitemap WHERE smid IN (0) in /usr/clients/www_html/new.m2osw.com/public_html/sites/all/modules/xmlsitemap/xmlsitemap.module on line 441.

Once I fixed the delete, I could remove the existing sitemap and then re-create it and it magically worked. Although I got an error message saying that it was up to date even though it was empty...

Your sitemap is up to date and does not need to be rebuilt.

Here I was testing with a new site where there was no Sitemap 1.x before. I had a problem upgrading from 1.x to 2.x as I mentioned somewhere else. And when I tried to create a new sitemap on those sites, from what I recall, it wouldn't work. I'll try again as I have several other sites with the same problem.

Thank you for the quick answer! (and fixing my problem!)
Alexis Wilke

Dave Reid’s picture

Priority: Critical » Normal
AlexisWilke’s picture

Status: Postponed (maintainer needs more info) » Needs review

Actuall, I should have changed the status, but at the time I had other problems that looked like something else wasn't working.

The "no context" message is definitively a bad one! 8-)

Thank you.
Alexis

tomjoy’s picture

Awesome thanks so much!

johnTEN’s picture

Im having the same problem. I only just installed it and it never generated a map.

ajventure’s picture

I too am having this issue. I have been having constant problems with the sitemap including unpublished pages and since the last update (which was supposed to amend this issue). Today I attempted to update to yet another update of this module as I thought it would address this issue and I unfortunately, as above, cannot even generate a sitemap at all. I have tried many of the suggestions in this report to no avail.

Just wanted to add to the discussion on the topic, to help others to see there continues to be an issue.

Thankyou for the module and time put into the Drupal community.

Anandyrh’s picture

Thanks a lot!

This one is Fantastic!

reikiman’s picture

I appear to have made a duplicate filing (#1139186: Sitemap.xml doesn't have any entries in it on one site, while other sites it has entries)

In my case reading the above comments pointed me to the Inclusion/Exclusion settings as I just described in a blog post: http://davidherron.com/content/potential-and-fix-drupal-xmlsitemap-modul...

Switching nodes and taxonomies and menus to be Included fixed my issues and my site is now generating proper xmlsitemap's

porcupine73’s picture

Version: 6.x-2.x-dev » 7.x-2.0-beta2

I upgraded from 6x 2.0 beta1 to 6x 2.0 beta 2 and then started having the 'There are currently no XML sitemap contexts available' problem again. I remember having this issue when installing beta 1. After messing around for about two hours, I gave up, disabled the add-in, uninstalled it, then reinstalled it, and now it seems to be working.

It seemed like if I clicked the 'update cached files' or 'rebuild links' then that's when the 'There are currently no XML sitemap contexts available' problem started.

One thing I noticed, was, in the xmlsitemap_sitemap table, oh wait, I just noticed the table structure is different between beta 1 and beta 2. I looked in update.php but it said there were no updates available. It looks like beta 2 does away with the context_hash table and adds a max_filesize column. Maybe that's where the problems were?

Uninstalling and reinstalling is a pain, because then all the node types default back to 'excluded' from the sitemap, and, if you have a lot of node types that takes quite a while to go through each one to re-include it.

editing to add: Ok, I'm stupid, I see what I did now. I have about a dozen sites in multisite, so I'm on to the next site. It was the update.php. I saw the xmlsitemap add ins, and those said no update needed, but the xml sitemap engine and something else, those had updates listed. But I didn't notice those the first time so I thought running update.php wasn't needed. It indeed is! This will save me time not uninstalling and reinstalling on the rest of the sites. Thanks for the great add-in!

Anonymous’s picture

Version: 7.x-2.0-beta2 » 6.x-2.x-dev

#42: Since this issue is for 6.x.2.x-dev, please leave it that way. If you have a similar issue for 7.x-2.x then find a suitable issue or create a new one.

paolomainardi’s picture

Subscribe, same problems here.

I have the same problem, the module has created a "sitemap.xml" that is correctly built, with menu, taxonomy and users, as configured by settings.

But "edit" and "add" functionalities seems to be totally broken, with messages like "A sitemap with the same context already exists." with no possibilities to change contexts (what are contexts ?) on "add" interface and the usual "There are currently no XML sitemap contexts available." when trying to edit the default sitemap.

Thanks a lot for this great module but a little bit of documentation would be great :)

dominateyourmarket’s picture

subscribe

almamun’s picture

I had the same problem, cause I have set noconnection for .xml in htaccess. But when I created an url alias without file extension, its working, though "no context" message is there D:

almamun
----------------------------
Dinajpur- My District Portal,
Rangpur-Another Local Portal (Drupal Powered)
Banglajogot- Bangla Web Design Blog (Drupal Powered)
JoomlaBangla - Joomla! Bangla Support Site

grabo’s picture

I have the same problem, waiting for a final stable version for drupal 6 and hope it works better.

Cybergrass’s picture

Version: 6.x-2.x-dev » 7.x-2.0-beta3

With DP 7.8, I cannot generate the XML file.
Also, GoogleNews for 7.x doesn't work either.

The file sites/default/files/xmlsitemap/.../1.xml is there with headers and structure content but no URL content.

I hope this helps you out.
Thanks

Anonymous’s picture

Version: 7.x-2.0-beta3 » 6.x-2.x-dev

Please do not change the version data in a ticket. If you have a differing Drupal version with a similar issue create a new ticket if one doesn't exist already.

The patch in #34 still needs a review by Dave who seems to be MIA.

Cybergrass’s picture

Sorry and thank you Earnie

Cybergrass’s picture

Removal of the 'ad' advertising module resulted in googlenews working fully and properly.

Since the ad module is still premature and somewhat experimental, there was probably a conflict somewhere that impacted googlenews.

Cybergrass’s picture

Removal of the 'ad' advertising module resulted in googlenews working fully and properly.

Since the ad module is still premature and somewhat experimental, there was probably a conflict somewhere that impacted googlenews.

Dave Reid’s picture

Status: Needs review » Active

The patch in this issue has already been resolved, moving this back to active.

polarizz’s picture

big thanks to cdpapoulias, it's work for me.

chlee’s picture

#9 from cdpapoulias worked for me as well. Many thanks.

spiderplant0’s picture

What does "#9 from cdpapoulias worked for me as well." mean exactly? Comment #9 does not offer a solution, he just says else where that he found a solution for him self.

Just to confirm this bug still exists on 6.x-2.0-rc2 and on 6.x-2.x-dev