Anybody did this? Would you mind sharing your experience to prepare me for the worst... I have a life site with hundreds of products and unfinished transactions. I have no idea how much has changed meanwhile. If you have any advice, please share it ! Thank you in advance.
| Comment | File | Size | Author |
|---|---|---|---|
| #12 | store_update_21.patch | 2.72 KB | neclimdul |
| #7 | update21_alternative.store.install.patch.txt | 7.28 KB | ñull |
Comments
Comment #1
ñull commentedI just tried to upgrade from 4.6 to 4.7 and update.php fails on me with a large list of warnings. Is there a need in the community that I document all the manual changes that will be necessary to upgrade to ecommerce 4.7 or am I the only one?
Comment #2
simeI would certainly like to read, and to stick this is the handbook. My only experience 4.6-4.7 was a rough upgrade: it was an early Drupal episode for me and the site had lots of hacks, so it wasn't really a documentation worthy experience.
Comment #3
ñull commentedOK I will keep track of the changes and try to produce the necessary SQL and submit it to the handbook.
Comment #4
gordon commentedIt depends on which version of E-Commerce 4.6 that you are upgrading from.
Check in the updates.inc file that exists in the 4.6 version and see how many updates there are. If there are The lastest version has 10 updates, when you are running the 4.7 upgrade start the store updates at 11.
Comment #5
ñull commentedDrupal 4.6.5 with ecommerce 4.6 (early version patched to make it work) and the following ec modules active:
address, cart, cod, generic, payment, paypal, product, shipping, store, and tangible.
* Made a backup of all the drupal directory and the MySQL database.
* Deleted everything, and installed latest version of Drupal 4.7.x core files and the contributed modules that I had active, among them ecommerce of course.
* Restored from backup the themes, sites and files directory and other CSS files I had changed (drupal.css, nice_menu.css etc.)
* I ran update.php accepting defaults.
* After that I opened MySQL and saw the following differences with a fresh install of Drupal 4.7 with ecommerce:
I might not need it, but did it anyhow:
CREATE TABLE `ec_credit_card` (
`txnid` int(10) unsigned NOT NULL default '0',
`cc_amount` decimal(10,2) NOT NULL default '0.00',
`cc_ordernum` varchar(32) NOT NULL default '',
`cc_refnum` varchar(32) NOT NULL default '',
`cc_reason` varchar(128) NOT NULL default '',
PRIMARY KEY (`txnid`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;
ALTER TABLE `ec_product` CHANGE `price_cycle` `price_cycle` INT( 11 ) NOT NULL DEFAULT '0'
ALTER TABLE `ec_product_tangible` ADD PRIMARY KEY ( `vid` )
ALTER TABLE ec_transaction_product DROP data
ALTER TABLE ec_transaction_product CHANGE product_data data TEXT DEFAULT NULL
Then without changing anything else I looked at the site and most of it looked the same, but:
- when i go to the existing transactions, and look at the addresses of a transaction, they are all empty
- when I look at an invoice of a transaction, the addresses are missing.
- when add something to cart and checkout no payment choice is given (COD should have been offered, Paypal is automatically chosen, nothing else)
Any suggestions before I start debugging this on monday?
Comment #6
ñull commentedI already discover the problem with the addresses. In the update process only a number of addresses were transferred, not all. I don't know why yet.
Comment #7
ñull commentedTo fix the problems with addresses, I decided to do it all over again and switch off upgrade 21, that failed to move all transaction addresses correctly. I manually created and inserted the the new transaction addresses using two SQL queries; much simpler then the used script in update 21. See the attached the patch to change it.
Comment #8
gordon commentedbump
Comment #9
schultzconsult commented+1 from me.
It works very well :-)
Comment #10
gordon commentedPatch applied to both DRUPAL-4-7--3 and HEAD
Comment #11
gordon commentedI have reversed this as this fix is not supported by all versions of MySQL which are supported by Drupal 4.7 and 5
Comment #12
neclimdulOk, this update should work with older versions of MySQL that don't support nested queries. Sorry for the delayed patch. Anyone that has their 4.6 backups and could test this it would be greatly appreciated.
Patch against 4.7.x-3.x-dev
-
James
Comment #13
brmassa commented