wpopt
Forum Replies Created
-
Forum: Plugins
In reply to: [Grow for WordPress] Ads displaying when activeYou didn’t mention whether or not these sites are supposed to have ads or not – if they are then I assume Grow is responsible for outputting the script wrapper which serves ads on the site, so the presence of ads in itself isn’t indicative of a problem.
As mentioned, if the sites are not supposed to have ads then this would need to be addressed by the plugin developer.
I’m sorry – I’m not trying to be difficult to you – I’m just a strong believer in clear, well-defined scopes and issue descriptions 🙂
Forum: Plugins
In reply to: [Grow for WordPress] Ads displaying when activeWhich ad network, if any, does this user use? I’m not super familiar with Grow, I don’t know if it takes the place of the Mediavine control panel and outputs the script wrapper into the site itself.
You’re being a bit sparse with details – if the sites are *supposed* to have ads showing on them, then a malicious ad needs to be reported to the ad network. It’s not something directly related to this plugin and so reporting it here isn’t the appropriate location for that.
If the sites are *not* supposed to have ads, then this is the appropriate place to report such an issue, assuming you have correctly ascertained that it is indeed this plugin which is responsible for outputting those (and assuming the display of ads isn’t detailed in their terms of use somewhere – in which case the issue still needs to be reported directly to Mediavine)
- This reply was modified 3 months, 1 week ago by wpopt.
Forum: Plugins
In reply to: [Grow for WordPress] Ads displaying when activeI should point out that I’m not a Grow developer, but I came across this and wanted to comment.
Am I missing something here – ads aren’t served from Grow, they’re going to be served from the ad network script (if this customer is a Mediavine or Mediavine Journey customer then they’ll have a Mediavine control panel plugin installed).
Have you verified that the ads are being output by Grow?
Furthermore, while undesirable, despite their best intentions, malicious ads can slip through ad networks’ checks. We get a handful of reports every year from people who think they’ve been hacked because of a weird redirect or popup, when in fact it’s always caused by a rogue ad. Such behaviour should be reported to the ad network immediately so they can identify and remove the offending ad!
Also MariaDB here 🙂
Glad we’re not the only ones. Had a huge number of queued database queries on a site we manage following an update to this plugin, all ALTERs as OP mentioned, triggered by AIO SEO. Have reverted to the previous plugin version for now.
Ok, annoyingly, I’m unable to reproduce this issue myself, so I’ve updated the site to the latest version of Kadence now and it seems just fine. I’d suggest OP ensure they purge any cache and optimization plugin (such as generated used CSS and the like).
fwiw, I’m going to spin up a staging site later with one of our affected sites and try and go through and identify the potential cause. I’ll report back 🙂
1.3.3 has the issue, yes – 1.3.2 as well (we updated from 1.3.2 in the hope the issue would be resolved).
It’s possible 1.3.1 was ok, but I reverted to 1.2.x.
I should add that in my case, the issue isn’t exactly as the OP describes – the main content area breaks out of its container and forces the sidebar to a width of about 60px, so not stacked.
Yeah, we’re also seeing major layout issues with Kadence 1.3x across several sites – seems that #main is breaking out of .content-container.
More troubleshooting than that I didn’t do because the site owners were more eager for their broken sites to be fixed.
I think the problem mainly arises with the fact that the plugin no longer requests the email address – it just asks for the API token and domain… it cannot authenticate without the email address so cannot proceed with the setup correctly.
Hi @wfpeter,
We (as the host) have made no changes on our side. In the run-up to thanksgiving and Christmas in general we keep any changes to an absolute minimum given that it’s our customers’ busiest time of year. As a result, I can confidently say that there were no server changes or updates which may have caused this.
It was not caused by any ModSecurity conflicts, since one of the affected users had ModSecurity disabled.
We use Imunify360 which has a wide array of security features which have previously been the cause of difficult to diagnose issues, but with its web security features disabled, the issue persists.
From what I can tell from our logs, the issue seems to be requests made to /wp-admin/admin-ajax.php which are immediately getting aborted:
2024-11-26 17:22:46.825021 NOTICE [5451] [T0] [my.ip.address:64077:HTTP2-145#APVH_some-site.com:443] POST request in process stage, fail with 503
2024-11-26 17:22:46.825037 NOTICE [5451] [T0] [my.ip.address:64077:HTTP2-145#APVH_some-site.com:443] oops! 503 Service Unavailable
2024-11-26 17:22:46.825041 NOTICE [5451] [T0] [my.ip.address:64077:HTTP2-145#APVH_some-site.com:443] Content len: 76, Request line: 'POST /wp-admin/admin-ajax.php HTTP/1.1'LiteSpeed Web Server will return a 503 error when a site has a lack of resources – this was not the case here (no resource limits were being hit) and it also returns a 503 error when an IP has been throttled or blocked due to a firewall rule or rate limiting block under certain circumstances in my experience.
This happened across numerous environments today, and as mentioned in reply to another commenter, we noticed the same thing happened suddenly with another popular security/firewall plugin (BlogVault).
Eventually it was determined that users of PHP 7.4 were the only affected users, and it seems likely, based on the simultaneous occurrences that perhaps some rule (perhaps a generic one which both services use or reference) has been modified or published which causes this? I’m afraid I don’t know enough about the inner workings of how Wordfence is working to offer further suggestions here. Just to clarify, I’m not suggesting Wordfence *itself* is the issue here, but actually a firewall rule in use.
@peopleinside Yes, PHP 7.4 is still widely in use. As a service provider we encourage people to change but it would be bad service to enforce a change to PHP 8.x and completely disable the sites of people whose sites are not compatible.
In many cases, it’s as simple as removal of a plugin – in other cases it’s their theme, and some people don’t have the desire, the time, the money, or the technical expertise to implement the changes necessary to make their site ready for modern versions of PHP.
I understand that they *should* be using new versions of PHP, but WordPress core, and Wordfence explicitly support PHP 7.4, so implying that this isn’t an issue because people “shouldn’t be using that version of PHP anyway” really isn’t helpful.
@dmorgan20 we actually saw the issue with another fairly popular firewall plugin as well, albeit a premium service so no support here in the forum. Evidently they’ve both deployed a rule or rules which are causing this issue.
Badass! Thanks guys 🙂
Forum: Plugins
In reply to: [Revision Manager TMC] Latest update causing high loadReally bad to see my support request being ignored. I guess the only option is to recommend my users to use a different plugin.