Can't delete custom code

[mikeoui]

I added custom code to my store for an affiliate program. I have ended that program, but the area for adding custom code has changed and there is no way for me to view (and remove) the code I added before the change. There is now a "Custom Code" area, but the custom code I entered into Cart Page and Receipt Page is not shown there. 

Thanks,

Mike

[Frida]

Hello @mikeoui,

Thanks for posting in the Seller Community again, welcome back! 😊

Sorry to hear you are encountering this issue. Full transparency here, this is currently a known bug and an open ticket that has been filed with out Engineering team. 

I am keeping my eye out for a fix or update related to this matter, but in the meantime, please feel free to call into Customer Support to see if any additional account related information is needed.  

[miss_anthropy]

Has this bug resurfaced? I am currently having a similar issue where I have added an embed code section to my Stories page and when I try to delete it, this error comes up:

The page is published and all efforts to remove then save/publish are ineffectual.

ETA: I eventually got it removed by editing it on the mobile site. 

[Laurie_]

Thanks for keeping us in the loop here, @miss_anthropy, and sorry to hear you ran into these issues when editing your Square Online site.

As far as I'm aware, we haven't seen this issue resurface internally but I can certainly flag this with our team so they're aware.

When you noticed the issue first occurring, what browser were you using at the time?

[miss_anthropy]

I tried with both Opera and Chrome on desktop, and was finally able to delete the section using Chrome on Android. 

[Laurie_]

Thanks, @miss_anthropy!

I've flagged this to our team but if you do notice this same behaviour again when logged in on your desktop, we first recommend switching to another browser. 

We've included a list of supported browsers in our Square Dashboard Troubleshooting guide. 

Failing this, please let us know if you experience this again in future.

I'm hoping though that this is a once-off for you given we've received no other reports with similar behaviour. 🤞