Is there any chance that upgrade from 1.1 to 1.3 will work??

[ct1976]

tried to upgrade to 1.2.5 before ad had sql errors (as did many others by the looks of it).

i desperately want to upgrade but dare not risk it if get the same issues as with 1.2.5!

[pb4sc]

Hi,
I just did it, no problem. As far as the SQL errors, here is what happened to me. I may be wrong, but it seems that when you do an upgrade, the there are some changes made by prestashop to the database. I practiced on a local host. On my first try, I did not have any SQL errors, but my images were missing. (Due to my FTP client not grabbing all the images). I tried again, but did not reimport my original SQL backup, and left the upgraded tables in the database. The second time, I had a bunch of SQL errors. I think it was due to the upgraded tables. The third time was the charm. I deleted the database tables from the upgrade. Re imported my original database, then did the upgrade. It worked.
Hope this sheds some light on your SQL errors.
pb4sc

[rellik]

"I deleted the database tables from the upgrade. Re imported my original database, then did the upgrade."

I'm confused. You indicate by deleting the database tables that you have done the upgrade and then you say you do the upgrade.

Step by step would be handy as I am not sure how to delete or import the database tables.

[ct1976]

thanks for the reply, i am still a little confused and dont want to attempt the upgrade until i know it definately works

[pb4sc]

Hi,
I suggest you do a local host install with WAMP to practice this. It has phpmyadmin built into it. Messing with the database can lead to trouble. This whole idea is dependent on if you have a backup of your old database.

1. Open phpmyadmin
2. Find the database name for your install
3. Open it, and delete all the tables.
4. Go to the import tab. Import you backup of your original database.

Then try the install. I believe that v1.3 changes the database in the install. My SGL errors was from trying to do the prestashop update, on a database that was already updated. When I installed the old database, it worked for me. I hope it works for you.


pb4sc

[rellik]

I'm sorry but an upgrade should a straight forward process. Why should we have to practice to get it right. 5 attempts to replace something that has been working satisfactory.

[rocky]

I think the SQL errors are usually caused by having duplicate entries in tables. When PrestaShop tries to modify tables so that they must have unique entries to improve the performance of PrestaShop, it fails with "duplicate row" error messages. You should check your tables for duplicate rows and remove them before attempting to upgrade.

[rellik]

Were not duplicate row errors. If I try a 6th time I will post the errors but does not explain missing pictures and pages not found. Once again there has to be a simpler upgrade path.

[rellik]

Just a thought have been running with a modified theme but reverted to original theme prior to upgrade. Is it possible that products added using the modified theme could be causing the errors?

[rocky]

I don't think so. Perhaps the format of the attributes or customisation could be changed in a theme, but otherwise the theme shouldn't affect adding products in the Back Office.

[rellik]

6th time still unlucky
1: Backed up site
2: uploaded 1.3 files
3: copied only img/p
4:copied settings.inc.php
All this was done with the shop using default theme and offline.
Ran install and 33 SQL errors as below.

SET NAMES 'utf8'

/* ##################################### */ /* STRUCTURE */ /* ##################################### */ ALTER TABLE `ps_product` CHANGE `reduction_from` `reduction_from` DATE NOT NULL DEFAULT '1970-01-01', CHANGE `reduction_to` `reduction_to` DATE NOT NULL DEFAULT '1970-01-01'

ALTER TABLE `ps_order_detail` CHANGE `tax_rate` `tax_rate` DECIMAL(10, 3) NOT NULL DEFAULT '0.000'

ALTER TABLE `ps_group` ADD `price_display_method` TINYINT NOT NULL DEFAULT 0 AFTER `reduction`

