Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Matt Taylor 873 posts 2086 karma points
    Feb 01, 2015 @ 17:34
    Matt Taylor
    0

    Differences in v3 from v2

    Obviously the main difference between v2 and v3 is the new marketting functionality.

    There are some other things that are different though which I cannot find documented.

    1. Payment inconsistency email
    2. Firstname/Lastname/Email properties don't need specifying any more?
    3. Lots of differences on the Store/Product tab, less properties need specifying.

    Regards, Matt

     

  • Dennis Aaen 4500 posts 18255 karma points admin hq c-trib
    Feb 01, 2015 @ 19:28
    Dennis Aaen
    0

    Hi Matt,

    Try to see the revision history of the different versions of Tea Commerce http://documentation.teacommerce.net/revision-history

    /Dennis

  • Matt Taylor 873 posts 2086 karma points
    Feb 02, 2015 @ 12:53
    Matt Taylor
    0

    Thanks Dennis, I had looked there but it doesn't explain the changes.

    Regards, Matt

  • Bjarne Fyrstenborg 1284 posts 4038 karma points MVP 8x c-trib
    Feb 02, 2015 @ 13:15
    Bjarne Fyrstenborg
    0

    Hi Matt

     

    You can still use v3 starterkit that was developed for Tea Commerce v2. But you need to change the code to handle the new price object, which support the marketing functionality.

     

    I have listed here which changes I have done in a webshop: http://dev.bjarnefyrstenborg.dk/tc-upgrade/

    Furthermore here is some examples with additional code so the customer is able to add discount codes and gift cards: http://dev.bjarnefyrstenborg.dk/tc-upgrade/examples.html

     

    /Bjarne

     

  • Anders Burla 2560 posts 8256 karma points
    Feb 02, 2015 @ 14:02
    Anders Burla
    0

    Hi Matt

    The main difference is the marketing features. We have also tried and simply some of all the settings. So now the "sku" and "product name" name properties is hardcoded to be "sku" and "productName" and the vat group should be "vatGroup". Its to make the admin a bit more simple.

    If you dont configure the sku and product name the node id and node name will be used as fallback.

    Kind regards
    Anders

  • Matt Taylor 873 posts 2086 karma points
    Feb 02, 2015 @ 15:00
    Matt Taylor
    0

    Thanks for the info there Bjarne.

    Ah, these changes are good to know as they would have affected me.

    I was going to start using 'title' for my produt name just to be consistent with the rest of my document types in my code behind.
    So the vat group definitely needs to be called 'vatGroup'?
    I think after I installed the package, it created one called defaultVATGroup or something but I renamed it. I'm going to have to name it back.

    Regards, Matt

Please Sign in or register to post replies

Write your reply to:

Draft