WPIntell

Source evidence

Bug in plugin with Post Compare

Toggle wpautop · support · 2014-07-16T15:15:00+00:00

complaintsentiment
highseverity
1.0relevance
3replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

8 / 34 rows with source links

23.5% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

26 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
Lou Friedman unresolved
Plugin worked great, until: 1. I tried to revert a post to a previous version using WordPress compare revisions screen. 2. The previous version may have had the correct HTML in the Text portion of the editor, but may not have had wpautop toggled ‘on’ and something went horribly wrong. The plugin ate up over 500MB of memory on my server, sent CPU usage to 100%, and caused my site to display a 503 error; it essentially broke my site while carrying out a rather simple process. Developer should be made aware of this bug. I’d be happy to provide more details if needed. Thanks, Lou https://wordpress.org/plugins/toggle-wpautop/ Hey Lou, The plugin is very minimalist on how it functions. We’re you able to reproduce it? Additionally did you have any other plugins installed at the time? Our team has the plugin installed on easily 40+ sites, including multisite installs and haven;t seen this reported yet. Any additional details would be greatly appreciated. Did you have anything in the logs? How did you know/confirm wpautop caused the memory consumption and the resulting server crash? Hi aware. I didn’t try to reproduce it. Maybe I will outside of normal business hours to prevent the site from disappearing. Let me get some logs for you. Umm, eh, where do I find those again? When the server stopped due to 503, the godaddy rep I was chatting with stopped the PHP processes, but the memory usage was still very high. Since this was the last plugin I had installed, I deactivated it and right after that memory fell from 500MB to 45MB. That’s me only evidence. It’s not rock-solid. It definitely sounds like something else is going on Lou, The plugin performs extremely simple operations. Have you still been having problems?

Comments

3 shown
Aaron Ware 2014-07-16T15:36:00+00:00

Hey Lou, The plugin is very minimalist on how it functions. We’re you able to reproduce it? Additionally did you have any other plugins installed at the time? Our team has the plugin installed on easily 40+ sites, including multisite installs and haven;t seen this reported yet. Any additional details would be greatly appreciated. Did you have anything in the logs? How did you know/confirm wpautop caused the memory consumption and the resulting server crash?

Lou Friedman 2014-07-16T16:15:00+00:00

Hi aware. I didn’t try to reproduce it. Maybe I will outside of normal business hours to prevent the site from disappearing. Let me get some logs for you. Umm, eh, where do I find those again? When the server stopped due to 503, the godaddy rep I was chatting with stopped the PHP processes, but the memory usage was still very high. Since this was the last plugin I had installed, I deactivated it and right after that memory fell from 500MB to 45MB. That’s me only evidence. It’s not rock-solid.

Jonathan Desrosiers 2014-08-02T14:10:00+00:00

It definitely sounds like something else is going on Lou, The plugin performs extremely simple operations. Have you still been having problems?