Pat K
Forum Replies Created
-
Forum: Plugins
In reply to: [Blackhole for Bad Bots] Adding Blackhole Rule to Generated robots.txt fileExcellent! This is most helpful. Thanks!
pkMe too. It is worth mentioning that the email is NOT being generated from WordPress, rather from “support@analytify.io”. Per emgraphics’ original post; there is a note at the bottom of the email message that reads:
Note: We hope your weekly Analytics summaries encourage the efforts you are putting in your business. But if you no longer wish to receive Analytify Insights emails, you may change your preferences from plugin settings.
If this were true, I would have either disabled it OR specified the address of someone who actually wants to receive these messages.
Otherwise, the plugin is working great – I’m hoping the developer will address this.
pkForum: Plugins
In reply to: [Blackhole for Bad Bots] Adding Blackhole Rule to Generated robots.txt fileFollow up – I forgot to reference this:
https://www.machine-agency.com/blog/adding-items-dynamic-wordpress-robots-txt/
…the source of the code snippet.Thanks for the fast reply Bill. On the sites in question wp-cron.php has been disabled and a manual cron job set up via cPanel (to speed things up) – in case your plugin is hooking into wp-cron.
I believe the other 2 tables that were not removed on uninstall were sbb_fingerprint and sbb_http_tools.
Thanks for the reminder. I still haven’t figured this one out. If / when I do, I’ll be sure to report back here.
pkExcellent! Thanks for the tips!! I’ll do some more testing and when I figure this out, I’ll post back here.
No, not by the wizard. I like to do stuff manually, so I have AutoFix turned OFF. I’m talking about the prompt at the top of the admin screen. If that’s copied and pasted it adds 2 non-breaking spaces (a tab indent) in the code window.
I think it may be a moot point though because I applied this fix on another site and was still getting the intermittent broken pages afterwards. Of note, I did a ‘wordpress reinstall’ from the WordPress Updates page and this seemed to make matters worse. In the short term I’m disabling script concatenation – until I have more time to troubleshoot.
I’m wondering if caching may be partly responsible…maybe updating the salts for the authentication keys in config file?
Thanks for following up! If you have any troubleshooting ideas (other than what I’ve listed above) I’d be happy to try them!
Hmmm. The editor stripped out the blank spaces before “AddHandler” in my original post. Just make sure there are no blank spaces before “AddHandler”…and time permitting AITpro might consider removing those blank spaces in the helpful code snippet.
Thanks awesome developer!
Sorry, no. The error message was disabled as soon as I ran the manual plugin update. I’m pretty sure it’s part of WP 5.1’s WSOD protection feature (https://wptavern.com/wordpress-5-1-to-introduce-new-white-screen-protection-feature-beta-1-now-available-for-testing). It basically said the plugin was disabled to keep the dashboard from crashing.
On the 2 separate sites this affected, I used a backup file to create a clone of the site (in a subdirectory), then looked at the plugin settings (the custom text) to verify it was actually there and I wasn’t mistaken / losing my mind (the text was there) and I copied it over to the updated plugin running on the live site.
I then ran the WP & plugin updates in both cloned dashboards and the same thing happened; error message and data wiped from the plugin settings.
This was a major PITA, so I have since opted to use custom functions for the custom cart & checkout text and have deactivated and uninstalled the plugin. I hope you figure this out and can implement a fix for other people using the plugin.
I considered turning this off using CSS, then realized doing so would disable all custom admin notices. To the awesome developers, there are methods to keep this disabled after it has been dismissed:
How to stop showing admin notice after close button has been clicked?
https://wordpress.stackexchange.com/questions/242705/how-to-stop-showing-admin-notice-after-close-button-has-been-clicked
pkI third the motion! At the very least, give us the option to dismiss the notice.
pkHi Bill,
I had time to do some more testing. There are no errors being reported so I tested logging in & out and closing the browser in several browsers; Opera (my default browser), Chrome, Firefox, IE & Edge). It turns out this behavior ONLY happens when I’m using Opera. I drilled down into the Advanced Settings for cookie management in Opera. Cookies & local data is set to be destroyed when the browser is closed – which explains why I keep seeing the ads.
What is weird is that yours is the only plugin this happens with. I have other plugins with similar ads, bit they they stay closed permanently once they have been dismissed. Not sure why.
Hopefully this information helps you as you make improvements to your excellent plugin.
Thanks again for your time.
pkThanks Bill; I will check out the troubleshooting tips. If I learn anything more about why the banners keep appearing each time I login, I will report back here.
Thanks for taking the time to reply to this support thread.
pkHi Bill,
Thanks for your quick replies. To clarify, the Dismiss button does indeed close your banner ad, and it stays closed until I do one of two things:
1) I clear my browser’s cache, or
2) I close my browser.Each time I login after having closed my browser, I have to dismiss the banner ad (every day). After a while this gets very tiresome. I suspect the dismissal is being saved in a JavaScript cookie, and the cookie is destroyed when the cache is cleared or the browser is closed. I don’t have this experience with other plugin ads; I suspect my dismissal action is being saved as a database preference in those cases.
I really like your plugin and would love to keep using it. I am bringing this to your attention because I suspect your intention is NOT to irritate potential customers (like me) but to bring attention to your commercial offerings. Unfortunately for us both, the current method IS irritating.
Thanks again for your replies – and for sharing your excellent plugin with the WP community.
pk