I've just gotten through updating a bunch of modules for my site, but two stubbornly refuse to change: Bluemasters and Webforms. I'm having problems with Bluemasters not showing any of my Webforms as it is, but I thought I would try updating both to see if that helped at all.
This site isn't live yet, so I went though and updated a bunch of things (wysiwig, drupal from 7.0->7.9, clock, various field modules, some themes) and the two things that refuse to update are those two.
Hi All,
I upgraded the my drupal multi-site installation from 5.x to 6x. It upgraded only the shared table of multi-site but it does not upgrade the specific tables e.g if i have different menu on another site so it did not upgraded. Any idea how i can upgrade the menu table of another site manually?
I've just upgraded from d5.23 to d6.22. All modules inactive (except Taxonomy because of the Forum module issue). Did the update and got this:
* user warning: Table 'db_name.cache_block' doesn't exist query: DELETE FROM cache_block WHERE expire != 0 AND expire < 1320801507 in /includes/cache.inc on line 165.
* user warning: Table 'db_name.cache_block' doesn't exist query: TRUNCATE TABLE cache_block in /includes/cache.inc on line 171.
I just updated from Drupal 6.19 to 6.22. Everything went OK for the most part, but after running update.php, my primary links are no longer showing up on the Home Page. If I go to any other page, the primary links are just fine, but on the Home page, where the menu should be, it shows "The requested page could not be found.".
I've rebuilt the menus, re-ran update.php, cleared caches and kicked the side of the machine.
I know it sounds like a dumb question but I don't to mess up the site, do I need to turn off the old module to upgrade to the new version or can I just upload the new folder of the module?
We're running Drupal on 64-bit Red Hat Enterprise Linux Workstation release 6.1. We're runnng Apache 2.2.15-9 and PHP 5.3.3-3. We've configured Apache to use virtual hosts and have set up two Drupal sites using the same core, using the multisite configuration. One of the sites is older and has some content; the second was just recently created and has not been modified from the original installation.