It doesn’t always come up, and I’ve been able to do a little bit of work, but between refreshing, this happens. Notice it doesn’t trigger on all the blocks, it starts with the tab blocks, then breaks the rest of the blocks below.
Really not sure why Cwicly needs to phone home to function.
The wording as I told you before is the main issue here. It makes us think that Cwicly is doing a license check while loading the blocks and failed to verify the license. Please update the wording to something like Blocks failed to load or whatever appropriate.
Thanks for the link. I’ve installed and will try it out. It should help, as it requires a break in my work to actually document and send in these bug reports.
@Louis, typically it’s not that I won’t want to follow up but, by the time I get around to posting here, I’d have spent many hours trying to work through and troubleshoot an issue. As mentioned above, having to stop time sensitive work to submit a bug report isn’t always feasible.
The license check problem has gone away somewhat with recent updates. I still get a license check notification every now and again. I can’t always know when it will happen, but I will turn on screen recording to see if I can catch it in the wild.
I’ve encountered it on my current project which uses about 10-12 repeaters + tabs (nested) on a single page. It tends to get triggered when the dynamic data needs to load. Refreshing the editor page does usually rectify it.