Announcement

Collapse
No announcement yet.

By weight shipping. Duplicates calculating inconsistently

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    By weight shipping. Duplicates calculating inconsistently

    I'll try to explain this as best I can.

    Problem apparent in 8.5.3 (was in 8.5.1 too, it's always been like this since upgrading from V7) and also 9.0.2

    Example site (test domain)

    Original Item SP1 Undertray ORIGINAL

    Added to cart, UK (England) Shipping £8.47, which is correct

    DUPLICATE item SP1 Undertray DUPE

    Added to cart (from empty cart), UK (England) Shipping £2.51, which is incorrect.

    After returning to store and clicking onto 'View cart' the calculation is corrected to £8.47.

    This happens with EVERY duplicate item in the store

    For some reason, it is initially calculating the shipping using the DEFAULT shipping weight, not the product weight.

    I know this because I changed the default weight to this £8.47 price band and the duplicate shipping on these items was fixed....only problem was, it then calculated smaller DUPLICATE items that should be £2.51 shipping, at £8.47 until the cart was viewed again!

    I'm not sure which is worse!

    I've tested it and it is definitely happening in both 8.5.3 AND V9 but I've no idea why or how to fix it.

    We rely heavily on duplicates in the store and this is really a bit of a problem, tbh (we've had complaints )

    Has anyone else had a similar problem?
    Tracey

    #2
    Hi Tracey,

    It looks like it's something to do with the 'Request Location Information Early' feature. If I upload the site without that switched on then it works correctly on the duplicate. I'll report it to the development team.
    ********************
    Tracey
    SellerDeck

    Comment


      #3
      ah..interesting. Thanks, Tracey.

      I had wondered if it was just this site that was 'broken' and it was perhaps a database issue.
      It's a wonder no one has mentioned it before now!
      I can't switch off the 'request location information early' function, mind you, because it's important to us that customers get their shipping costs immediately.

      Hopefully there'll be some other fix for it (especially as it happens in the latest versions of both V8 and V9)
      Tracey

      Comment


        #4
        I'm just trying to find out if this is controlled by perl or if it is in the C++. Hopefully perl so I can give you a fix.
        ********************
        Tracey
        SellerDeck

        Comment


          #5
          Hi Tracey,

          Finally got a workaround for this:

          - browse to your site folder and go into the 'ShipControl' folder
          - open 'ShippingTemplate.pl' in a text editor such as notepad
          - search for 'sub GetWeight' (without the apostrophes)
          - just below this you will see the line...

          Code:
          my $dUnitWeight=$::s_Ship_OpaqueDataTables{
                             $::s_Ship_sShipProducts[$nIndex]};
          - replace the above line with the following 3 lines...

          Code:
          my $sOrigProdRef = $::s_Ship_sShipProducts[$nIndex];
          $sOrigProdRef =~ s/^\d+\!//g;
          
          my $dUnitWeight = $::s_Ship_OpaqueDataTables{$sOrigProdRef};
          - save and exit the file
          - update the site

          The above solution causes the look up of the weight using the original product reference instead of the duplicate product reference. This is necessary as duplicate product details are not stored separately online.
          ********************
          Tracey
          SellerDeck

          Comment


            #6
            ah, excellent, Tracey

            I'm not at the correct computer to do that right now but I'll do it this evening and report back

            Thanks very much
            Tracey
            Tracey

            Comment


              #7
              Fantastic, Tracey, thank you
              That's fixed that now
              Phew!
              I should have posted it over 12 months ago really, when we first noticed it, but it just got over shadowed by more important stuff.

              Much appreciated
              Is the fix the same for V9?
              Tracey

              Comment


                #8
                Is the fix the same for V9?
                Yes it is.
                ********************
                Tracey
                SellerDeck

                Comment


                  #9
                  thanks, Tracey

                  I'll add it to the list of 'things to do before/after upgrading'!
                  Tracey

                  Comment


                    #10
                    *rolls eyes at the realisation that this STILL happens in 9.0.5 (beta) and so I still need to apply this fix*

                    suprised? me?
                    nahh
                    Tracey

                    Comment

                    Working...
                    X