Jump to content

1.6.0.6 is a complete mess, do not recommend upgrade

med458

By med458
in OUT - 1.6.0.11 [7 Jan 2015]

 Share

Recommended Posts

med458 Newbie

med458

Posted
Posted

If your site is working fine now, I would not advise upgrading it, 1.6.0.6 is a complete mess!

Even when I rollback there are some errors that persist that I cannot figure out how to fix.

I hope this post saves someone from lots of headaches that I am facing.

  • Like 1
Link to comment
Share on other sites
duster Newbie

duster

Posted
Posted

I agree. It's a complete disaster!

 

My site's countries, states, zones, carriers, default currency, taxes were all set for Australia only and now everything to do with Localization has reverted back US defaults and it all has to be set up again.

 

 

Link to comment
Share on other sites
med458 Newbie

med458

Posted
  • Author
Posted

wow you had it much worse than me, i just had big layout problems, like the homeslider was in 2 places and all the images disappeared and everything was way too big for the screen.

i reverted back and i fixed everything except one thing, the contact info in the footer will not update.  it stays empty.  my payment processor requires me to have my contact info so i might be in trouble if they see that.  so i need to get that back up asap.  any ideas??

Link to comment
Share on other sites
selectshop.at Newbie

selectshop.at

Posted
Posted

If your site is working fine now, I would not advise upgrading it, 1.6.0.6 is a complete mess!

Even when I rollback there are some errors that persist that I cannot figure out how to fix.

I hope this post saves someone from lots of headaches that I am facing.

I agree to that. For the time being I wil not upgrade my projects. For new shops, it is OK, but not for upgraded shops. Some of the reports are closed, because they cannot be reproduced, but they are still available on upgraded/cloned shop.

 

One ex for upgrade problem: http://forge.prestashop.com/browse/PSCSX-1050. Without possibility to re-work orders I will not upgrade Prestashop. I also tried by adding new orders to check it there is a problem only for old orders. That's not. Cannot add products to order cause there are no buttons available for that and also cannot delete products from order.

Link to comment
Share on other sites
selectshop.at Newbie

selectshop.at

Posted
Posted

thats why its recommended to use overridding and duplicate default theme and work with the copy

i have updated also and i dont have such problems like you

Override what ? According to developers Prestashop does not support overrides anymore with PS 1.6. ? On next upgrade overrides will not work again ? Not a fix possibility for me.

Link to comment
Share on other sites
dioniz Newbie

dioniz

Posted
Posted

Override what ? According to developers Prestashop does not support overrides anymore with PS 1.6. ? On next upgrade overrides will not work again ? Not a fix possibility for me.

 

Where can i read about this? If theme overriding is not supported anymore Prestashop is unusable

  • Like 2
Link to comment
Share on other sites
med458 Newbie

med458

Posted
  • Author
Posted

hello all my friends, may i ask one question?

does anyone know what file calls the footer cms contact info?  

and what file contains the footer cms contact info, if it is not the same file?

everything will be fixed for me if I can locate these 2 files.  thank you.

Link to comment
Share on other sites
sooroos Newbie

sooroos

Posted
Posted (edited)

Override what ? According to developers Prestashop does not support overrides anymore with PS 1.6. ? On next upgrade overrides will not work again ? Not a fix possibility for me.

 

You "offer professional paid support for Prestashop" but you dont override prestashop files when developing a new project?

Edited by sooroos (see edit history)
  • Like 2
Link to comment
Share on other sites
selectshop.at Newbie

selectshop.at

Posted
Posted (edited)

Support is one and coding is a complete different thing.

As I told you before: Prestashop developer told me that overrides are deprecated and not supported anymore on PS 1.6. (This was as an official developer statement on a thread I was participating about PS 1.6.). Overrides were created especially for PS 1.4. and PS 1.5. to make both versions closer and animate users to upgrade. Unfortunately in the meantime the link was changed: http://forge.prestashop.com/browse/PSCSX-843?focusedCommentId=83098&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-83098

Before it was: override are deprecated.

 

Well, all these years working with Prestashop I learned one important thing. Don't touch the core, also not with overrides. You are programming future problems with them.

Edited by selectshop.at (see edit history)
Link to comment
Share on other sites
jprr773 Newbie

jprr773

Posted
Posted

I don't recommend AT ALL upgrading from 1.6.0.5 to 1.6.0.6 using 1-Click Upgrade module.

 

Apparently the upgrade process went well, only showed some messages on the upgradeDb:

 

