We use Webnus Modern Events Calendar (https://webnus.net/dox/modern-events-calendar/)
After a booking is made in MEC, a WP user is created for the participant using the email provided. However, many bookings are stored in the database that do not relate to a specific WP user and all have ID’s of 0.
This causes the participant’s email to be uncorrelated by MEC, resulting in notifications not being sent and email placeholders not showing the information correctly.
We discovered that disabling Wordfence solves this issue. Is there a setting that would block this functionality? Is there anyone that can assist us so we can use Wordfence moving forward?
Thanks
Matt
]]>They seem to be realted to Telegram because all the users are like this: 102 785 RYB SBERBANK telegram – @sibbnk
There is some variation on the usernames but is always that pattern. I have deleted all those users and changed the passwords for all my admin accounts but they keep getting created. Just during this night, 15 more admins were created.
I have updated all plugins and WordPress, I have the Wordfence plugin active and it doesn’t show anything out of the ordinary. I’ve looked in apaches error and access logs but I don’t see anything either.
Can someone help, please.
]]>In this setup, SuperSiteEditors can create SiteEditors and SuperSiteEditors, but not Administrators, which makes sense. However, I’ve found that a SuperSiteEditor can delete an Administrator account, which seems REALLY wrong. That’s definitely not what I want, and I’m having trouble understanding why it would be the case. Am I confused about something, or have I screwed something up? Bottom line: Can I set up my site so SuperSiteEditors can delete SiteEditors but not Administrators (and, I guess while I’m at it, not other SuperSiteEditors)? Thanks!
]]>Problem is everything just retuns empty. What I can get is the userid or email. It seems like this mail is sent before the other information is saved?
If it makes any difference, I create the user via the WooCommerce REST API.
Hope someone can help, I am really at a loss with this one.
Thank you!
]]>Currently I’ve accomplished this by commenting out parts of the create_user() function, but this practice does throw some errors and may cause some issues that I haven’t come across or troubleshot yet. Just wondering if there’s something I’m missing in the developer hooks that would accommodate this. Thanks.
]]>Thank you!
]]>