Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options.
I'm upgrading D6 to 7.14 and have disabled non-core modules etc. update.php is producing a blank page. Searching previous posts suggests a missing default theme is the problem, but this site was running Garland, with the only modification being the colour.
Anyway, the upgrade from 6.25 to 7.x went very smoothly and without error.
However, I started adding the new modules and adding one at a time running update script after each new module, got the error below on, so far, three modules but eight other modules had no errors.
As a side note, the module "drupalchat" worked initially despite this error but has since failed
I have a feeling this will be a fairly hot topic soon.
since 1 month, I got a new webmaster-job for the homepage of our historical community. The reason is sad: A good friend of mine - who mastered everything before - died unexpectedly...
So, what I try now is to update Drupal. The actual version is:
I believe I was following the Drupal upgrade steps to the letter - here is what I was doing:
Updated core and all contrib modules to latest version of 6
Downloaded Drupal 7 and all v7 contrib modules as needed for the site to another folder
Backed up files and database of my D6 site and logged in as user 1 to turn on maintenance mode
Changed default theme to Garland
Disabled all non-core modules
Removed default.settings.php file
Removed all core files and replaced them with the Drupal 7 core
Step 9 on http://drupal.org/node/570162 states the following: Remove uninstalled modules
If you uninstalled any modules, remove them from the sites/all/modules and other sites/*/modules directories. Leave other modules in place, even though they are incompatible with Drupal 7.x. So I did this - left all D6 contrib modules in place
Made settings.php file writeable and ran update.php.
However, when I attempted the above (tried it twice) I got to the ugrade.php screen with the following messages:
I updated my drupal installation with the automated updater. Dont remember what the update was. However after the update only the first page works. All pages in the site menu gives this error message:
Notice: Use of undefined constant MENU_PREFERRED_LINK - assumed 'MENU_PREFERRED_LINK' i i18n_menu_init() (rad 811 av /var/www/vhosts/simon.l/httpdocs/kontrollauto/sites/all/modules/i18n/i18n_menu/i18n_menu.module).
Notice: Use of undefined constant MENU_PREFERRED_LINK - assumed 'MENU_PREFERRED_LINK' i i18n_menu_init() (rad 849 av /var/www/vhosts/simon.l/httpdocs/kontrollauto/sites/all/modules/i18n/i18n_menu/i18n_menu.module).
Notice: Use of undefined constant MENU_PREFERRED_LINK - assumed 'MENU_PREFERRED_LINK' i i18n_menu_init() (rad 851 av /var/www/vhosts/simon.l/httpdocs/kontrollauto/sites/all/modules/i18n/i18n_menu/i18n_menu.module).
Notice: Use of undefined constant MENU_PREFERRED_LINK - assumed 'MENU_PREFERRED_LINK' i i18n_menu_init() (rad 849 av /var/www/vhosts/simon.l/httpdocs/kontrollauto/sites/all/modules/i18n/i18n_menu/i18n_menu.module).
Notice: Undefined index: menu_name i menu_set_active_trail() (rad 2291 av /var/www/vhosts/simon.l/httpdocs/kontrollauto/includes/menu.inc).
Notice: Undefined index: href i menu_set_active_trail() (rad 2328 av /var/www/vhosts/simon.l/httpdocs/kontrollauto/includes/menu.inc).
Similar questions have probably been answered before but I dont see anything that is quite the same focus.
I am really at a stage of evaluating Drupal to see if it will be better for my needs. Coming from a Wordpress situation. In WP anybody slightly savvy builds everything in a Child theme approach, which basically isolates all your individual preferences so that when an upgrade comes around there is no possibility of overwriting new code or css etc