• As other reviewers have noted, this plugin crashed my website.

    Specifically, when this plugin is activated, I immediately get a PHP Fatal Error: maximum memory limit exceeded. The entire site becomes inaccessible. Restoring the site to functionality requires re-naming this plugin’s folder, as that’s the only way to deactivate the plugin when the site is down.

    Yes, it’s true, I could change the maximum memory limit allocated to PHP, just to accommodate this plugin. But I’m not going to do that. I shouldn’t have to do that. None of my other plugins require me to do that.

    This plugin is a resource hog. Rather than require users to reconfigure their websites, the plugin authors should fix the plugin itself. Well-written plugins are not this resource-intensive.

    Note to WPMUDEV staff: I would be willing to reconsider this review if, and only if, you release a streamlined version of this plugin that runs on a stock WordPress system without tweaking the PHP memory allocation. Unless and until you do that, please do not contact me with requests to reconsider this review. Thank you.

Viewing 1 replies (of 1 total)
  • Plugin Support Amin – WPMU DEV Support

    (@wpmudev-support2)

    Hello @mardesco,

    I’m sorry that our plugin didn’t worked on your site. I understand your frustration. I will of course pass your feedback to our developers – if that would be possible can you tell us what hosting provider you are using and what are your memory limits?

    kind regards,
    Kasia

Viewing 1 replies (of 1 total)
  • The topic ‘Crashes site’ is closed to new replies.