Benedict Popelar
Forum Replies Created
-
Forum: Plugins
In reply to: [Woo Manage Fraud Orders] Can’t easily remove user from blacklistHi Emma,
My customer was able to successfully submit an order. In summary, to recover from a legitimate customer who gets blacklisted you must:
- Remove the customer’s information (name, phone number, email address, IP address, billing / shipping address) from the blacklists located at WooCommerce -> Settings -> WMFO
- Remove the customer’s related entries from the WMFO -> Fraud Attempt Logs
- I’m not certain this was strictly necessary, but I also removed the customer’s related entries from the WMFO -> Blocked Logs
Ben
Forum: Plugins
In reply to: [Woo Manage Fraud Orders] Can’t easily remove user from blacklistHi Emma,
I have been having the same issue with a legitimate customer who got blacklisted due to a typo in their billing address. Removing the customers information from the various blacklists did not allow the customer to successfully complete a transaction. I believe this is due to the history of failed attempts by the customer contained in the WFMO -> Fraud Attempts Logs.
I have removed the customer from the blacklists and have also cleaned up the Fraud Attempts Logs. I have asked the customer to attempt another transaction to see if this truly cleans up the blocking conditions. I let you know if it works.
Ben
I went back and switched to defining the style inline with <style> tags after the conditional block code and it is working as you described.
Although the inline style tags have a slightly higher precedent than the stylesheets defined before it (sorry the brain is a little foggy – order matters), the slightly highed precedent shouldn’t matter; however, it appears to make a difference as the jQuery function $.show() is clearly deciding to add the display:block style to the HTML element when the stylesheet approach is used (but not when the inline style tag approach is used).
Not sure why that is the case, but thanks for the help!
Ben
No it won’t.
The styles defined as HTML attributes have a higher precedent than any other styles (defined either inline between <style> tags or included in a stylesheet). The only way to override the HTML style attributes is to add the !important modifier to the lower priority style definitions. Doing so forces the display attribute to always defined as flex and consequently the toggling of the display attribute by the js has no effect (and the conditional fields are always displayed).
Hi Jules,
Thank you for your timely response.
I’ve tried your suggestion (added it to the stylesheet) and it does not override the inline HTML style statement that the js uses to toggles the display mode between none and block mode.
The display of the “Physical Location:…” block of fields (located in the middle of section 4 of the form) is controlled by the “Group is Meeting” radio buttons in section 3 of the form below:
https://www.scws-al-anon.org/new-al-anon-group-registration-form/
Ben
- This reply was modified 3 years, 4 months ago by Benedict Popelar.