[OK] SQL 1.6.0.6 SET NAMES 'utf8'
[OK] SQL 1.6.0.6 ALTER TABLE `ps_order_invoice_tax` ADD INDEX (`id_tax`)
[OK] SQL 1.6.0.6 INSERT IGNORE INTO `ps_meta` (`id_meta`, `page`, `configurable`) VALUES (NULL, 'products-comparison', '1'), (NULL, 'cms', '0'), (NULL, 'category', '0'), (NULL, 'product', '0'), (NULL, 'module-bankwire-payment', '0'), (NULL, 'module-bankwire-validation', '0'), (NULL, 'module-cheque-validation', '0'), (NULL, 'module-cheque-payment', '0')
[OK] SQL 1.6.0.6 INSERT IGNORE INTO `ps_theme_meta` ( `id_theme` , `id_meta` , `left_column` , `right_column` ) SELECT `ps_theme`.`id_theme` , `ps_meta`.`id_meta` , `default_left_column` , `default_right_column` FROM `ps_theme` , `ps_meta`
[WARNING] SQL 1.6.0.6 1060 in ALTER TABLE `ps_tab` ADD `hide_host_mode` tinyint(1) NOT NULL DEFAULT '0' AFTER `active`: Duplicate column name 'hide_host_mode'
[OK] SQL 1.6.0.6 UPDATE `ps_employee` SET `bo_theme` = 'default'
[OK] SQL 1.6.0.6 DELETE FROM `ps_image_type` WHERE `name` = 'cart_default'
[OK] SQL 1.6.0.6 INSERT INTO `ps_image_type` (`id_image_type`,`name`,`width`,`height`,`products`,`categories`,`manufacturers`,`suppliers`,`scenes`,`stores`) VALUES (NULL, 'cart_default', '80', '80', '1', '0', '0', '0', '0', '0')
[WARNING] SQL 1.6.0.6 1146 in ALTER TABLE `ps_cart_rule_combination` ADD INDEX `id_cart_rule_1` (`id_cart_rule_1`): Table 'lojadada.ps_cart_rule_combination' doesn't exist
[WARNING] SQL 1.6.0.6 1146 in ALTER TABLE `ps_cart_rule_combination` ADD INDEX `id_cart_rule_2` (`id_cart_rule_2`): Table 'lojadada.ps_cart_rule_combination' doesn't exist
[OK] PHP 1.6.0.6 : /* PHP:p1606module_exceptions(); */

 

Now I just can't access the backoffice, and when I try to open it I got this screen:

 

[PrestaShopDatabaseException]

Table 'myshop.ps_access' doesn't exist
 

				SELECT *				FROM `ps_access` a				LEFT JOIN `ps_tab` t ON t.id_tab = a.id_tab				WHERE `id_profile` = 0

at line 623 in file classes/db/Db.php

617. 			WebserviceRequest::getInstance()->setError(500, '[SQL Error] '.$this->getMsgError().'. From '.(isset($dbg[3]['class']) ? $dbg[3]['class'] : '').'->'.$dbg[3]['function'].'() Query was : '.$sql, 97);618. 		}619. 		else if (_PS_DEBUG_SQL_ && $errno && !defined('PS_INSTALLATION_IN_PROGRESS'))620. 		{621. 			if ($sql)622. 				throw new PrestaShopDatabaseException($this->getMsgError().'<br /><br /><pre>'.$sql.'</pre>');623. 			throw new PrestaShopDatabaseException($this->getMsgError());624. 		}625. 	}626. 627. 	/**

 

 

I got to MySQL workbench, and I was stunned to see all t the tables from ps_a* to ps_cms_category were gone.

I'm only glad to have a couple of cold beers in my fridge and a backup.....

Link to comment
Share on other sites
Yzzy Newbie

Yzzy

Posted
Posted

Nightmare!! I now have a clients existing store that will not allow any edits to the categories, wont show slider images and that's just the beginning of her issues. I'm left to try and fix it all and tear my hair out waiting for this support forum to come up with solutions.

 

I wish we hadn't upgraded!

Link to comment
Share on other sites
benjamin utterback Newbie

benjamin utterback

Posted
Posted

Hello,

 

 Thank you all for your feedback. It would be best to have forge reports made of these issues so our development team can look at them. Making a forge report and posting it on the forum also allows other community members to vote for the issue.

 

If there are forge reports made, please link us to them. We need to find ways to reproduce these errors if not, then we need to find out what environments and configurations caused these errors.

 

It seems that localization was an area that multiple people had errors on correct? Thanks again everybody, we appreciate your help.

 

ps: Always, always do a manual backup of your PrestaShop database and files before an upgrade. Always, Always test an upgrade on a test environment. Here is a link to a blog post that shows you how to do both. http://www.prestashop.com/blog/en/set-up-a-test-server-for-your-online-store/

Link to comment
Share on other sites
jprr773 Newbie

jprr773

Posted
Posted

Hello,

 

 Thank you all for your feedback. It would be best to have forge reports made of these issues so our development team can look at them. Making a forge report and posting it on the forum also allows other community members to vote for the issue.

 

If there are forge reports made, please link us to them. We need to find ways to reproduce these errors if not, then we need to find out what environments and configurations caused these errors.

 

It seems that localization was an area that multiple people had errors on correct? Thanks again everybody, we appreciate your help.

 

ps: Always, always do a manual backup of your PrestaShop database and files before an upgrade. Always, Always test an upgrade on a test environment. Here is a link to a blog post that shows you how to do both. http://www.prestashop.com/blog/en/set-up-a-test-server-for-your-online-store/

+1000, tks Benjamin

  • Like 1
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...