Arnan
Forum Replies Created
-
Forum: Plugins
In reply to: [AdRotate Banner Manager] ID” on null in adrotate-output.php on line 378But the error is relevant for the Post Injection feature, not for widgets.
Widgets use different code/functions to load ads.On the page you’re testing on, are there ads between or near paragraphs that are placed with Post Injection?
If not, then please re-check the exact error and let me know.Forum: Plugins
In reply to: [Payment Gateway of Stripe for WooCommerce] Payment FailedI have this too, version 4.0.4.
I think it worked fine on earlier versions.Forum: Plugins
In reply to: [AdRotate Banner Manager] ID” on null in adrotate-output.php on line 378I can’t reproduce the warning anywhere, with or without stats.
What kind of post are you loading that triggers it?
Is it some kind of custom post type? A blog post? Page? Or…Forum: Plugins
In reply to: [AdRotate Banner Manager] ID” on null in adrotate-output.php on line 378Can you check with the current version of AdRotate Banner Manager if the warning still pops up, and which line it’s at? 378 is no longer accurate I think.
It’s probably 379 now.
Forum: Plugins
In reply to: [AdRotate Banner Manager] ID” on null in adrotate-output.php on line 378Hmm, I’ll look into that.
Forum: Plugins
In reply to: [AdRotate Banner Manager] Can’t create new adsAha. So the Javascript is missing or not loaded.
Make sure you do not have an adblocker active that blocks the AdRotate assets.
You may have to clear the browser cache after disabling the adblocker.Or, if you use some kind of minimizer or cache on your website that also works on the dashboard, make sure it includes all Javascripts, or make it exclude Javascript so that the missing code is loaded as was originally intended.
Forum: Plugins
In reply to: [AdRotate Banner Manager] Can’t create new adsJust because one of the examples does not work does not mean you can not create adverts.
You can simply type in the AdCode field, or copy other text into it.For the examples to work you need a little piece of Javascript. This is of-course loaded/included with the plugin.
If something doesn’t work about it it’ll give errors in your browser inspector and such an error should become visible right after you click the example you want to use.So please check what that error is by taking a look at your Browser Inspector.
Errors can usually be found in the ‘Console’ tab.Yes that for sure would be easier from a troubleshooting pov 🙂
Let’s rule out a few things.
– It used to work.
– Issues likely started after doing updates.
– Yesterday on my plain WooCommerce setup It worked fine for 4 tests all created a new account without issue, while blocking the account until I met all requirements.
– You’ve changed one setting for usernames in WooCommerce which changed the login behavior.
– The current error is related to a background check for bots.To me this means that WooCommerce has changed something without you knowing.
It also means that your settings in No-Bot are probably fine, assuming you didn’t change anything.Since No-Bot does not talk to other plugins other than WooCommerce it seems unlikely to me that there is some kind of conflict (with other security plugins for example).
Since you’re now stuck on a bot protection feature related to the form fields it might be an autofill issue (From another plugin or your browser. Though either sounds unlikely) or something is wrong with the security questions you set up (More common if things go wrong).
Maybe simply re-saving the security questions helps. If the plugin gets stuck on that, mismatching the answers, resaving it with the correct data should fix that.
Of-course make sure the questions have the answers you want.Then the plugin thinks you’re a bot.
This can happen if you enter something in a hidden login field, this field should stay empty. Bots don’t know that, so they auto-fill every field they find and thus fail the checks.
Or if the security questions you set up do not match the possible answers, another thing bots often screw up and thus fail another check.My guess would be that something is wrong with the security question you set up.
I just did some tests and it seems to work fine for me on WP 6.7.1 and WC 9.5.1.
Make sure you’re not allowing the username to be an email address as that defeats the ‘disallow email as username’ setting in my plugin.
The email for username setting is warned about in the No-Bot settings.You’ll find this in WC > Settings > Accounts & Privacy, under the ‘account creation options’.
Hmm 🤔
Which version of WordPress/ClassicPress and WooCommerce do you have?Thanks for your kind words.
Not sure what you mean with consolidating info, which info do you mean? – If you have suggestions for improvement please send your ideas through https://ajdg.solutions/contact/. Thanks!
Does it work if you enable the WooCommerce protection?
Forum: Plugins
In reply to: [AdRotate Banner Manager] AdRotate 5.13.6 breaks the post contentI think I found it, some forgotten debug code.
5.13.6.1 Fixes that.Forum: Plugins
In reply to: [AdRotate Banner Manager] AdRotate 5.13.6 breaks the post contentHow do you place the adverts? With a widget? Shortcode?
What kind of advert are you seeing this with?Do you have a screenshot or some example so I know what to look for?