[Flashpaper]

It concerns me that this fix was posted over a 2 years ago, yet the error still happens on WordPress 3.6.1. as of November, 2013 on a site I’m building. I just purchased this plugin after having used an old version of it without problems on another site years ago. Any patches or updates available that address this problem? Perhaps my concerns are unwarranted, but as a QA professional stuff like this really raises red flags since my own plug-in developers would not get paid if their plug-ins resulted in warnings like this.

[Author]

Posts