By vv7 on
i've update Drupal several times in the past with no problems.
however, after updating my 6.8 to 6.9 i am now faced with the following error:
Fatal error: Call to undefined function: node_types_rebuild() in /home/covoare2/public_html/daihinia/includes/common.inc on line 3653
this error also happens when i try to clear the cache.
any ideas or clues on how to resolve this?
Comments
No answer for you but reaction....
I'm so sorry but, as a newbie, I don't have an answer for you. Wish I did.
However, your post, along with others who experience upgrade problems, does cause people like me to be very reluctant to upgrade versions. When I think of the possibility of downtime and the time/frustration that is associated with a non-developer trying to find a fix, I am reluctant to upgrade. Please don't misunderstand me. I'm not saying that people should avoid posting requests for help. Instead, I'm saying that the perception created by the posts is that the upgrade step may result in more work and complexity on my already very busy desk. Avoidance, unfortunately, is the resulting (unhealthy) behavior.
I wonder if upgrading will ever be easier or if it's as easy as it can be now?
** postponing upgrade from 6.8 to 6.9 until sufficient time has passed to enable me to see the types of problems people experience and the solutions.
Make sure that all files
Make sure that all files were uploaded and readable by the webserver. In particular, check
modules/node/node.module--
The Manual | Troubleshooting FAQ | Tips for posting | How to report a security issue.
checked. all okay. i've
checked.
all okay.
i've uploaded all of drupal once again to make sure, yet the problem persists.
other ideas?
Check the system table in
Check the system table in your drupal database and make sure the node module has status 1 and is at the expected path (modules/node/node.module).
--
The Manual | Troubleshooting FAQ | Tips for posting | How to report a security issue.
bingo! for some reason,
bingo!
for some reason, status was set to 0.
corrected it to 1 and now my site is back online.
thank you very much for your help!
fatal errors during Kickstart install
Thanks a million Heine,
That helped me get past the error too, but then I got a dozen AJAX HTTP errors. Is there a "cookbook" for doing a Kickstart install when you already have PHP and MySQL installed and running on an Apache localhost on Windows? I am getting really frustrated hitting these problems one at a time:
enable PDO_mysql in php.ini
enable gd2.dll in php.ini
disable mysqli.dll in php.ini (because I am using MySQL)
regards,
DJ
I don't think this will be
I don't think this will be of any use, but we just upgraded from 6.8 to 6.9 without a problem.
We used CVS, so maybe something's wrong with the package?
Maybe bit too much wrong..? yes many mods, so %tual not thatmuch
Drupal Upgrade Tutorial (from 6.x to 6.y)
http://drupal.org/node/287824
I'm afreight I've reached my psychological limits after 2,5 week trying to setup a drupal6.8 site (after I'd quit similar work 2 years ago with an early 5 series) and wont 'upgrade' (& that might be the problem; there is no upgrade; its more a new install & then trying to get the old site back).
6.13 Fatal error: Call to undefined function node_types_rebuild(
I am trying to do an upgrade from 6.12 to 6.13 and got the same error message (and a few others!).
I changed the said table row to '1' , checked the path 'modules/node/node.module', re-ran the update.php and it still doesn't complete.
The table row is reverted to '0' after running the update.php.
Are there any more tips for the upgrade to 6.13?
P-L-E-A-S-E.
Report Back
Well, this is the SHORT version of how we 'solved' our issue.
Set up absolutely fresh install of 6.13 files in new folder on site.
Had to alter the above-mentioned table row to '1'.
Ran update.php WITHOUT ANY ADDED MODULES.
Add the modules back in and ran update.php again (had to rebuild content_access but this is expected).
Renamed folder to where original install was.
Hope this helps someone.
Follow up - the day after
Whilst using the site after the upgrade to 6.13 I found that the Book navigation and structures were gone. They were also not listing in the menus. New content being created did not assume an automatic path alias either upon saving the node or doing a bulk update via the Pathauto admin area.
The dev version of Pathauto was tried as this was our gut feeling of where it was going wrong (because books may have been breaking as they couldn't 'read' the Pathauto alias for the nodes and also because a new alias could not be created on adding new content), but this did not solve our problem.
So....the site was reverted to 6.12, where all works again as it did.