Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By pamphile on
Let's share our 4.4 to 4.5 upgrade tips !
1. I followed the drupal INSTALL.txt upgrade instructions
---------------------------
1. Backup your database and Drupal directory - especially your
configuration file (www.example.com.conf or includes/conf.php).
2. Log on as the user with user ID 1.
3. Remove all the old Drupal files then unpack the new Drupal files
into the directory that you run Drupal from.
4. Modify the new configuration file to make sure it has the
correct information.
5. Run update.php by visiting http://www.example.com/update.php.
2. But I ran in into database upgrade issues and errors with:
menu table - so I also turned off the menu module and deleted the menu table, there was a conflict with the upgrade script ( someone mentioned they had to delete the menu table this in a thread somewhere :) )
userprofiles: so I also turned off user profiles module
Basically I kept all other core modules turned on but disabled modules which caused problems within upgrade.php script.
I was able to discover all these tricks after 5-6 failed attempts.
I hope your upgrade is easier. Don't give up... !
Marcel
http://scriptdiary.com
Comments
menu vs navigation: battle royale
I am having trouble with my move to 4.5 because it seems like the navigation module and the menu module use different definitions of the same table. (menu)
Am I missing something?
I keep switching out the tables when I want to try the other module (RENAME TABLE menu TO menu_menu; RENAME TABLE navigation_menu TO menu), which seems silly.
Also, the instructions for the navigation module don't reflect the new admin menu (there is no "configure"!)
I would delete or rename the
I would delete or rename the old menu table and create the new one. I also think that the navigation.module isn't needed for 4.5 anymore.
--
If you have troubles with a particular contrib project, please consider to file a support request. Thanks.
--
Drupal services
My Drupal services
I am using Drupal for years...
...but this time I think I'll skip upgrading some of my sites. I am not sure where the problem lies, but on already two sites the upgrade.php simply died with loads of silly errors. I had to handedit the update.php from hwere it died on over four places.
But very important to note, is that those two sites were not 4.4, but CVS sites! However, I have no time yet, to look into this thoroughly (deadlines, contracts, client meetings rushrush)
[Ber | Drupal Services webschuur.com]
Umlauts b0rked, textile.module a wee bit strange, HTML screwed
Somehow, I had a fair share of problems with the upgrade...
1) the textile.module seems to be not quite up to the task>
- When I switch an entry to textile (manually or by SQL statement), all German Umlauts and French accents are broken badly
- it does not recognize old textile nodes and convert them properly - all the 'old' entries where I used Textile v2 have a [textile] in the teaser and in the body. IIRC, when I used textile, the new module should notice this and convert it automatically. I can fix the format issue with the sql statement
update node SET format = 4 where body like '%\[textile\]%'
however, I'm not rid of the [textile] string in the teaser, which I'd also like to do. Any good trick, like a recreation of all teasers across all nodes?
all German Umlauts and French
all German Umlauts and French accents are broken
Sounds like this problem & solution.
all the 'old' entries where I used Textile v2 have a [textile] in the teaser
In input format > configure filters you can set Textile to use the [textile] tags. Maybe that can solve your problem?
Upgrading a live site sounds a bit dangerous
I would expect most serious websites would start by upgrading a test site first. So this is what I have started on myself, but would also appreciate tips from anyone who has gone ahead.
I have duplicated a test copy of a 4.4 website, so that I could trail the 4.5 upgrade and determine what the implications are and be prepared for any difficulties, before actually steaming ahead with an upgrade to a live site.
As expected, I have a bit of work to do to get everything into reasonable order:
- lots of template work (custom phpTemplate based template)
- think about how best to use new features in 4.5
- check permissions and security of profile data
- configure workflow
etc.
I have found the upgrade process quite trouble free, and am looking forward to making use of some of the new Drupal features on a live site...
However, when I have all the issues sorted out on the test site, I am not sure what is the best way to quickly port all those changes across to the live site - to avoid downtime.
I will need the new drupal codebase, modified 4.5 compatible templates and modules working on the test site, the upgraded database schema, all the new settings for a 4.5 install, etc. All of this has to be ported across to the live site as quickly as possible (preferably automated), all without upsetting the live data (registrations, posts, comments, logs, etc.)
I'm sure I'll work something out, but if anybody has already got past this hurdle, I'd appreciate some tips.
Cheers,
Ross.
syncing script
Although I haven't done it yet, I am going to make a 'syncing' script, that will transfer all content and user data from a 4.4 live site to a nearly-ready-to-go-live 4.5 site (on the same server).
Basicly this is to help with the problem I described above.
If other people show their interest, I will put a bit of extra work in to make it usable for other people. It will probably be a shell or perl script, that makes use of mysql client commands.
So the upgrade process would look like this:
1. make a duplicate of a live (4.4) site (www.mysite.com -> test.mysite.com)
2. upgrade the test site from 4.4 to 4.5 (standard update process)
3. take time fixing problems (templates, modules, configuration, etc)
4. run 'syncing script' to get all the latest content and signups into the test site.
5. swap over the test and live sites
The result (from a website visitor's perspective) is a seamless, very quick and trouble free site upgrade.
Interested
I'd be interested in taking a look at it.
-c
Since I'm all about PHP, I wo
Since I'm all about PHP, I would really prefer a PHP version...
but hey as long as it helps someone, I support it...
http://01wholesale.com
This is a rewrite of my above
This is a rewrite of my above first intructions since I can't edit my original post.
1. Backup your database and Drupal directory - especially your
configuration file (www.example.com.conf or includes/conf.php).
2. Log on as the user with user ID 1.
Additional Steps I had to take
-------------------
3. userprofiles: Turned off user profiles module
Basically I kept all other core modules turned on but disabled modules which caused problems within upgrade.php script.
4. menu table - turned off the menu module and delete the menu table - there are conflicts with the upgrade script ( someone mentioned they had to delete the menu table this in a thread somewhere :)
--------------------
5. Remove all the old Drupal files then unpack the new Drupal files into the directory that you run Drupal from.
6. Modify the new configuration file to make sure it has the
correct information.
7. Run update.php by visiting http://www.example.com/update.php.
8. Please read this if your using flexinode:
After upgrading to the 4.5 version of Flexinode, I noticed that my images were deleted from the database. And no default image dimensions and size were given, this caused errors.
So I edited the image settings within each flexinode, one by one. Providing image dimensions and
size.
I was able to discover all these tricks after 5-6 failed attempts.
Don't give up... !
Marcel
http://01wholesale.com
I upgraded three sites over the weekend
Hi all.
I have been playing with Drupal since fall of 2003, when I first learned about (perhaps from a Slashdot article).
I spend a few months playing with it on my test machine at home, getting to know it better, and developing a migration strategy for my sites.
Then, on new year's day 2004, I converted my web sites to Drupal.
Around May 2004, I upgraded to Drupal 4.4.1.
Last weekend, I upgraded to 4.5.0.
Every time before I upgrade, I copy the database dump from the weekly backup of my web sites (you do backups, right?) to my test machine, and do an upgrade locally, and see if there are any problems.
I untar Drupal and other modules and files I want to use, then make this a new tar ball that I copy to my hosting machine and untar it there.
For 4.5.0 the upgrade was fairly smooth. I initally had problems on my test machine related to the menus tables. But that was due to me not cleaning the database between tests. Some newly created tables were left over and confused Drupal.
In input filters, I had to disable the automatic conversion of new line to HTML br tags, because my existing content has line breaks in it.
I was careful to move old directories and files out of the way before extracting the tar ball.
I like the new features, such as being able to put a custom logo in the pushbutton theme, ability to turn off the "submitted by .... on ...." on certain types of content, ability to turn on or off certain things like Slogan, Primary and Secondary links, ...etc.
Well done Drupal team!
Having a test setup is essential to success. And any machine you have now at home can be a test setup actually.
--
Drupal performance tuning and optimization, hosting, development, and consulting: 2bits.com, Inc. and Twitter at: @2bits
Personal blog: Ba
Upgraded from 4.3 to 4.5
I had been hesitant to upgrade my drupal installation (running for over a year) because I was using a module from deanspace that was not compatible with 4.4
This past week I went ahead and upgraded. Backed up the database; ran the update files to upgrade to 4.4 like the install guide says; then wiped all the files and uploaded the 4.5 files and ran the update script.
All my content was visible - in my test with 4.4 in the past my events listings were not compatible. Only thing I had to do was use the 4.5 event module - export the events info from the node table, use sql query to add them to the events table and bam! all events back on the calendar! Lost my linkage to yahoo maps and map quest that was part of deanspace event module, but I will devise another way to do that.
Still waiting for the ability to do recurring events in the event module.
4.4.2 -> 4.5.0 without any problems here!
As the title says...
Cheers!!!
I haven't done any official u
I haven't done any official updates, yet. I have done it in a sandboxed evironment, though.
Like with past upgrades, I can reload the old DB repeatedly and try every "last update" choice available and all will get me errors. The only one that actually worked this time was from 4.3, even though I'm running 4.4.1 now. Using that update worked, but I still got errors.
The biggest holdup for me is that I need to re-build my themes.