(1060) Duplicate column name 'price_display_method'
CREATE TABLE `ps_carrier_group` ( `id_carrier` int(10) unsigned NOT NULL, `id_group` int(10) unsigned NOT NULL, UNIQUE KEY `id_carrier` (`id_carrier`,`id_group`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8

(1050) Table 'ps_carrier_group' already exists
ALTER TABLE `ps_country` ADD `need_identification_number` TINYINT( 1 ) NOT NULL

(1060) Duplicate column name 'need_identification_number'
ALTER TABLE `ps_customer` ADD `dni` VARCHAR( 16 ) NULL AFTER `firstname`

(1060) Duplicate column name 'dni'
ALTER TABLE `ps_image` ADD INDEX `product_position` (`id_product`, `position`)

(1061) Duplicate key name 'product_position'
ALTER TABLE `ps_hook_module` ADD INDEX `id_module` (`id_module`)

(1061) Duplicate key name 'id_module'
ALTER TABLE `ps_customer` ADD INDEX `id_customer_passwd` (`id_customer`, `passwd`)

(1061) Duplicate key name 'id_customer_passwd'
ALTER TABLE `ps_tag` ADD INDEX `id_lang` (`id_lang`)

(1061) Duplicate key name 'id_lang'
ALTER TABLE `ps_customer_group` ADD INDEX `id_customer` (`id_customer`)

(1061) Duplicate key name 'id_customer'
ALTER TABLE `ps_category_group` ADD INDEX `id_category` (`id_category`)

(1061) Duplicate key name 'id_category'
ALTER TABLE `ps_image` ADD INDEX `id_product_cover` (`id_product`, `cover`)

(1061) Duplicate key name 'id_product_cover'
ALTER TABLE `ps_employee` ADD INDEX `id_employee_passwd` (`id_employee`, `passwd`)

(1061) Duplicate key name 'id_employee_passwd'
ALTER TABLE `ps_product_attribute` ADD INDEX `product_default` (`id_product`, `default_on`)

(1061) Duplicate key name 'product_default'
ALTER TABLE `ps_product_download` ADD INDEX `product_active` (`id_product`, `active`)

(1061) Duplicate key name 'product_active'
ALTER TABLE `ps_tab` ADD INDEX `class_name` (`class_name`)

(1061) Duplicate key name 'class_name'
ALTER TABLE `ps_module_currency` ADD INDEX `id_module` (`id_module`)

(1061) Duplicate key name 'id_module'
ALTER TABLE `ps_product_attribute_combination` ADD INDEX `id_product_attribute` (`id_product_attribute`)

(1061) Duplicate key name 'id_product_attribute'
ALTER TABLE `ps_orders` ADD INDEX `invoice_number` (`invoice_number`)

(1061) Duplicate key name 'invoice_number'
ALTER TABLE `ps_product_tag` ADD INDEX `id_tag` (`id_tag`)

(1061) Duplicate key name 'id_tag'
ALTER TABLE `ps_cms_lang` CHANGE `id_cms` `id_cms` INT(10) UNSIGNED NOT NULL

ALTER TABLE `ps_tax` CHANGE `rate` `rate` DECIMAL(10, 3) NOT NULL

ALTER TABLE `ps_order_detail` ADD `discount_quantity_applied` TINYINT(1) NOT NULL DEFAULT 0 AFTER `ecotax`

(1060) Duplicate column name 'discount_quantity_applied'
ALTER TABLE `ps_orders` ADD `total_products_wt` DECIMAL(10, 2) NOT NULL AFTER `total_products`

(1060) Duplicate column name 'total_products_wt'
/* ##################################### */ /* CONTENTS */ /* ##################################### */ UPDATE `ps_group` SET `price_display_method` = (SELECT `value` FROM `ps_configuration` WHERE `name` = 'PS_PRICE_DISPLAY')

UPDATE `ps_configuration` SET `value` = ROUND(value / (1 + ( SELECT rate FROM ( SELECT t.`rate`, COUNT(*) n FROM `ps_orders` o LEFT JOIN `ps_carrier` c ON (o.`id_carrier` = c.`id_carrier`) LEFT JOIN `ps_tax` t ON (t.`id_tax` = c.`id_tax`) WHERE c.`deleted` = 0 AND c.`shipping_handling` = 1 GROUP BY o.`id_carrier` ORDER BY n DESC LIMIT 1 ) myrate ) / 100), 6) WHERE `name` = 'PS_SHIPPING_HANDLING'

DELETE FROM `ps_configuration` WHERE `name` = 'PS_PRICE_DISPLAY'

DELETE FROM `ps_product_attachment` WHERE `id_product` NOT IN (SELECT `id_product` FROM `ps_product`)

DELETE FROM `ps_discount_quantity` WHERE `id_product` NOT IN (SELECT `id_product` FROM `ps_product`)

DELETE FROM `ps_pack` WHERE `id_product_pack` NOT IN (SELECT `id_product` FROM `ps_product`) OR `id_product_item` NOT IN (SELECT `id_product` FROM `ps_product`)

DELETE FROM `ps_product_sale` WHERE `id_product` NOT IN (SELECT `id_product` FROM `ps_product`)

DELETE FROM `ps_scene_products` WHERE `id_product` NOT IN (SELECT `id_product` FROM `ps_product`)

DELETE FROM `ps_search_index` WHERE `id_product` NOT IN (SELECT `id_product` FROM `ps_product`)

DELETE FROM `ps_search_word` WHERE `id_word` NOT IN (SELECT `id_word` FROM `ps_search_index`)

DELETE FROM `ps_tag` WHERE `id_lang` NOT IN (SELECT `id_lang` FROM `ps_lang`)

DELETE FROM `ps_search_word` WHERE `id_lang` NOT IN (SELECT `id_lang` FROM `ps_lang`)

INSERT INTO `ps_configuration` (`name`, `value`, `date_add`, `date_upd`) VALUES ('PRESTASTORE_LIVE', 1, NOW(), NOW()), ('PS_SHOW_ALL_MODULES', 0, NOW(), NOW()), ('PS_BACKUP_ALL', 0, NOW(), NOW()), ('PS_1_3_UPDATE_DATE', NOW(), NOW(), NOW()), ('PS_PRICE_ROUND_MODE', 2, NOW(), NOW())

(1062) Duplicate entry 'PRESTASTORE_LIVE' for key 2
INSERT INTO `ps_hook` (`name`, `title`, `description`, `position`) VALUES ('createAccountTop', 'Block above the form for create an account', NULL , '1'), ('backOfficeHeader', 'Administration panel header', NULL , '0'), ('backOfficeTop', 'Administration panel top hover the tabs', NULL , '1'), ('backOfficeFooter', 'Administration panel footer', NULL , '1')

[rocky]

It looks like you are trying to upgrade a database that has already been upgraded. That's why you are getting errors when you try to add the new PrestaShop v1.3 columns, because they are already in your database. You should restore a backup of your old PrestaShop database before you attempted to upgrade, which doesn't have the price_display_method column in ps_group, for example.

[rellik]

The database was the current one from my working 1.2.5 shop. Would an updated database still work with 1.2.5?

[rocky]

It might, but there may be unexpected consequences to running a PrestaShop v1.2.5 shop with a PrestaShop v1.3 database. It is better that they match.

[rellik]

The 33 sql errors came up with my 1st attempt at upgrade.
How can I restore a complete backup of my database?

Also am trying to set it up in WAMP but having trouble with details of server name etc for local database when running the install.

[rocky]

The ps_group price_display_method column was added in PrestaShop v1.3. It didn't exist in PrestaShop v1.1. Since there was an error saying the column already existing, then it can't have been the first attempt to upgrade the database. Perhaps you accidentally upgraded your website twice.

Have you been making regular backups of your database? If you haven't, then you can't restore a backup and are stuck with an un-upgradable database. In that case, you'll need to do a clean install or PrestaShop with a different prefix and manually copy over the data.

[rellik]

Have regular backups and currently replacing database with one that is definately prior to upgrade attempt.
Will try number 7 later.
You said that field did not exist in 1.1 was it in 1.2 or new to 1.3?

[rocky]

The price_display_method field was added to ps_group in PrestaShop v1.3.0.1. It didn't exist in previous versions.

[rellik]

7th time grabbed on old database backup (forgot that it would be modified on the server not in prestashop) and tried an upgrade.
Results on 1 SQL error not 33

SET NAMES 'utf8'

/* ##################################### */ /* STRUCTURE */ /* ##################################### */ ALTER TABLE `ps_product` CHANGE `reduction_from` `reduction_from` DATE NOT NULL DEFAULT '1970-01-01', CHANGE `reduction_to` `reduction_to` DATE NOT NULL DEFAULT '1970-01-01'

ALTER TABLE `ps_order_detail` CHANGE `tax_rate` `tax_rate` DECIMAL(10, 3) NOT NULL DEFAULT '0.000'

ALTER TABLE `ps_group` ADD `price_display_method` TINYINT NOT NULL DEFAULT 0 AFTER `reduction`

CREATE TABLE `ps_carrier_group` ( `id_carrier` int(10) unsigned NOT NULL, `id_group` int(10) unsigned NOT NULL, UNIQUE KEY `id_carrier` (`id_carrier`,`id_group`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8

ALTER TABLE `ps_country` ADD `need_identification_number` TINYINT( 1 ) NOT NULL

ALTER TABLE `ps_customer` ADD `dni` VARCHAR( 16 ) NULL AFTER `firstname`

ALTER TABLE `ps_image` ADD INDEX `product_position` (`id_product`, `position`)

ALTER TABLE `ps_hook_module` ADD INDEX `id_module` (`id_module`)

ALTER TABLE `ps_customer` ADD INDEX `id_customer_passwd` (`id_customer`, `passwd`)

ALTER TABLE `ps_tag` ADD INDEX `id_lang` (`id_lang`)

ALTER TABLE `ps_customer_group` ADD INDEX `id_customer` (`id_customer`)

ALTER TABLE `ps_category_group` ADD INDEX `id_category` (`id_category`)

ALTER TABLE `ps_image` ADD INDEX `id_product_cover` (`id_product`, `cover`)

ALTER TABLE `ps_employee` ADD INDEX `id_employee_passwd` (`id_employee`, `passwd`)

ALTER TABLE `ps_product_attribute` ADD INDEX `product_default` (`id_product`, `default_on`)

ALTER TABLE `ps_product_download` ADD INDEX `product_active` (`id_product`, `active`)

ALTER TABLE `ps_tab` ADD INDEX `class_name` (`class_name`)

ALTER TABLE `ps_module_currency` ADD INDEX `id_module` (`id_module`)

ALTER TABLE `ps_product_attribute_combination` ADD INDEX `id_product_attribute` (`id_product_attribute`)

ALTER TABLE `ps_orders` ADD INDEX `invoice_number` (`invoice_number`)

ALTER TABLE `ps_product_tag` ADD INDEX `id_tag` (`id_tag`)

ALTER TABLE `ps_cms_lang` CHANGE `id_cms` `id_cms` INT(10) UNSIGNED NOT NULL

ALTER TABLE `ps_tax` CHANGE `rate` `rate` DECIMAL(10, 3) NOT NULL

ALTER TABLE `ps_order_detail` ADD `discount_quantity_applied` TINYINT(1) NOT NULL DEFAULT 0 AFTER `ecotax`

ALTER TABLE `ps_orders` ADD `total_products_wt` DECIMAL(10, 2) NOT NULL AFTER `total_products`

/* ##################################### */ /* CONTENTS */ /* ##################################### */ UPDATE `ps_group` SET `price_display_method` = (SELECT `value` FROM `ps_configuration` WHERE `name` = 'PS_PRICE_DISPLAY')

UPDATE `ps_configuration` SET `value` = ROUND(value / (1 + ( SELECT rate FROM ( SELECT t.`rate`, COUNT(*) n FROM `ps_orders` o LEFT JOIN `ps_carrier` c ON (o.`id_carrier` = c.`id_carrier`) LEFT JOIN `ps_tax` t ON (t.`id_tax` = c.`id_tax`) WHERE c.`deleted` = 0 AND c.`shipping_handling` = 1 GROUP BY o.`id_carrier` ORDER BY n DESC LIMIT 1 ) myrate ) / 100), 6) WHERE `name` = 'PS_SHIPPING_HANDLING'

DELETE FROM `ps_configuration` WHERE `name` = 'PS_PRICE_DISPLAY'

DELETE FROM `ps_product_attachment` WHERE `id_product` NOT IN (SELECT `id_product` FROM `ps_product`)

DELETE FROM `ps_discount_quantity` WHERE `id_product` NOT IN (SELECT `id_product` FROM `ps_product`)

DELETE FROM `ps_pack` WHERE `id_product_pack` NOT IN (SELECT `id_product` FROM `ps_product`) OR `id_product_item` NOT IN (SELECT `id_product` FROM `ps_product`)

DELETE FROM `ps_product_sale` WHERE `id_product` NOT IN (SELECT `id_product` FROM `ps_product`)

DELETE FROM `ps_scene_products` WHERE `id_product` NOT IN (SELECT `id_product` FROM `ps_product`)

DELETE FROM `ps_search_index` WHERE `id_product` NOT IN (SELECT `id_product` FROM `ps_product`)

DELETE FROM `ps_search_word` WHERE `id_word` NOT IN (SELECT `id_word` FROM `ps_search_index`)

DELETE FROM `ps_tag` WHERE `id_lang` NOT IN (SELECT `id_lang` FROM `ps_lang`)

DELETE FROM `ps_search_word` WHERE `id_lang` NOT IN (SELECT `id_lang` FROM `ps_lang`)

INSERT INTO `ps_configuration` (`name`, `value`, `date_add`, `date_upd`) VALUES ('PRESTASTORE_LIVE', 1, NOW(), NOW()), ('PS_SHOW_ALL_MODULES', 0, NOW(), NOW()), ('PS_BACKUP_ALL', 0, NOW(), NOW()), ('PS_1_3_UPDATE_DATE', NOW(), NOW(), NOW()), ('PS_PRICE_ROUND_MODE', 2, NOW(), NOW())

INSERT INTO `ps_hook` (`name`, `title`, `description`, `position`) VALUES ('createAccountTop', 'Block above the form for create an account', NULL , '1'), ('backOfficeHeader', 'Administration panel header', NULL , '0'), ('backOfficeTop', 'Administration panel top hover the tabs', NULL , '1'), ('backOfficeFooter', 'Administration panel footer', NULL , '1')

INSERT INTO `ps_carrier_group` (id_carrier, id_group) (SELECT id_carrier, id_group FROM ps_carrier c, ps_group g WHERE c.active = 1)

/* PHP */ /* PHP:convert_product_price(); */

SET NAMES 'utf8'

ALTER TABLE `ps_order_detail` ADD INDEX `id_order_id_order_detail` (`id_order`, `id_order_detail`)

ALTER TABLE `ps_category_group` ADD INDEX `id_group` (`id_group`)

ALTER TABLE `ps_product` ADD INDEX `date_add` (`date_add`)

SET NAMES 'utf8'

/* ##################################### */ /* STRUCTURE */ /* ##################################### */ ALTER TABLE `ps_product_attachment` CHANGE `id_product` `id_product` INT(10) UNSIGNED NOT NULL, CHANGE `id_attachment` `id_attachment` INT(10) UNSIGNED NOT NULL

ALTER TABLE `ps_attribute_impact` CHANGE `id_product` `id_product` INT(11) UNSIGNED NOT NULL, CHANGE `id_attribute` `id_attribute` INT(11) UNSIGNED NOT NULL

ALTER TABLE `ps_block_cms` CHANGE `id_block` `id_block` INT(10) UNSIGNED NOT NULL, CHANGE `id_cms` `id_cms` INT(10) UNSIGNED NOT NULL

ALTER TABLE `ps_customization_field` CHANGE `id_produc

[rocky]

I can't see any errors. Can you paste the entire contents of the SQL log in a text file and attach to a post?

[rellik]

The log was in my last message

[rocky]

Yes, but there are no errors in that log and it appears to be cut off at the end. You said there was 1 SQL error. I need to see individual SQL query and error message to help.

[rellik]

sorry was cut off at the end due to too many characters to post. Do not have a copy and not going to try again. Will stick to 1.2.5 until there is an easier upgrade path.

EDIT
error

ALTER TABLE `ps_search_engine` ADD UNIQUE (`server`,`getvar`)

(1062) Duplicate entry 'bing.com-q' for key 2
REPLACE INTO `ps_search_engine` (`server`,`getvar`) VALUES ('google','q'),('aol','q'),('yandex','text'),('ask.com','q'),('nhl.com','q'),('yahoo','p'),('baidu','wd'), ('lycos','query'),('exalead','q'),('search.live','q'),('voila','rdata'),('altavista','q'),('bing','q'),('daum','q'), ('eniro','search_word'),('naver','query'),('msn','q'),('netscape','query'),('cnn','query'),('about','terms'),('mamma','query'), ('alltheweb','q'),('virgilio','qs'),('alice','qs'),('najdi','q'),('mama','query'),('seznam','q'),('onet','qt'),('szukacz','q'), ('yam','k'),('pchome','q'),('kvasir','q'),('sesam','q'),('ozu','q'),('terra','query'),('mynet','q'),('ekolay','q'),('rambler','words')

[rellik]

SOLVED
Finally done on the 9th attempt. There were 2 entries for Bing in the search engines but the silly part is I have never added them. Must have come from previous updates.
Perhaps there may be a way for checking a database prior to doing an upgrade.
Thank you for all you help.

EDIT
After update everything came up page not found had to regenerate my .htaccess file

[rocky]

Yes, good idea. I'll post on the bug tracker, but I'm not sure whether the PrestaShop team would be interested. Perhaps a module could be developed to check for database issues like duplicate entries that would prevent a successful upgrade, and maybe automatically delete duplicate entries.

[rellik]

I see your comments on the bug tracker but I now have another problem.
In product description the old products only show as HTML and new products as Plain Text but the major problem is there is no longer a toolbar at the top.

Hope you can help again as I appreciate your effort.
I have posted this elswhere without any answers.

[rocky]

Did you overwrite the /js/ directory with the one from PrestaShop v1.3 and upload it? I suggest that you check for Javascript errors. Look in the bottom-left corner of IE for "Done, with errors". If it does say that, click the icon and post the errors here.

[rellik]

Have uploaded the updated js and did it again in case I missed a file.
When you say check for eroors in IE I use firefox and what function should I do to get errors.

[rocky]

I might be wrong, but I don't think Firefox displays Javascript errors. I think you need to install Firebug to view Javascript errors.

[rellik]

Have frebug installed but did not show error but received the following error with IE.

Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2)
Timestamp: Sat, 5 Jun 2010 01:56:09 UTC


Message: Object expected
Line: 145
Char: 5
Code: 0
URI: http://insideco.com.au/rellik/index.php?tab=AdminCatalog&id_category=14&id_product=41&updateproduct&token;=a9c9f3966d11a78f47a44e3224c1acc9

[rocky]

What's on line 145 when you right-click on the page and choose "View Page Source"?

[rellik]

Looks like there is a language problem should the "0" be "1"
If so what file needs to be edited.


displayFlags is not defined

Line 145


displayFlags(languages, id_language, 0);

[rocky]

In PrestaShop v1.3, a feature was added so that each employee can set their own default form language. This value is stored in PrestaShop's cookie. It appears the cookie wasn't updated when you upgraded PrestaShop. Try clearing your cookies. That should force PrestaShop to generate a new cookie with a correct default form language.

[rellik]

Cleared cookies Changed details re employee and that line now says language as 1 not o but still same error

Checking language in tools I have the iso code of en but the Check if a language pack is available for this iso code... just hangs or says no language for this code.

[rocky]

That is a known issue that I've reported on the bug tracker. It might be easier if I could see the problem myself. Can you please create an account for me so I can log in to your Back Office and PM me the details?

[rellik]

Thanks to those that have tried to help me but spent over a week trying to get the upgrade right. I have previously done about 4 upgrades to get to 1.2.5 but going to 1.3.1 has caused me headaches. I have reverted back to 1.2.5 but have a converted database that seems to work OK. I did a backup prior to conversion but no longer have it and my only non-converted backup is 43 days old too many changes would have to be made. Hopefully the next release may work better or some one develops a better upgrade path.

[ct1976]

I took the plung and upgraded...all seemed fine to my relief then hit a big problem;

http://www.ukbedsonline.com

You will see that starts to load the cannot display the right hand blocks and errors. however if you click one of the left hand links goes through until page loads, cants see right hand blocks, errors.

I have tried re-writing the .htaccess and also tried 1.1 compatability on and off. Tried re-uloading the old theme and then put the new one back.

I upgraded from 1.1 to 1.3.0

Can anyone help pls!!

[rocky]

It appears there is a PHP error in one of your modules. Perhaps it isn't compatible with PrestaShop v1.3.1. Check your PHP errorlog or edit config/config.inc.php and temporarily change 'display_errors' from 'off' to 'on' so that you get an error message, then post it here.

[rellik]

Bit the bullet and decided to start from scratch rather than upgrade.
Got everything working all looked normal until I changed a few things.
Set currency only to dollar & deleted others, Edited dollar to AU, In country restrictions set only to Australia, added GST and deleted the others in taxes.
Then started to set up shipping. Previously there was a price range corresponding to each weight range but could not see where I could set a price range relative to weight only a min & max price range.
Deleted default products and started to add new products and back to my previous problem with no toolbar in descriptions.
Back to my backup of 1.2.5

[ct1976]

thanks Rocky

the error is;

Fatal error: Smarty error: [in /home/ukbedso1/public_html/modules/blockcart/blockcart.tpl line 46]: syntax error: unrecognized tag 't' (Smarty_Compiler.class.php, line 590) in /home/ukbedso1/public_html/tools/smarty/Smarty.class.php on line 1095

[ct1976]

deleted all add-on modules ive aquired....no change im afraid

i will try reinstalling the cart module now

[ct1976]

uninstalled cart, refreshed Home page and all footers and other blocks to the right reappeared. reinstalled cart and vanished again.

any ideas?!

[ct1976]

SOLVED !

overwritten old cart from previous backup and works!!!!

[searcher]

Do not repeat the wrong line. If I try, I will release the sixth error, but did not explain the missing images and pages not found. Again, there should be a simple upgrade.

[MikeMc68]

Why is Prestashop so horrendous at upgrades?

Are the developers not able to simply have an UPGRADE button that does it automatically, the same as many other PHP based products that have been out for years like Wordpress? I am appalled at how complicated it is. Unless you have experience and knowledge in these things you are screwed.

[rocky]

If no-one customised their PrestaShop websites, I would agree with you. I could create a module with a one-click upgrade button that downloads PrestaShop and overwrites all the PrestaShop files, then executes the upgrade SQL. I could even check for potential issues like duplicate rows and permissions before allowing the button to be clicked, but I wouldn't know which files have been modified. Many modules require you to overwrite core PrestaShop files. To automatically detect modified files and merge them with the changes in PrestaShop v1.3 would be quite difficult. Do you have any suggestions for how this one-click upgrade would resolve these conflicts?

[starxox]

Don't know too much about the ins and out, but my host (Vidahost) has installed the softaculous script for prestashop that made it very easy for me to update, altho it was still necessary to go into the prestashop installer but really was easy. I still had to copy over any modules that were changed, but really was easy enough.

ps vidahost are excellent and very cheap (almost no downtime and excellent support). Yes I do get a bit of money if you sign up with my link, but really the only reason I signed up to their affiliate program is how amazing they are and compatible with prestashop, and will help you solve any problems

Vida host are a great company!