Hi, we tried Dam Spam but the black background and small text was too difficult for my client to work with. Plus it has the same issue as Stop Spammers that drove me to try Dam Spam, which is this: I click the thumbs up to allow the request. The IP address now appears in the allowed area, but the request persists when going back to the request page. Also, if there are three requests, and I click the thumbs up on one of them, all three get acted on. They stay on the request screen like I never did anything. The most troubling of this is clicking on one, and all the requests get approved.
“we have previously acknowledged an issue within this option where the customizations saved as drafts are getting reflected in the live emails. “
This is exactly what happened, as I looked in our mail log, which does not lie, and the prebuilt template was used in three outgoing emails. I did save the draft because I’d made numerous changes to the template. I am feeling slightly less lazy today and uploaded the screenshot of one of the live emails that went out:
You said this was previously acknowledged this issue. I saw nothing in the interface warning of this issue. I searched the forum for this issue and found nothing, which is why I started a new thread. I’m not one to start very many threads on here. While I appreciate the response, you indicate that it will be fixed in a future release, meaning it is not yet fixed. I’m under a time crunch to get these modifications live by today Jan 31, 2024, so I cannot wait around for the fix and risk more order and account notifications going out while I customize. These emails created some overhead for their company to follow up with the customers that are being provided ‘coupons’ that don’t exist. As I stated before I was enjoying the plugin and it was not hard to modify the header image. If you’re curious at I am trying Yaymail (testing first on a dev site – lesson learned), which seems to work better and has a clear toggle switch for when the email is active or not. I think their interface is also slightly more user-friendly.
I’ll refrain from leaving a review since you say it is being worked on. Not all of us have the gift of time on our side. I’ve used WebToffee plugins in the past without any issues. Good luck!
Greetings, I reinstalled to demonstrate that it crashes when I try to add the product to the cart. These image will delete after one month. I edited to remove the database directory paths.
Also, should this work and not crash: This display doesn’t show the ranges. Ideally I would need it to say 10-19: 10% 20-29: 15% 30-35: 20% Case of 36: 25% I don’t see option for a range in the product settings.
This is from the debug.log. I removed the full path in the text below. The only statements in there re. discount plugin are notices. I could send the whole log privately with instructions.
[14-Sep-2023 18:01:06 UTC] PHP Notice: Undefined index: plus_discount in /wp-content/plugins/woocommerce/includes/react-admin/connect-existing-pages.php on line 91 [14-Sep-2023 18:01:07 UTC] PHP Notice: Undefined index: plus_discount in /wp-content/plugins/woocommerce/includes/react-admin/connect-existing-pages.php on line 91
Greetings, thanks for your suggestions. I don’t have access to the client’s FB store, and I cannot change the theme or deactivate plugins on a very active live site, and I don’t think I can ‘sync’ a dev site nor would I want to, to a live FB store. So my ability to test for conflicts is limited, unless you have a way around that I’m not thinking of. I’ve asked the client to look into the FB business manager and check the settings.
Well this is odd – I’m not able to replicate the error! I’m so sorry. I tried – the error it gave had something to do with roles; once I unchecked the default role in the import interface, the import worked.
I got feedback that the issue was with an update 1.6.2 that it will void subscription payments if no payment method is saved and will likely be fixed in their next update. Now to look for an older version of the plugin.
Thanks for your reply. I did include the **password** tag in the email, but if you don’t click the box to allow the password reset, it doesn’t include the password in the email. I didn’t know this ahead of time, and wish I had. I know it’s not an error, it was more not being aware of the logic involved in storing passwords.
The import has an option to include a default role. If I had any role selected, the import failed. Perhaps because I had a role defined in the spreadsheet? No big deal, once I figured out that deselecting the default role made it work.
Thanks for working on a solution for the issues with importing/hosting.
