I developed a demo site for client using 4.6.3 version and now i'm going to develope a product using drupal by using 4.6.5 OR 4.7 ,I want to inherit the changes that already done in demo site(4.6.3) to latest drupal release ie 4.6.5 How can i do ...
I feel your pain. It took me a bit to figure this out, but I had node problems...see http://drupal.org/node/40526.
Actually, I came to realize it was database problems. What I did was I upgraded to the most current stable version. As of now it is 4.6.5, BEFORE upgrading to the 4.7 series. It worked right off. I believe the thinking by the developers is that upgrades must be done from the most stable current versions, which makes good sense. So, 4.6.3 is not the most current version, 4.6.5 is. I hope this helps.
even though others here have claimed that 4.6.3 database is the same as 4.6.4 and 4.6.5
well I ran update from 4.6.5 and guess what?
Nuked the database! Totally useless for 4.6.5 and 4.6.3 now.
So I reinstated the original database and both 4.6.3 and 4.6.5 installs run fine (they share the same database).
So just for the hell of it I thought why not try the update script in 4.7.0 beta2 again.
So off I go
The proceedure seems to be going trouble free....I even see a screen for a few milliseconds which I have not seen before....a progress bar flashes by.
Then the proceedure claims to be finished.
*********************************************
Drupal database update
Updates were attempted. If you see no failures below, you may proceed happily to the administration pages. Otherwise, you may need to update your database manually. All errors have been logged.
Reminder: don't forget to set the $access_check value at the top of update.php back to TRUE.
main page
administration pages
*********************************************
Warning: Unknown column 'referer' in 'field list' query: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (0, 'php', 'Unknown column 'cache' in 'field list'\nquery: UPDATE sessions SET uid = 0, cache = 0, hostname = '60.226.8.229', session = 'messages|a:0:{}', timestamp = 1136810892 WHERE sid = '0b9a5bf459dd97dc8bb8267967e5bc2f' in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive470-beta2/includes/database.mysql.inc on line 108.', 2, '', '/interactive470-beta2/update.php?op=finished', '', '60.226.8.229', 1136810892) in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive470-beta2/includes/database.mysql.inc on line 108
So there looks like some problems.
Then I try to go back to the admin area.
Warning: Unknown column 'referer' in 'field list' query: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (0, 'php', 'Unknown column 'referer' in 'field list'\nquery: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (0, 'page not found', '<em>admin</em> not found.', 1, '', '/interactive470-beta2/?q=admin', 'http://www.orchidauction.biz/interactive470-beta2/update.php?op=finished', '60.226.8.229', 1136811081) in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive470-beta2/includes/database.mysql.inc on line 108.', 2, '', '/interactive470-beta2/?q=admin', 'http://www.orchidauction.biz/interactive470-beta2/update.php?op=finished', '60.226.8.229', 1136811081 in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive470-beta2/includes/database.mysql.inc on line 108
Home
Page not found
user warning: Unknown column 'referer' in 'field list' query: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (0, 'page not found', '<em>admin</em> not found.', 1, '', '/interactive470-beta2/?q=admin', 'http://www.orchidauction.biz/interactive470-beta2/update.php?op=finished', '60.226.8.229', 1136811081) in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive470-beta2/includes/database.mysql.inc on line 108.
Warning: Unknown column 'referer' in 'field list' query: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (0, 'php', 'Unknown column 'cache' in 'field list'\nquery: UPDATE sessions SET uid = 0, cache = 0, hostname = '60.226.8.229', session = 'messages|a:0:{}', timestamp = 1136811081 WHERE sid = '0b9a5bf459dd97dc8bb8267967e5bc2f' in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive470-beta2/includes/database.mysql.inc on line 108.', 2, '', '/interactive470-beta2/?q=admin', 'http://www.orchidauction.biz/interactive470-beta2/update.php?op=finished', '60.226.8.229', 1136811081) in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive470-beta2/includes/database.mysql.inc on line 108
So I go and look at the db.....its basically unchanged.
Still even works for 4.6.3 and 4.6.5!
Dose not solve the dilemma of getting some data into 4.7.0 beta2 though.
That's it I give up folks!
I have just worked it out roughly that I have wasted nearly 40 hours trying to get data into 4.7.0 betas 1 and 2.
I will not waste one more minute on it until I hear news that it is set in stone, guaranteed, to be a working update proceedure. I would advise all who are considering it to think carefully before wasting your time...no matter how good 4.7.0 sounds it just is not worth it!
I too have wasted many hours-it's called learning! First, drink a beer. Then proceed. This worked for me. Just try it. Go from 4.6.3 to 4.6.4 to 4.7.0-beta1. I have done this procedure 3 times. They worked all 3. Turn off all noncore modules. Be sure that the update version is correct. The Drupal update script says you don't need to choose the update version because it does it automatically. False. By choosing different update versions you get different results. It sounds kooky but it's true. Good luck.
Comments
I would like to do the same
however there seems to be a distinct lack of ideas how to successfully achieve that end.
update.php does not seem to work....be very careful. It nuked two of my 4.6.3 databases rendering them useless for me.
I am working out my own method at present however not so much time to be able to do that right now.
I will follow this thread with interest for others advice.
wellsy
orchidsonline.com.au
I too waiting for experienced developer reply.
Hi,
I developed a demo site for client using 4.6.3 version and now i'm going to develope a product using drupal by using 4.6.5 OR 4.7 ,I want to inherit the changes that already done in demo site(4.6.3) to latest drupal release ie 4.6.5 How can i do ...
I had the same problem...
I feel your pain. It took me a bit to figure this out, but I had node problems...see http://drupal.org/node/40526.
Actually, I came to realize it was database problems. What I did was I upgraded to the most current stable version. As of now it is 4.6.5, BEFORE upgrading to the 4.7 series. It worked right off. I believe the thinking by the developers is that upgrades must be done from the most stable current versions, which makes good sense. So, 4.6.3 is not the most current version, 4.6.5 is. I hope this helps.
wim
ok i read your idea and thought why not
even though others here have claimed that 4.6.3 database is the same as 4.6.4 and 4.6.5
well I ran update from 4.6.5 and guess what?
Nuked the database! Totally useless for 4.6.5 and 4.6.3 now.
So I reinstated the original database and both 4.6.3 and 4.6.5 installs run fine (they share the same database).
So just for the hell of it I thought why not try the update script in 4.7.0 beta2 again.
So off I go
The proceedure seems to be going trouble free....I even see a screen for a few milliseconds which I have not seen before....a progress bar flashes by.
Then the proceedure claims to be finished.
*********************************************
Drupal database update
Updates were attempted. If you see no failures below, you may proceed happily to the administration pages. Otherwise, you may need to update your database manually. All errors have been logged.
Reminder: don't forget to set the $access_check value at the top of update.php back to TRUE.
main page
administration pages
*********************************************
So there looks like some problems.
Then I try to go back to the admin area.
So I go and look at the db.....its basically unchanged.
Still even works for 4.6.3 and 4.6.5!
Dose not solve the dilemma of getting some data into 4.7.0 beta2 though.
That's it I give up folks!
I have just worked it out roughly that I have wasted nearly 40 hours trying to get data into 4.7.0 betas 1 and 2.
I will not waste one more minute on it until I hear news that it is set in stone, guaranteed, to be a working update proceedure. I would advise all who are considering it to think carefully before wasting your time...no matter how good 4.7.0 sounds it just is not worth it!
wellsy
orchidsonline.com.au
update to 4.6.4 first
I too have wasted many hours-it's called learning! First, drink a beer. Then proceed. This worked for me. Just try it. Go from 4.6.3 to 4.6.4 to 4.7.0-beta1. I have done this procedure 3 times. They worked all 3. Turn off all noncore modules. Be sure that the update version is correct. The Drupal update script says you don't need to choose the update version because it does it automatically. False. By choosing different update versions you get different results. It sounds kooky but it's true. Good luck.
wim