This forum is for questions about upgrading an existing Drupal site. Don't forget to read the UPGRADE.txt file that comes with every Drupal download.

Update to 4.6.0 - database problem

I finally dared to upgrade my 4.5.0 to 4.6.0 . running the Update script, I get the following error:

user error: Duplicate entry '56-239' for key 1
query: ALTER TABLE term_node ADD PRIMARY KEY (tid,nid) in /home/httpd/vhosts/skydance.at/httpdocs/includes/database.mysql.inc on line 66.

ALTER TABLE {term_node} ADD PRIMARY KEY (tid,nid)
FAILED

Looked into the database, and just about all of the "tid" values are there multiple times.

The site seems to work fine, though.

What can I do? Is this critical?

Problem in the 4.6.2 upgrade - node.module

Problem in the 4.6.2 upgrade - node.module

I upgrade my site from 4.6.1 to 4.6.2 and notice that the Default 403 (access denied) page does not work anymore. My Default 403 (access denied) page is node/35.

The page setting for the Default 403 (access denied) page can be found on the administer >> settings page under “Error handling”.

To fix the problem, I had to restore the node.module file from version 4.6.1.

4.6.2 Upgrade still page not found

I recently upgraded two live sites and the test site on my local machine from 4.6.0 to 4.6.1, after doing this whenever an anonymous user tries to access a node that has had permissions set to authenticated they receive a “Page not found” message instead of “Access denied”.

I have since upgraded to 4.6.2 with not change to the situation, this problem can be seen at www.avondescent.com.au (select competitors) and www.clubswa.com.au (select members only).

Confused about the 4.6.1 to 4.6.2 upgrade instructions

The 4.6.1 to 4.6.2 upgrade instructions states the following:

" To upgrade from Drupal 4.6.1, upload all of the files and directories in the Drupal 4.6.2 package to your webserver, replacing older copies of the files. As with any upgrade, it is a good idea to backup of your site and database first. No API or database changes have been made since Drupal 4.6.1 so all contributed themes and modules that work for 4.6.0 and 4.6.1 will work with 4.6.2."

Problem:
I did exactly what these instructions said and it resulted in access denied to the site after the upgrade. Therefore I had to restore back to version 4.6.1 to restore access the site again.

Questions:
The patch instructions are stated as follows:

To patch Drupal, use the patches below:

For Drupal 4.6.1:
http://drupal.org/files/sa-2005-002/filter-4.6.1.patch
http://drupal.org/files/sa-2005-003/xmlrpc.patch

The patch method from the above two links show the following files being modified. Do I only need to replace these files for the upgrade?

Index: modules/comment.module
Index: modules/filter.module
Index: modules/node.module
Index: includes/xmlrpc.inc
Index: includes/xmlrpcs.inc

Then I searched and found a post at http://drupal.org/node/26158 and it stated that one needed to replace all the following files:

database.pgsql
common.inc
image.inc
menu.inc
theme.inc
xmlrpc.inc
xmlrpcs.inc
blogapi.module

Forum categories and personal image gallery

Hi. I upgraded the test/development site of my site from drupal 4.5.2 to 4.6.2. Some of my modules are modified, included contributed ones such as image.module. So far no major problems and everything went smooth. However I am confronted with two issues:
1) The forum entries lost their categories. I had a vocabulary only for the forum.
2) I did not find a way to activate the "personal gallery" of an authenticated user. Therefore now I do not have a quick link to see all images contributed by a user.
I need both features for my production site. Somebody knows how to:

4.6.2 Upgrade (?) - can't login

I just moved my installation to another system and at the same time applied the 4.6.2 upgrade. On the new server I can't login. When I enter the credentials it just loads the same page again, nothing happens. In the watchdog table it shows the usual successful login message.

I applied the same upgrade to some other sites I take care of and neither of them have this problem.

Anyone seeing (seen) anything like this?

Pages

Subscribe with RSS Subscribe to RSS - Upgrading Drupal