webbymasterru

Simply deleting the /freemius directory from the plugin doesn’t solve the problem. The database crashes, and the frontend displays a “Database connection error.” This indicates a massive database corruption. I haven’t fully verified where else Freemius is being injected, but if it’s corrupting the database, I suspect it’s site-wide.
After clearing the wp_fs_logger table itself, it’s recreated, already populated (about 1.9GB).

After reverting to your plugin version 1.8.9, the wp_fs_logger table was no longer created. Incidentally, at the time of the plugin version change, it was 5.7GB (!)
It’s possible that you had purely good intentions when creating your plugin, and I’m even sure that’s true, but third-party add-ons shouldn’t make it unusable due to their corruption.

The Freemius add-on itself doesn’t appear in the console, but their APIs (local ones, at that) are listed in the /freemius config, which is certainly concerning. This, I think, explains the populated wp_fs_logger table after it’s cleared.

Basically, if you think Freemius should be mentioned as your friend and partner, it should be there and point to their app in the repository, but their app and add-on shouldn’t be running surreptitiously in your shell.

And your plugin is a great idea and implementation, for which I thank you very much. But there’s a saying: “Trust, but verify.”

• This reply was modified 6 months ago by webbymasterru.
• This reply was modified 6 months ago by webbymasterru.
• This reply was modified 6 months ago by webbymasterru.
• This reply was modified 6 months ago by webbymasterru.
• This reply was modified 6 months ago by webbymasterru.