Updating a browser
/*\ |*| |*| :: :: |*| |*| A complete cookies reader/writer framework with full unicode support.
|*| |*| Revision #1 - September 4, 2014 |*| |*| https://developer.mozilla.org/en-US/docs/Web/API/document.cookie |*| https://developer.mozilla.org/User:fusionchess |*| https://github.com/madmurphy/|*| |*| This framework is released under the GNU Public License, version 3 or later.
We published a post 8 hours ago, and our feed was still not updated.
After some tinkering around and research, we managed to find several potential solutions.
In the left column you will now see a button for “Pingshot”. This will cause your feed to ping every time there is an update.
Clicking on it will clear Feedburner’s cache and refill it with your new content. Our new content was now appearing on the feed, but why should we have to do this every time?As a matter of last resort, if you have a caching plugin like W3 Total Cache or WP-Supercache installed then you may have to clear the cache from your admin panel or simply disable caching the feeds.Although this is written for W3 Total Cache, a similar method will work for other plugins. Under that there should be an option for “Page Cache”.Press the “Ping Feedburner” button to update your feed immediately rather than waiting on Feedburner’s automatic update that happens every 30 minutes. But as you can see with our reaction, it did not work for us.As we scrolled down the list of troubleshooting options, there was the option to Resync your feed.