I followed steps 1-8 on the upgrade.txt file, and wasn't quite sure about 9 but I assumed it just meant to ensure that the site was up and working again, which mine was. So I proceeded to step 10, running update.php, however the site ran the update process claiming it finished updates 0 out of 0. Everything says no updates available on update.php. When I go to the Available Updates page, it says I'm running 6.19 and everything is up to date, but none of my modules are listed.
So, I recently got a Drupal site setup, hosted by JustHost.com and with a Template Monster template. JustHost did the initial Drupal install for me (6.17), and it's in the main directory for the website. I see now this security update for 6.19. I've read all the instructions and engaged in some of the posts on here, but feel really nervous. First, I don't know what files in my root directory I need to keep and what I should delete. I've seen the list, but there are also non-Drupal files in that directory, like things for phpmydmin and stuff.
Hello all. I was upgrading from 6.1 to 6.19 and received the error message after a 100% update.php
Fatal error: Only variables can be passed by reference in /sites/all/modules/admin_menu/admin_menu.inc on line 521
I have upgraded from 6.17 to 6.19. Thing were great! Things were looking dandy. Just a few modules to go. Doing them one at a time:
CCK - ok
Pathauto - Fine
Date - Easy as pie
Now I thought I was home and dry:
Token and insert the update.php runs ok but I am getting this error:
Fatal error: Call to undefined function token_get_values() in /home/westoxo1/public_html/modules/page_title/page_title.module on line 447
when I try to access the front page.
I very new at this...I inherit a site that hasn't be maintained for 1yr. 6mo. I want to upgrade from 6.1 - 6.19. I backed up the site and now started to prepare for the upgrade. I can't tell what are the non-core modules. Can't disable the cck- content. Sorry,for the ignorance. Can someone give some advice before I blow up the server!
I've just updated to Drupal 6.19. It is not OK as I expect. The problem is when type http://mysite/cms/update.php , updating was very fast. After updating Drupal 6.19 core, I updated all of new module marked as "Update available".
I am sure that I updated new module in the right way because I did that every week.