Upgrading Drupal

Hey All... Have searched but can't find anything related to 'Save Configuration' failures, so has anyone ever run into this?

- I've installed a new module & go to admin/build/modules to enable
- With the Enable checkbox checked, I hit Save Configuration
- The system returns me to admin/build/modules with no messages (success or failure)
- When I check the module's listing, my changes haven't been registered by the system

I have just upgraded from 5.2 to 5.7 and cannot enable / disable Comments, Content, Contact, Path or Taxmonomy. Can anyone help figure out why this might be. The boxes are grayed out. Please help!

All the translation assigned with Localizer in Drupal 5.7 what will happen after an upgrade to Drupal 6?

Will they all be single nodes with diferent languages and not be connected?

Localizer and Adsense and CCk are the only important Modules that I didnt see that have a updated 6 version, or am i wrong?

Please help me...

I just upgraded my very rudimentary development site from Drupal 5.7 to 6.1. I have some questions about what happened.

First, I absentmindedly ran Drupal after copying the files and it displayed the install script. I started the script and got errors before I realized my mistake. That may account for the errors I got later.

Hi, i have been using drupal for few months and i absolutely love it..

I am using the stable version of cck in my site. However to use advanced profile module, i need the latest development build of cck.I have already created many content types with custom fields . I would like to just update the stable version cck module in my site to the dev version.

I have referred the upgrading handbook. it has a wealth of information about how to upgrade the drupal core along with contributed modules. And it also mentions that running update.php more than once might cause problems.

Hi,

I'm starting to really get itchy feet to upgrade to drupal 6.1 from 5.7 now that fck and imce are nearly over but there is only one module holding me back - the taxonomy access control. Is there any way the functionality of this module can be reproduced in drupal 6.1?

Basically I want to limit which nodes a role can view based on their taxonomy - surely there's a way round this in 6.1??

Thanks,

Richard