The cache just uses the php SESSION to store the widget output while the user is viewing the site. I’m not sure why it would be showing an empty list, but just clicking save on the widget options will reset the cache. I’ll take a look into it, see if I can find something.
ok, try to get rid of PHP SESSION, it has caused conflicts with other plugins; search about “session” here:
http://wordpress.org/plugins/si-contact-form/changelog/
Just FYI, I’m using WP Super Cache, CDN enabled for use with Amazon Cloudfront. Maybe the empty list is a cache compatibility issue.
Best regards
Ok, I thought using a named cache would remove any conflict issues, but I guess I should do some more digging. Thanks for the resource.
After some digging, I have found how to test if a session has already started or is allowed to be started, so it should help with any conflicts. But the question is this: should I still try to cache the widget output for better performance or should I just try to avoid SESSION altogether?
Good question. I’d say that if SESSION gives you a good result to store cached items, then do your best to detect any possible incompatibility and catch it from the code itself to prevent the script to trigger errors.
🙂
What else can you use if not SESSION? cookies? mysql cache?
I removed the cache, should work now.
I tested it now. The widget was seamlessley updated. Not blank views. Good job boy!!! 🙂
