Closed (fixed)
Project:
Views Bulk Operations (VBO)
Version:
6.x-1.5
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
4 May 2009 at 22:05 UTC
Updated:
6 May 2009 at 03:53 UTC
Hi,
I"m geting the WSOD when I try to update node taxonomy term. I am using D6 latest & latest VBO 1.5. This happens right after I click confirm, after selecting the term and pressing submit. Any ideas what this could be caused by. I have the module on another site and it seems to be working. I have dried 1.5 and the dev module, with the same issues.
Comments
Comment #1
kaw3939 commentedThe selected nodes are not associated with any vocabulary. Please select other nodes and try again.
I get this error too. I wonder if it is connected. These nodes do seem to be associated with terms, they have terms.
Comment #2
kaw3939 commentedI made a video of the problem:
http://podcast.njit.edu/relay/relay1/test/Views%20bulk%20operation%20WSO...(1024x768)%20-%2020090504%2006.42.37PM.html
No option related to node taxonomy seems to work.
Comment #3
kaw3939 commentedType filefield
Date Monday, May 4, 2009 - 18:51
User admin
Location http://carbon.njit.edu/video/content/5ai-factoring-out-polynomial
Referrer http://carbon.njit.edu/video/
Message FileField was trying to display the file relay1/kwilliam/CAPE-Tutors/mp4/kwilliam_01-05-2009-03-01-33.mp4, but it does not exist.
Severity notice
Hostname 128.235.113.135
Operations
I get this in the log after I try to update the node taxonomy. I wonder why this happens? The file does exist and I can download it from the node.
Comment #4
kaw3939 commentedHi again,
Did a little detective work...
I found that I could update the taxonomy terms for nodes other than a custom content type that I created for a module. I get the error about the CCK file field trying to display in the log. Other node types seem to update just fine.
The only difference seems to be that the node has a video embedded on the page, while nodes that do not, don't seem to have this problem.
Comment #5
kaw3939 commentedI fixed this issue with my module that I was developing, but I don't know how. The new version of the module (has no new code for file uploads) seems to not have any problem. Sorry for all the fuss, but this was driving me nuts I love this module.
Comment #6
infojunkieIs there anything that you need me to verify or fix here?
Comment #7
kaw3939 commentedNo. The only thing that is a bit curious is why your module would have been impacted by something in mine, actually, it seemed to be the CCK file field that was the problem. Thanks for your attention, your a credit to module developers.
Comment #8
infojunkie