Helison S. Cruz
Forum Replies Created
-
Forum: Plugins
In reply to: [Meow Lightbox] Bug causing script delay with debloatHello. Thank you for your reply.
It didn’t work 100%. I still had to disable the “Minify all the deferred or delayed JS files” option in Debloat.
Another thing I noticed is that the close image button disappeared; this has caused some rage clicks on the mobile experience.
Forum: Reviews
In reply to: [Better Core Video Embeds] The best in its category, but…Thank you for your feedback. Your plugin is truly wonderful, and I’ve changed my rating to 5 because your response was very timely. I look forward to hearing from you in the future.
Hi, @oliviertls
Let me share my recent experience with this situation. In my case, what worked was first reporting the 410 error and then, somewhat redundantly but effectively, reporting the noindex again. My server is Apache.
Problem History:
Google is indexing URLs with secupress_dcts_timer | ww.wp.xz.cn<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{QUERY_STRING} (^|&)action=secupress_dcts_timer(&|$) [NC]
RewriteRule ^wp-admin/admin-ajax\.php - [R=410,L]
</IfModule>After a few months I applied this below.
<IfModule mod_rewrite.c>
RewriteCond %{THE_REQUEST} \s/wp-admin/admin-ajax\.php\?action=secupress_dcts_timer [NC]
RewriteRule ^ - [E=NOINDEX:1]
</IfModule>Edit 1: In my robots.txt I also added.
Disallow: /secupress-9a58bee1/
Disallow: /wp-admin/admin-ajax.php?action=secupress_dcts_timer- This reply was modified 7 months, 2 weeks ago by Helison S. Cruz.
Forum: Plugins
In reply to: [Meow Lightbox] Uncaught ReferenceError: wp is not definedHi @valwa ! Me again!
The error didn’t go away; when I cleared my cache, it reappeared. The plugin remains active for you to check.
Forum: Plugins
In reply to: [Meow Lightbox] Uncaught ReferenceError: wp is not definedHi @valwa !
The error disappeared after the last update. I reactivated the plugin today in case you want to check it out.
I’m eagerly awaiting version 2.4; according to the log, it was supposed to be released yesterday. The fix looks promising, but today I managed to mitigate all ulrs, indicating to Google that they don’t exist via htaccess.
Hi @koax
Even after removing the plugin completely from my site, the URLs that had been sent still remain, but now they’re showing “Not Found (404).” From here on, I don’t know what to do. However, traffic has stopped dropping, stabilized, and started to grow again.
I don’t know if this was related to the plugin and the URLs or the recent Google algorithm update, but these URLs have caused serious damage to how Google watch my site.
I also changed my website to use Cloudflare services, there I have almost all the plugin functions and I still have data to validate.
It’s very sad to not get feedback on something clearly caused by a bad code update.
ThanksHi @koax
Well, I applied this code last Monday. The URLs started changing the error type, changing from “Indexed, but blocked by robots.txt” to “Blocked due to another 4xx issue.” Before that, my traffic had dropped by a lot, about 45%. Today, I’ve noticed a recovery in traffic, but I still haven’t been able to identify if it was due to this.
@koax I made a change in my htaccess code and it work. If your server is Apache, add this before the #BEGIN WordPress rule in .htaccess:
# Block any call to admin-ajax with secupress_dcts_timer
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{QUERY_STRING} (^|&)action=secupress_dcts_timer(&|$) [NC]
RewriteRule ^wp-admin/admin-ajax\.php - [R=410,L]
</IfModule>Hi, I tried the same thing, but the indexing didn’t stop. I had to remove the plugin to stop indexing on 754 pages. I also tried the code below via htaccess, but without success. Once Google indexed, even if blocked by robots.txt, if the URL was still active, it would continue to do so indefinitely, and removing it would be costly. This is so sad. The plugin was great, now it’s just bug after bug.
<Files admin-ajax.php>
<If "%{QUERY_STRING} =~ /action=secupress_dcts_timer/">
Header set X-Robots-Tag "noindex, nofollow"
</If>
</Files>I also tried using the Redirection plugin, using regular expression to indicate to Google that urls with “secupress_dcts_timer” are invalid, this method seemed more efficient.