Announcement

Collapse
No announcement yet.

YASB - HTML Emails corrupting prompts.

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

    YASB - HTML Emails corrupting prompts.

    YASB - Yet Another SellerDeck Bug.

    Intermittently seen on 16.0.3. Not seen on 18.0.0.0 SEGA. HTML emails are corrupting the cart display because SD is sticking newlines in at a set number of characters regardless of whether this is in the middle of an HTML tag.

    To see this the demo site Diamond Pendant with an other info prompt of

    Long other info prompt that may cause email problems

    Then view that product and put the following into the prompt field
    Code:
    -----------------------------------------------------------------
    Now checkout and your customer email will contain:
    Long other info prompt that may cause email problems
    ----------------------& #45;------------------------------------------
    This will undoubtedly affect SD 2018 too.
    Attached Files
    Norman - www.drillpine.biz
    Edinburgh, U K / Bitez, Turkey

    #2
    Is this in v18, Norman? We fixed a bug a few releases ago which looked a bit like that.

    Have you reported it to Support at all?
    Bruce Townsend
    Ecommerce Product Manager
    Sellerdeck Ecommerce Solutions

    Comment


      #3
      Also, did you have code compaction enabled?
      Bruce Townsend
      Ecommerce Product Manager
      Sellerdeck Ecommerce Solutions

      Comment


        #4
        Apologies for not mentioning the versions I was testing on. I'm usually clear about that. I've amended my initial post.

        I've tested this on three sites now and have mixed (but hopefully good) results.

        All sites have Compact HTML/CGI/JS checked.

        I saw it on an clients 16.0.3 site that had been upgraded from earlier V16 releases. I re-ran the test on a copy of that site here using a different SMTP server and saw the same issue.

        I just tested it on a clean 16.0.3 site (same SMTP server as used on the failure sites) and cannot reproduce the error.

        I also tested on a clean 18.0.0 SEGA site and that works fine too.

        So it could be that something in sequence of V16 site upgrades hasn't carried through in the 16.0.3 site that I'm seeing failures on. When I get time I'll look at the Perl script revision numbers and see if there is an old script in use.
        Norman - www.drillpine.biz
        Edinburgh, U K / Bitez, Turkey

        Comment

        Working...
        X