Resolved Widget FW , CACHE, and Ajax tabs errors

Hello @xfrocks and everyone

I'm using Widget framework

There seems to be a problem when you use TABBED (grouped) widgets, which require ajax calls when they are clicked, and the WF Cache

When the WF is configured to be on cache (WF cache backend = memcache, or database or files), the ajax calls do not work all the time, sometime they spit out a couple of "\n" instead of the content.

this is always true if I flush my memcached (restart) backend store

What Can I do about this ?

 

Forgot to say ha t this is with latest b14 on latest xf

 

It seems to me there are still various issues with tabs.
Some tab loads are refused ; reloading the page once or twice solves it...

 

Thanks for your attention,
It's really difficult to reproduce, I'm trying to come up with useful info for you.
All I can say is that it affects "not busy boards" (my dev website), if you hit reload 2 or 3 times all tabs finally seems to work.

I know that java answers back an error because of the size of the answer, sometimes calling the url of the ajax call ( asking for json) a second time works well, sometimes you've got an empty ajax (that you can see as a json answer in your browser) a dozen of times in a row

it's really weird. I'm trying to find useful infos for you and will post them here.

 

Sorry it's not a ajax error it answer; it's this

{"css":"","js":"","templateHtml":"\n\n\n\n\n\n"}

I can now reproduce all the time, when flushing my memcached ( cache backend )

If you hit reload a few times, it finally goes fine.

It does not seem to be related to BD-cache, it seems to be a problem with the tabs widgets and WF's own caching system.

It happens with all kind of widget (thread, resource manager, etc).

Is basically gives out a "\n" per expected line of output... And start behaving correctly after a few reloads

 

Problem disappears when switching off WF's own caching

Cache Store

• Disabled

then there is no problem.

Problem occurs with both memcached or wf database as store backend


It's a bug in WF when (1) using tabs (2) at the first pageviews (flush your cache, restart your server, etc), or after 300/600 secs : after the cache expiration.

Which makes the problem occur all the time, by chunks of 5 minutes.

 

And I can assure you I'll buy another addon, even if I don't need it, if you could fix this

 

can we get an update ? can you confirm the bug ? is anyone working on this ?
The tabs basically do not work with cache, which is the recommended setting for WF ("use in production")...
so it's kinda major bug.