ALDesigner

@lschuyler Thank you so much for looking into this and for the speedy turnaround! You rock!

Thanks for getting back, @611shabnam. I typically use ManageWP, but in this case I was logged into this particular site’s dashboard and viewing the active plugin page.

The usual red warning that I’ve seen before on other plugins when PHP wasn’t compatible is not displaying, which I understand only appears when the plugin has a minimum PHP explicitly set. Since 23.8 isn’t displaying that message, and getting this site migrated isn’t going to finish soon, I wanted to check if updating while still on PHP 7.2.5 would work. I’ll rather hold off updating if more than very minor issues could occur, but I understand why your team may want to take a softer approach to enforcing the PHP limit so as to not feel like it’s locking people out.

Glad I found this. Same is happening to me, as well as alignment not working. Had to add a bit of CSS, as shown in other replies. My only issue now is that I have 107 sites to go through and do this to now…

UPDATE: After spending nearly 2 full days digging deeper into the matter, we’ve been able to determine that the Simple Share Buttons Adder plugin is not the cause for our sites being flagged for malware. Since that was the only change that occurred to any of our sites in recent history, we wanted to at least bring it to attention for possible consideration.

Turns out the issue is from a script served to our sites by our CDN provider that is being falsely perceived as a shopping card exploit (we don’t even use the software this exploit is supposedly for, so the confused ensues).

@devnihil The issue appears to be resolved with the latest Yoast update. New comments are now nesting properly on all of our custom themes.

Thanks again for the info / help.

@devnihil Thank you for the response!

On the sites that experienced the issue, we were using the latest Yoast and all sites had just been updated to 5.5 core. Sites that were rolled back to 5.4.2 no longer experienced the issue with comments not nesting.

We’ve been testing since, and the combination of factors necessary to replicate with consistently seems to be specifically Yoast 14.7 + WordPress 5.5 + our custom blog theme. It’s the same theme for all 100+ sites, but it uses the generic comments.php also seen in most of their TwentyN themes. Disabling Yoast OR rolling WordPress back to 5.4.x OR disabling our theme each resolve the issue.

We’ll look deeper into what it is about our theme that could be causing it and, if we find anything that might be helpful to your team, let you know.

Thank you for the reply, Bill. Apologies for my belated response.

ShareCount.com analysis of the URLs produced a numerical count, while the pages continued to show “0.” Unfortunately, since this was for a paying client, we have [at least temporarily] switched to a different plugin.

I will set something up in a test environment when I am able and test some more.

I would like to also request this feature. We currently use a small script to automate this process, but it requires going to each site we manage and running it. Something built in would be greatly appreciated!

Were you able to resolve both of these issues?

Same problem here. Just installed the plugin to use for sending notifications of comments being posted to all authors for all posts. No one, myself (admin) included, is getting any emails.

Default notifications to the author and admin, plus all other system emails, are getting through normally.

Just noticed this today. I went through and disabled and re-enabled all plugins to see who the culprit was. I was half expecting it to be Yoast, but was surprised when it turned out to be this plugin. Kind of a shame, really, as it’s a very basic plugin I’ve used for a long time.

All in all, I understand that they have to keep the lights on and the water running, but it felt like it came out of nowhere. A dashboard banner indicating that ads were incoming would have been appreciated.

@wpchefgadget,

After getting the site back up we went through the contents of the blacklist to see what may have been the issue. We have a small script we run to try to extrapolate suspect IPs, focusing heavily on repeat lockouts. Turns out someone here was trying to log in, constituting a false-positive, and after they tried a bunch of usernames that all failed the IP was added to the blacklist. In short, we added one of our internal IPs that should have been whitelisted and blocked ourselves.

@prathameshp Thank you.

Second this. I would love a feature where IPs are automatically appended to the blacklist after N number of lockouts.

An option on the plugin settings page in the WP dash would be appreciated. Thank you!