By wellsy on

Ok I intend to cautiously upgrade to drupal 4.6.4.....via a test site
I have an existing 4.6.3 site running live with fair traffic so I want no disruptions at all to that site.

Is it possible to install the 4.6.4 site then dump the data using MyPHPAdmin from a backup of the 4.6.3 site?

I have searched and can find nothing regarding this query.

My experience so far is that it is hard enough getting a duplicate site running at a different location using two installs of 4.6.3 so I am very concerned about the results of a 4.6.3 backup dumped to 4.6.4. Does anyone have any experience with this yet?

Thanks in advance!

⋅ Categories: Drupal 4.6.x

Comments

bryansd’s picture

bryansd commented

As far as I know, there are no changes to the database structure going from 4.6.3 to 4.6.4.

wellsy’s picture

wellsy commented

Just to give a little feedback which may help others.

It seems there is no problem if you have a 4.6.3 site to simply upload the 4.6.4 files to a new directory in your web server to test first.

In my case I have the below setup for 4.6.3 www.mysite.com.au/drupal/ and for 4.6.4 www.mysite.com.au/drupal01/

First I suggest you first disable all 3rd party modules in your 4.6.3 site (admin/modules)

Then....
Set the settings.php (4.6.4) to relate to that path and login to check all is OK. If you have the 3rd party modules disabled all should be ok when you navigate to www.mysite.com.au/drupal01/

If that is the case you can then safely upload all the 3rd party modules and enable all required for your puposes.

Then once you are satisfied all is working you can simply rename the drupal01 diectory to drupal and again edit settings.php (it needs to be edited to the new path).

Thats it you should now have a working 4.6.4 installation

Some possible issues:

you may have to modify your style.css if that was not standard and any other changes made to sundry other theme files etc.

wellsy

orchidsonline.com.au

spyjournal’s picture

spyjournal commented

I have 3 (three) 4.6.3 sites going now.
I was wanting to be able to upgrade them so as to keep current and in front of security issues like those listed as being the reason for the upgrade. I have heaps of 4.5.3 sites that I am just NOT going to upgrade. I will just replace them at opportune times in their life time.

If there was an easy upgrade then I would, but each of these sites has heaps of 3rd party modules - flexinode, taxonomy access subscriptions etc. There are user communities in each case and I dont want to cause disruption to them. 2 of them are for clients. The third is my test site that I and my staff use. Each of them has modified (customised) themes and templates

If there are no changes to the database then why cant we just replace the core files (exluding the themes and modules) and the conf files? Surely this would just work!!!

I'm not sure I want to do this but i guess i will.....Thanks for the suggestions on how to do it with a copy. I'll try that first on the test site to see what issues it has.

wellsy’s picture

wellsy commented

in these forums I was a little bit wary. So I have tested the above on a test area. The good part of the above is the new 4.6.4 site will run simultaneously (on the live database) and you can do all your checking first. Sure the site functionality will be affected while you have the 3rd party modules disabled but this can be done very quickly and if all is ok a quick change of directory name has the site switched over to 4.6.4.

Anyway someone else (more knowledgeable than me) may be able to get back with the update.php answer.

wellsy

orchidsonline.com.au