Announcement

**John Ennals** · 23-Mar-2024, 10:14 AM

Why Sellerdeck have chosen not to tell all their users about this known problem as a matter of urgency is beyond me. I actually suggested they use the new message centre for this but that seems to have been ignored.

Anyway, below is the fix supplied to me by Sellerdeck, and which I am told will be incorporated as standard in 18.2.4.

Go to ‘Design | Library | Layouts’ and scroll down to the ‘Javascript Header Functions’ group and expand it.
Open the layout ‘Standard Javascript Header Functions’ and move down the code until you see the line: -

<script defer crossorigin="anonymous" src="https://polyfill.io/v3/polyfill.min....etch%2CPromise"></script>Remove this code and replace it with the following: -

<script type="text/javascript">
$(document).ready(function() {
$(".usesFetch").show();
});
</script>
And click ‘OK’ to save the layout.

Once you have done this go back to ‘Settings | Business Settings | Payment and Security’ and change the in option in the ‘Present Payment Options As’ selection box to ‘Accordion’ and upload the site for the changes to take place online.

John

**Seorch** · 23-Mar-2024, 12:03 PM

I'm not sure what's going on, as my main section image links on the home page are not going to the Actinic directory sections but to the root directory, so I've had to redirect some pages from the root.

footballtrophy.co.uk/football-trophies.html
<body><meta http-equiv="refresh" content="0; url=https://footballtrophy.co.uk/shop/football-trophies.html"></body>

Edit in reply to post 7: I'll update here as I don't want to dilute the Accordion error thread. Yes, it may be unrelated and a possible other script error as I wasn't getting the cookie prompt once the cache had cleared.

**Buzby** · 23-Mar-2024, 03:39 PM

We were on holiday for two weeks and still receiving healthy orders whilst closed. And then about 13th the orders dropped off a cliff. We then had a few messages saying there wasn’t anywhere to enter card details. We checked and could see this was the case.

we couldn’t do anything as we were in Turkey, so just had to suffer the losses.

upon our return this week I found if I reintroduced Bank Transfer as the first option, when you then had to select Clear accept, the details would then populate.

a bit peed off that this was more widespread that our site, and Sellerdeck haven’t fixed or advised.

**EdHarrison** · 23-Mar-2024, 03:51 PM

I assume this was a clearaccept issue?

**Seorch** · 23-Mar-2024, 06:02 PM

Not the payment service but the way it is presented.

**John Ennals** · 23-Mar-2024, 06:07 PM

I assume this was a clearaccept issue?

No, it was caused by third party "polyfill" code which was being loaded by Javascript Header Functions to provide compatibility with IE11. Apparently the third party code has become unstable or something, so the Sellerdeck fix means it is no longer used.

I've applied the fix and it's working fine, and orders have started coming through again after nearly a week of nothing. My concern now is that my regular customers, upon whom I rely heavily, will have lost confidence if they've recently been unable to place orders due to this fault.

I'm not sure what's going on, as my main section image links on the home page are not going to the Actinic directory sections but to the root directory,

I haven't experienced this and it sounds like a completely separate issue to me, however I may be wrong.

My advice is to apply the fix regardless of whether you are using Accordion payments.

**EdHarrison** · 23-Mar-2024, 07:30 PM

I have not had the issue, I am on 18.12 with radio buttons, is it still wise to do the fix?

Thanks Ed

**John Ennals** · 23-Mar-2024, 11:52 PM

Ed,

Since you're not using accordion payments and if everything else is working, it'd probably be best to wait and check with SD support to be on the safe side. But I've been told the fix is going to be standard issue from 18.2.4 onward, so I doubt whether it would do any harm.

The reason I suggested applying it anyway was to cater for the possibility that polyfill.min.js is used by other aspects of Sellerdeck websites, not just the payment bit of the checkout. I don't know if this is the case, but if it is, it is possible that it might be causing other adverse effects.

Anyway, this is all well beyond my pay grade. Hopefully Sellerdeck will issue some sort of clarification next week, and until then "if it ain't broken, don't fix it" is probably the best way to go.

**EdHarrison** · 24-Mar-2024, 07:26 AM

Thanks John, I will wait but have a quick look around at various basics to see if anything is looking odd.
Quite worrying that something that halts sales haa not been addressed more urgently unless its more complex than it appears.

**Mantra** · 25-Mar-2024, 05:00 PM

Originally posted by John Ennals View Post

Ed,

Since you're not using accordion payments and if everything else is working, it'd probably be best to wait and check with SD support to be on the safe side. But I've been told the fix is going to be standard issue from 18.2.4 onward, so I doubt whether it would do any harm.

The reason I suggested applying it anyway was to cater for the possibility that polyfill.min.js is used by other aspects of Sellerdeck websites, not just the payment bit of the checkout. I don't know if this is the case, but if it is, it is possible that it might be causing other adverse effects.

I am using V18.2.2 with Present Payment Options As Drop-down List and not aware of any problems with this setting, however, I would suggest if other users apply the fix before upgrading to V18.2.3 to keep a check log of the change made because in my experience when a change like this is applied to an earlier version of the software it gets overwritten when upgraded and needs to be re-applied except when the fix is applied in the later version in this case V18.2.4 - hopefully!

**gcamley** · 26-Mar-2024, 10:35 AM

When the cause of this problem was first tracked down it was expected to be a temporary glitch due to the migration of the service between servers. We also needed confirmation that the fix was working, which added another delay.

Given the continuing reports from customers it was decided that we should remove the code that uses the 3rd party service completely. We have prepared a Knowledge Base article to detail how to remove the dependency - see https://community.sellerdeck.com/for...-do-not-appear. The change is the same as described earlier in this thread.

**graphicz** · 26-Mar-2024, 11:09 AM

Hi John - look what is going out: You lead and the world follows!

10:49 (13 minutes ago)

Click image for larger version

Name: criticalbug.jpg
Views: 62
Size: 49.9 KB
ID: 556992

**Hugh Gibson** · 26-Mar-2024, 11:18 AM

Thanks for confirming receipt, Jonathan.

We've also used the Important Messages extension (added for 18.2.3) for the first time. Can anyone on 18.2.3 confirm that they've seen this message? You might have to restart Sellerdeck Desktop for it to appear.

**graphicz** · 26-Mar-2024, 11:33 AM

Do we have to delete this chunk too?

Code:

<script type="text/javascript">
/***********************************************************************
*
* polyFillsLoaded - called when the Poly Fill JS bundle has loaded
* Note the defer attribute so that it only runs after the page is loaded
* PolyFills are required to support Fetch and promises in IE11
*
************************************************************************/

function polyFillsLoaded()
{
//
// Now okay to do anything that depends on fetch
//
$(".usesFetch").show();
}
</script>

I guess so as there is no polyFills to load.

Announcement

Accordion users act now

Accordion users act now

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment