My previous excitement with using VBO to add nodes to groups has been dampened with the discovery that there are some problems related to forum topics. I am wondering if anyone has some suggestions on how to overcome this.
When VBO is used to add forum topics to a group it executes without reporting any errors. However, examination of the forums reveals that many, but not all, forum topics show "This topic has been moved" and clicking on this oddly goes to a page that appears like a forum page and has the url http://example.com/forum/xxx where xxx is the numeral of a taxonomy term that was applied to the forum topic. Editing the forum topic still shows the correct forum and the correct taxonomy terms and simply saving the node again restores it to the correct forum.
You can still go to the false forum with the url http://example.com/forum/xxx and the forum topic also appears there with the message "This topic has been moved". I do not think this residual is a VBO problem as you will see when you read on.
Testing on another Drupal installation where VBO has not been used, it is possible to enter the url http://example.com/forum/xxx using the taxonomy number for any existing term. This displays a page that looks like a table display for forum topics with the taxonomy term as the title and the table lists forum topics that have that tag along with "This topic has been moved". So it would appear this is a problem with the core taxonomy module.
However, it is causing problems for VBO when VBO is operating on forum topics.
I don't know if this is enough information to explain the problem.
Fortunately, I do have a backup of the data which I have been able to restore and examine in trying to understand this problem. I would still like to be able to add forum topics to a group and wonder if there might be a fix to permit this.
Thanks,
Izzy
Comments
Comment #1
infojunkieI was able to reproduce that problem. I'll look into it.
Comment #2
izmeez commentedI was just wondering if there are any further thoughts on this problem. I also posted an issue about the Forum and Taxonomy behaviour and there has been some response but I am not sure if it is any help in solving the problem. Those posts are available at http://drupal.org/node/513618
Thanks,
Izzy
Comment #3
infojunkieFixed. Please use the latest dev (12 hours from now) and let me know if it works.
Comment #4
izmeez commentedI'm sorry to report but this does not work for me.
I am not sure if I am contributing to the problems. I already had two views for vbo for different roles, one with some limited options for one role and the other with more options for another role. I updated the module to the latest dev version and had the same results on the forum posts as before.
I also noticed a couple of other problems which may be related to other issues or just cosmetic for now.
I am unable to select multiple content types using the ctrl or command key. Again possibly this has to do with my particular views.
When there are multiple pages of nodes listed if I select all and then select the button for all nodes not just those on the page displayed, after selecting the group to add the nodes to I get a message that 0 rows have been selected and whether I confirm or cancel none are changed.
Also, and this is cosmetic, after selecting the nodes to add to a group, on the next display where the group is selected the "Next" button looks like a button while the "Cancel" is just text and does not properly align with the "Next" button. On the next display, the "Confirm" button looks like a button while the "Cancel" does not but both are aligned.
I don't know if you want me to bother to highlight these as separate issues.
I look forward to your thoughts.
Thanks,
Izzy
Comment #5
infojunkieLet's keep the cosmetic issues separate. In general, I am not inclined to fix them if they can be addressed by fixing the theme or CSS. Concerning UI mis-behaviours, before posting an issue against VBO, please check the behaviour with other View styles (especially Table). If the behaviour is the same, then the issue probably belongs to Views itself.
Concerning the forums issue: Can you confirm that the file taxonomy.action.inc now contains the text "Reassemble a taxonomy array that can be saved." ? This indicates that the fix is present.
Also, please make sure you're not inadvertently using 2 copies of VBO in the same installation.
Comment #6
izmeez commentedI have confirmed that the text "Reassemble a taxonomy array that can be saved." is present in the version used.
There is only one version of the VBO module on the site. However, I do have two Views that use VBO and hope that is not the cause of any problems.
Thanks,
Izzy
Comment #7
infojunkieIn modules/forum/forum.module, function
forum_nodeapi, please addright after
You will need to enable devel.module to see some output. What do you see?
If you see a blank value, then add
right after
What do you see?
Comment #8
izmeez commentedSorry, we had to move on and had the changes entered manually. Clicking on the forum topic edit, selecting group and public or not settings as required, and save worked without problems. Just a tedious clerical job that would have been nice to avoid but doable in this particular case.
Hopefully, someone else with the same need will be able to follow-up.
Izzy
Comment #9
infojunkieComment #10
izmeez commented@infojunkie Sorry, we never did get a chance to test your suggestions, but we noticed the Drupal 6.16 update has a fix related to the forum module, http://drupal.org/node/422218
I am wondering if this will resolve the problem?
Back in January we tried the VBO dev version for a bulk change to add forum topics to a group without applying any patches and ran into the same problem as before.
Sorry, we do not have time to perform any tests on this right now, but I thought a post here might be helpful to others and maybe someone else will be able to report back their experiences.
Thanks,
Izzy
Comment #11
infojunkieI'm not sure the recent fix would be related to the problem here. Further, I wasn't even able to reproduce the problem after my initial fix, so I really don't know what to test for.
I'll close this issue for now until someone bumps into the same problem and re-opens it. Thanks for the heads-up.
Comment #12
izmeez commentedMaybe postponed would be a more appropriate status for this issue?
Comment #13
bojanz commentedSince nobody provided further info, closing the issue.