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 looking for a way in Drupal 6 to restrict users in where they can place menu items. In Drupal 5 there was the option 'Restrict parent items to' but this seems to have been replaced in D6 with 'Default menu for content'.
The handbook says that:
Drupal 6 allows you to select which of your site menus is selected by default in the content authoring form. All other menus are still visible/accessible within the Menu settings drop-down, but you can shepherd your user to use the menu of choice.
I apologize if this is a dumb question, but please understand I am incredibly new to Drupal. I've tried searching for an answer, but have been unable to find concrete instructions. I currently have a site that's running Drupal 5.7, and I'd like to upgrade to 5.9. I understand I'll need to upgrade to 5.8 first, then 5.9, but could someone please explain to me in the most simple language possible how to do that?
I recently decided to start my upgrade to version 6.3, and I was following the instructions on the upgrade.txt until the point where it said to delete all the files, and proceeded to do so then I realized that I had not backed anything up except for the files directory. So here I am without a config file anymore.
I recently upgraded my site from 5.3 to 6.3 using a fantastico script drupal is up and running fine.But one problem that I've encountered is that attachment files to my node pages do not display. I receive the message "the requested page could not be found'. One thing I've noticed is that my My file system path: is set to "files/drupal4" and set to public and the path that is displayed under my attachments when viewing in edit is http://www.domainename.com/files/drupal4/filename.pdf
I have just run a prototype upgrade on my home pc for 5.7 to 5.9. It worked but with the usual bugs regarding categories/forums/help tips.
The install instructions I followed as per the upgrade.txt file.
I think those instructions are written for upgrades from 4.X to 5.X type upgrades.
I do not believe I should have to fiddle about dis/enabling modules like the upgrade.txt file says. This is time consuming and difficult given the module dependencies involved (yeah I am a lazy bugga).
Here's a list of files changed by the latest Drupal upgrades. We use this so we don't have to replace the entire Drupal installation, as usually only a few specific files have actually changed.
Update: In the 5.9 changed files list and going forward, I'm not checking core module .info files, which always update. This way you can see exactly which core module files changed.