Help. we did an upgrade last night, and I was trying to resolve an issue with our mobile display, and when I turned off “header display” under Ads for phones, we started to receive an issue where mobile tagDiv code is not being interpreted…you can see if you go to http://www.distressedmullet.com our site is not rendering. BTW, did a restore and it’s still an issue. After spending hours searching cache’s blah, still no idea what’s going on. Please provide your thoughts on this ASAP 🙁
Tim
So I spent hours …disabling and trying to see what was conflicting with no success. our staging site works and as i mentioned, so did our production site until the change i mentioned. Check it out at:
https://distressedmullet.com – prod
https://staging-distressedmullet.kinsta.com/ – test
Test works, prod doesn’t. I’m hoping you can help. Let me know if you need login info etc. to check it out and how i can get it to you. thanks.
Hi,
So the issue happens just when the mobile theme plugin is active? We could take a look at it, send us admin login at contact@tagdiv.com and we will activate the mobile theme to see what is happening exactly. If you have any more useful details mention these in the email.
Include a link to this topic in the email.
Thanks
Thanks, Simion. No, it was when it wasn’t active. So here’s what I think. It was caching. Something went weird and got cached. When I went back at it this morning, it’s now working. 1) I hate caching and 2) did I mention I hate caching? 🙂
Anyway, let’s call this resolved as I think that’s what it was. BTW, I’m not using the mobile theme as I need the capabilities of the builder and the different tagDiv designs.
Thanks for the quick reply…and the moral of this is beware of caching…as always.
It seems that the conflict is with AppPresser. Have you guys worked with them at all? There’s a “mobile theme” that is not active but is managed through their plugin for building mobile iOS and Android apps.
Want to pull the thread on trying to understand what’s causing it to get it worked out. I’m reaching out to them too, but checking to see if you have any experience.
Thanks! Tim
Looks like we figured it out. It was aggressive caching by Kinsta that was causing all this blowback. Just fyi, in case it ever comes up again. We excluded the cookies for AppPresser and it’s fine. Nothing to do with you guys but affecting you guys. Thanks!