We have some lingering issues in our upgrade from Drupal 5 to 6. (Site was originally started in Drupal 4).
We have been getting this php error: PHP Fatal error: Call to undefined function _forum_get_vid() ... MYSITE.ORG/includes/common.inc(1685) : eval()'d code on line 2
The only reference we've been able to find to this was back in 2007 when Drupal 6 was just coming out and it supposedly was "fixed." It also seemed to pertain to the forum module. We are hesitant to try an old patch that supposedly was fixed, but clearly we are having some serious problems. We get the white screen of death during various functions, ranging from changing module preferences, logging in and sometimes even saving content. We have been testing pretty hard on local site which now does this fairly frequently; We've tried disabling the forum module; we removed vocabularies/keywords from forums; we've cleared cache ...
Can anyone shed some light? I hesitate to call this a bug since we haven't seen others experience this recently. ... But we really really would appreciate some help on this.
thanks
geoff
Comments
Comment #1
asimmonds commentedThe eval() is the clue, you probably have a PHP-code node or block that hasn't been updated for 6.x compatibility.
Comment #2
ggevalt commentedHow do I find it?
g
UPDATE: We have gone through all the blocks AND all of our site notes. We know of no blocks with any php coding in them, nor do we know of any nodes with php coding in them. So the question remains, how would we find out if there is some out of date php somewhere?
FYI, we know that all modules have religiously been kept up to date. We know that we had troubles in the initial upgrade from 5 to 6 with book, image and taxonomy modules.
I realize we are asking someone to suggest how we can find a needle in a haystack that may or may not be located in Ethiopia, Australia or Alaska, but if anyone can provide us some more information, this would be great. We are quite worried about this...
thanks
geoff
Comment #3
damien tournoud commentedComment #4
ngudiono commentedsame problem
Comment #5
ggevalt commentedUpdate: We did finally find the issues. It seems to have centered on conversion from Drupal 5 to 6 within images AND a human error problem (ours) on a php-based sort that had been created for us that was out-dated. So, in final analysis, our mistake was in not doing a more thorough search of image nodes that had been damaged and that had also affected a couple of taxonomies.
Case closed.
geoff
Comment #6
ggevalt commented