Teeinblue product page problem

[BOHSFootball]

I am having a HUGE issue with the way Teeinblue interacts with my product page in Shopify.

Any time I try to add, delete, or hide any of the blocks within the Product Information section of my product page in Shopify, all Teeinblue personalization fields disappear. And if the change gets saved, it's irreversible, even for new campaigns. I first noticed it when I tried to add collapsible rows for product info, size charts, etc. to that section, so I thought the collapsible rows were the problem, but now I've realized it does it when you alter ANYTHING in that section. You can't even hide or delete a block without the personalization fields disappearing. It doesn't appear to do it when you alter sections other than the main product info section.

I then decided to look for another template to see if it did the same thing (it did it with every template). This is definitely a new problem, because I had added collapsible rows to the Product Information section on another site months ago. Those rows are still there, but the minute I try to alter that section again, the Teeinblue fields disappear.

Is anyone else having this issue? And is this an issue with Shopify or with Teeinblue?

[Small_Task_Help]

Hi,

Few possible reasons can be

- Dynamic Section IDs and HTML Structure Changes
- App Block or App Embed Issue
- Shopify’s Default main-product.liquid File Update

[BOHSFootball]

Thanks for the reply, but it did it even with a brand new, undoctored template. I tried multiple templates, browsers, etc... Lexie ended up emailing me to let me know my app embed was off. I never turned it off. So I turned it back on and tried editing the Product Information section again... literally just hiding the brand title... same thing. When I looked, it had turned off again. So I turned it back on and tried adding a block to that section, and the personalization options vanished again. I checked the app embed and it was still on. So I turned it off then on again, and voila! Everything worked again. So it seems I'll be fighting this glitch until it's sorted out, but at least I figured it out.