Title: Practically Malware!!!
Last modified: May 3, 2018

---

# Practically Malware!!!

 *  [lucyfift](https://wordpress.org/support/users/lucyfift/)
 * (@lucyfift)
 * [8 years, 1 month ago](https://wordpress.org/support/topic/practically-malware/)
 * I love Patreon and was excited to see a plugin that would add its functionality
   to my website. But this thing broke my website hard. Right after installation
   I got a fatal error message and my site was completely nonfunctional. Fatal error:
   Call to undefined function openssl_random_pseudo_bytes() in /usr/home/www/wp-
   content/plugins/patreon-connect/classes/patreon_routing.php on line 67.
 * So I had to call my sysadmin. And once he got the fatal error fixed, we discovered
   that none of my site images worked anymore. After hours of troubleshooting, we
   figured out that this terrible plugin added an entry to the web site’s root-level.
   htaccess that broke all images on the site. It didn’t remove that entry when 
   I uninstalled the plugin, and it did NOT provide a warning that I’d need to remove
   that entry myself.
 * This plugin does for WordPress sites what methanol does for whiskey.
    -  This topic was modified 8 years, 1 month ago by [lucyfift](https://wordpress.org/support/users/lucyfift/).

Viewing 1 replies (of 1 total)

 *  Plugin Contributor [CodeBard](https://wordpress.org/support/users/codebard/)
 * (@codebard)
 * [8 years, 1 month ago](https://wordpress.org/support/topic/practically-malware/#post-10244863)
 * Sorry to hear you experienced issues with the plugin.
 * Checking what you reported, it seems that the first error you encountered is 
   not due to the plugin, but an important security function used by the plugin 
   not available at your host. There is nothing plugin could do to go around your
   host not having that function. It seems they enabled it after you called them.
 * The image issue you report, should not happen with 1.1.1 unless you explicitly
   enable image functionality. Concluding from that, its possible that you used 
   an earlier version of the plugin – possibly 1.1.0. The current version is 1.1.1.
   This issue may happen if you were using 1.1.0 and you did not update your permalinks
   after upgrading, or your host cached your htaccess rules.
 * I am not able to reproduce any of these issues with a test install on a default
   web host.
 * In any case, all of these issues could be handled if you visited the official
   support forum that is listed in plugin’s options page.

Viewing 1 replies (of 1 total)

The topic ‘Practically Malware!!!’ is closed to new replies.

 * ![](https://ps.w.org/patreon-connect/assets/icon-256x256.png?rev=1782351)
 * [Patreon WordPress](https://wordpress.org/plugins/patreon-connect/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/patreon-connect/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/patreon-connect/)
 * [Active Topics](https://wordpress.org/support/plugin/patreon-connect/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/patreon-connect/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/patreon-connect/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [CodeBard](https://wordpress.org/support/users/codebard/)
 * Last activity: [8 years, 1 month ago](https://wordpress.org/support/topic/practically-malware/#post-10244863)