Upgrading Drupal

can anyone advise on multisite updating, when using SEPERATE database for the secondary (non-default) sites?

the multisite was working fine under 4.6, the update to 4.7 has worked fine for the primary site.

but the seperte database for the secondary / sub-domain site doesn't work - clearly the db needs updating...
can I do this simply by add copying update.php to the sub-domain folder under /sites and then browsing to the subdomain.mainsite.co.uk/update.php?

thanks....

I just spent an hour trying to get the taxonomy_access module to work. Following the instructions from the INSTALL.TXT that came with it, it says:

INSTALLATION:

1) COPY taxonomy_access.module to your drupal installation's module directory

2) ACTIVATE THE MODULE from administer >> modules

3) ENABLE TAXONOMY ACCESS SETTINGS: Go to administer >> settings >> taxonomy_access and enable the module

4) CONFIGURE ACCESS PERMISSIONS to the various categories from administer >> access control >> category permissions

NOTE: DATABASE TABLES are automatically added to database. Module creates two tables in database: 'term_access' and
  'term_access_defaults'.

It does NOT automatically add the 2 tables to the database. I know because I started fresh...I deleted those tables due to errors after upgrading to 4.7.0. I had to use the taxonomy_access.mysql file from version 4.6. Naturally I had errors since I needed to follow the UPDATE.TXT file so it will work in 4.7.

So I opened up the UPDATE.TXT file and followed these instructions:

UPDATING
--------

1. Backup your database.

2. Log on as the user with user ID 1.

3. Run update.php by visiting http://www.example.com/update.php.

Absolutely nowhere in any of the "help" TXT files does it say that you have to upload any other files. But when it comes down to it, you need to upload the whole taxonomy_access folder so you can get the taxonomy_access.install file up. Naturally when I saw the file I figured it would need to be used...but since it was NOWHERE listed in the INSTALL or UPDATE files, I was dubious about using it. After exhausting all other options, I finally just had to use the 4.6 taxonomy_access.mysql file and upload the install file, run the update.php and pray.

Ok, the errors were not really indicative of the problem on my site.

The script will not do a lot. Indicative is that there are no tables generated, and that one won't see the progress indicator.

There should be a warning in UPGRADE.txt concerning this subject.

When upgrading from 4.6.5 to 4.7 I get an error: Unknown column 'access' in 'field list' query: UPDATE users SET access = 1147026055 WHERE uid = 1 inincludes/database. mysql.inc on line 120.

This error appears in the log 3 times.

I had a working system using the event plugin. I had created my own content type called "diary date"

After upgrading (with no errors) i now dont have the content type of diary date any more. I can see all the old diry date entries that I had created but if i try and edit them they have forgotten the fields that i had defined (start date, where, contavt name etc)

If i go to admin / settings / content types i can see page, poll and story but not "diary date" and i dont seem to have an add new option.

I've put this into the upgrade forum as I can only assume it's not a co-incidence that this happened while I was trying to upgrade another site to 4.7.

My live site currently runs 4.6.6. I decided this weekend to try and upgrade to 4.7. I expected there to be problems so I created a copy of my live site in a subfolder of my webspace (my live site lives in the root folder currently), exported a copy of the database and loaded it into a seperate on. I changed the base url to point to the subfolder of the upgrade subfolder site and pointed it towards the separate database. In my head I now have two seperate sites running off 2 different databases so I could safely try and upgrade the subfolder site while leaving my main live site untouched.

This was possibly mistake number one.

I proceeded to try to upgrade and failed (as expected) with many errors but I figured that the main live site was still ok so I had nothing to worry about and a quick look at the main site made me think that it was still ok.

Mistake number two methinks.

This morning, one of my users added a post which made me take another look at it in detail and I now find that some of my links where image assist has inserted code for thumbnails have broken. It just leaves the filter code displayed in the post rather than replaceing it with the thumbnail. The files still exist in the files folder and you can still see them in the galleries ok. If you edit one of the broken posts you can get image assist to load and insert an appropriate code but when you subsequently submit the post, the broken code remains. The really odd thing is that in some cases the links are ok and the thumnails from image assist work fine. It doesn't seem to be time dependent.