Upgrading Drupal

Hi,

I'm upgrading a drupal 4.5.2 to 4.6.5 and I wish to install views and banner.
The upgrading of the core was sucessfully, except some problems with image that I resolve.

I install many modules on 4.6.5 like taxonomy_dhtml, taxonomy_xml, event,
When I move views, banner or epublish directory to /modules I can't access /admin/modules and in the log there isn't any error.

I'm really lost

Thanks

Silenciario

The other day I was trying to upgrade an Drupal powered webportal, and got the following errors during updated:

NOTE: upgrading from pre-4.7-head to 4.7 beta 4

Error while upgrading:

#############ERROR##################

Update #151

* INSERT INTO {menu} (mid, pid, path, title, description, weight, type) VALUES (1, 0, '', 'Primary links', '', 0, 115)
* Failed: INSERT INTO {menu} (mid, pid, path, title, description, weight, type) VALUES (2, 1, 'node/562', 'apples', 'bananas', 0, 118)
* Failed: INSERT INTO {menu} (mid, pid, path, title, description, weight, type) VALUES (3, 1, 'colours', 'Books', 'james', 0, 118)
* Failed: INSERT INTO {menu} (mid, pid, path, title, description, weight, type) VALUES (4, 1, 'poll', 'Polls', '', 0, 118)
* Failed: INSERT INTO {menu} (mid, pid, path, title, description, weight, type) VALUES (5, 1, 'weblink', 'Links', '', 0, 118)
* Failed: INSERT INTO {menu} (mid, pid, path, title, description, weight, type) VALUES (6, 1, 'blog', 'Blogs', '', 0, 118)
* Failed: INSERT INTO {menu} (mid, pid, path, title, description, weight, type) VALUES (7, 1, 'forum', 'Forums', '', 0, 118)
* Failed: INSERT INTO {menu} (mid, pid, path, title, description, weight, type) VALUES (8, 1, 'image', 'Image Gallery', 'Photo albums, etc.', 0, 118)
* Failed: INSERT INTO {menu} (mid, pid, path, title, description, weight, type) VALUES (9, 1, 'http://mywebsite.com', 'california', 'hotel', 0, 118)

Overall, an upgrade to 4.6.5 I just did to a Drupal test site went well. Software is Apache 2.0.55, PHP 4.4.2, and PostgreSQL 8.1.3. Old content is still available -- no problems encountered there -- but I noticed something odd while doing some testing. Comments are configured to be viewed as threads in chronological order, oldest first. That seem to be getting done properly. The problem is that the indentation of the replies to threads is incorrect.

I created a small test story and added six comments. What I expected to see was a set of comments that looked like:

comment 1
        comment 1.1 (reply to comment 1)
comment 2
        comment 2.1 (reply to comment 2)
comment 3
        comment 3.1 (reply to comment 3)

Instead, what I'm seeing is:

comment 1
        comment 1.1
        comment 2
                comment 2.1
                comment 3
                        comment 3.1

Whatever is causing this goofy indentation doesn't appear to be theme-related. I've tried all the default themes that are shipped with the core release and get the same results regardless of the theme in use.

Any ideas on what might be the cause of this?

BTW: I have another site running v4.6.3 with Apache 2.0.55, PHP 4.4.2, and PostgreSQL 8.0.3 that doesn't exhibit this comment indentation problem.

Hello,

I'm relatively new to Drupal and wanted to take advantage of the JavaScript features in 4.7, so I decided to try to upgrade my installation from 4.6.5 to 4.7 beta 4.

I followed the instructions in upgrade.txt, but when I tried to load the update.php function, I received an error (this was even before I clicked the "run the database upgrade script" link):

After updating to drupal 4.7b4, I found that both anonymous and authenticated users couldn't log in any longer. I checked the users_roles table and found it were emptied. I also checked the logs of updating and found :

Update #171
DELETE FROM {users_roles} WHERE rid IN (1, 2)

I also checked the update scripts and found:

Hi,

We're creating internal documentation for initial site roll-out purposes. Basically the whole move the working Testing site to an existing non-Drupal Production site. (See the sanitized working doc below) The existing http://drupal.org/upgrade/copying-your-test-site-via-command-line and http://drupal.org/upgrade/copying-your-test-site-via-GUI don't seem to answer a couple of questions.

Q1) As the current production version of Drupal is a moving target, the testing site will invariably be a release or two out of date (e.g. 4.6.2 vs. 4.6.5). Are there any problems with truncating the tables of a greenfield install (4.6.5) and SQL inserting all data from the testing system (4.6.2) into the new database? (See section : Copy Data)

Q2) Are the database/table changes between 4.6 and 4.7 small enough that this same methodology can be used to upgrade from 4.6 to 4.7?

Thanks,

M.J. Taylor
Publisher
from Reason to Freedom

==== Rollout Documentation ====

Constraints:
Non-*nix trained operator

Using:
cPanel and Fantastico

Base Path:
{private data deleted}/drupal/staging

==== Begin Rollout Instructions ====

: Login
login to Control Panel

: Clean Install to Production
[Fantastico, Drupal, New Installation]
follow prompts
{private data deleted}

: Add table(s)
[phpMyAdmin, select Database, SQL, Copy&Paste from:]