I just read in another thread that this issue may be the result of a bug. In a prior life I worked for a high end enterprise software development company and along with every release, we also published what is knows as a KBR, or Known Bugs Report. I would recommend you do the same. It sucks to waste so much time trying to figure this stuff out independently. As well it also sucks to have built a solution around an application such as yours that goes in the crapper because of a bug. You might want to take a look at your testing procedures to keep this from happening in the future. It’s one thing to develop new functionality that has bugs, it’s an entire other issue to induce bugs in known working functionality – because people expect that what was working without error before will continue to work after an update. Make sense?
unfortunately I believe that this is an error with the latest WP & AiOEC versions conflicting. the quick fix i was able to come up with was to downgrade WP to 4.3.x. It’s far from the most ideal situation, but until time.ly addresses the issue then I don’t have any other answers.
and FYI, i spent like FOUR HOURS trying to debug this issue until i stumbled upon some other posts mentioning some of the incompatibility issues.
anyhow, i downgraded, refreshed my feeds, and i was back in action.
