Yesterday we did the upgrade from 3.4.7 to 3.5. After copying over all changes made to scripts and language files, we did a system upgrade and all seems to work fine.
 
What I noticed:
 
- Changelog file still refers to changes from 3.3 to 3.4 (!)
- Some php files refer to version 3.4.7 and some to 3.5. It seems not all files have been updated to 3.5. From a versioning point of view this is a no-no, to find what files changed it is very good .
- New payment processors added: yourpay_check, paypal_payflow_pro_express, paypal_payflow_pro_direct, ogone_basic, linkpoint_check, ideal_lite_process, hsbc_cpi_functions, hsbc_cpi_direct, hsbc_cpi_check, hsbc_cpi, gate2shop_functions, gate2shop_check. however as usual the upgrade script does not add these to the system and must be added manually from the SQL script in /db/.
- Major changes to language files - many hardcoded strings in php files where moved to language files.
- No changes in template files (afaik).
- Worldpay script still broken (see post from Chris for fix).
 
The quantity features are nice as well as the ability to place the product quantity selectors where you want. 3.5 is an evolution to 3.4.7 and provides some minor improvements here and there.
 
Hope this helps.
 
Cheers!
 
DickS

Hi DickS,
Where can I find the feature for placing quantity selectors where we want please ?
I can't seem to find that one
 
I didn't find any changes to templates either
I saw a couple of new languages but didn't take note of what they were

There are changes to block_product_details.html & block_product_list.html to account for the price matrix.
 
I think he means you can choose to display one type of control on the list page and another type on the details page (that's all)

@on2dvd: that is correct re. display location.
 
Template upgrades are a pain as we customised the product details and list template. Will take a look at the changes made.

I have mentioned this before and it is worth doing so again I think; this is a method used by another eCommerce softwrae that I have and it makes upgrading a breeze. Viart may not want to copy it but they may want to consider a solution that is as easier for us.
 
.........................
 
There is a default theme templates folder with it's own css.
I develop my own theme folder and I copy to it ONLY the templates I want to modify and my own css and language file.
 
The program first looks for templates in the theme folder (specified by admin)- if a template is missing it goes to the default folder for it.
 
Now, for upgrade, overwrite everything - your own theme folder is unaffected and keeps it's mods. If a template has been re-written it can be copied to the new theme folder and modified . . . then all can be uploaded. Easy.

Dear all,
 
Actually, from version 3.4 we have added a new similar structure for customized templates to make the upgrade easier.
 
We recommend you to create a separate folder for the templates you have made changes to and put the modified templates there. Then select this folder as the Templates Directory * for the active layout you are using. When doing the upgrade the system will consider this directory as default and will take your custom templates as active. If it doesn't find an appropriate template it will refer to the default folder with standard templates and your site will work smoothly and without any errors.
 
Regarding Worldpay script it should work correctly in version 3.5. In case you found any errors or inconsistencies, we'll greatly appreciate if you send us details via our support center https://www.viart.com/support.php
 
With kind regards,
ViArt Support Team

Thats a very good idea. Many thanks off to try it..

Thanks on2dvd, thanks DickS, thanks Anjula

That's excellent Anjula.
After my upgrade to 3.5 I will create this set up.
 
Thank you.
 
Chris

One thought occurs to me Anjula, if we create a modified template file in our new directory — and you later make a significant change to the default copy that means we should update our own special copy — how will we know? Will you announce this?

Viart lacks basic documentation skills, unfortunately. That would make this solution more reliable for companies. As it stands every release is a "found out by coincidence" and "lets install to find out what is new".
 
What I also really do not like is the fact that the upgrade script does not add new payment processors. 3.5 has some new ones but you need to extract them from the SQL script manually and add them via SQL. Not ideal at all.
 
DickS

Christopher, I always use Meld (on Linux) to check my modified template file against the new default one. This can be done at directory/folder level. This new proceedure means less checking WinMerge might work for those on another OS.
 
Its also useful for doing merges of say the messages files (Zip to postcode, Shipping to delivery etc..)