Thank you for your reply.

However, your response is not adequate given the seriousness of the issue that was reported.

The problem I described is not a general bot protection matter. It appears to be a flaw in the way your plugin handles account creation and/or validation. If a plugin allows attackers to bypass WordPress settings and create accounts, that is a defect in the plugin’s logic. It is not acceptable to shift responsibility to users by instructing them to deploy Cloudflare, Wordfence, or reCAPTCHA as compensating controls.

Security controls such as firewalls and CAPTCHA are defense-in-depth measures. They are not substitutes for correct server-side validation and adherence to WordPress core security mechanisms. A plugin must function securely in a standard WordPress environment without requiring users to re-architect their network, introduce third-party services, or alter user experience flows to compensate for insecure code paths.

Recommending Cloudflare and Wordfence does not address the root cause. It avoids the core issue: your plugin is bypassing expected WordPress restrictions and enabling unauthorized account creation.

If the plugin modifies or overrides WordPress registration logic, that logic must include proper nonce validation, capability checks, and server-side enforcement of the site’s registration settings. Anything less is a security vulnerability.

I am asking you to:

• Acknowledge whether the behavior described is reproducible.
• Confirm whether the plugin bypasses native WordPress registration restrictions.
• Clarify whether a patch will be issued to correct this behavior.

This is a security concern, not a configuration preference. It should be handled as such.

I look forward to your technical response.

Yes, that works. Thanks!

Hi, I tried all the CSS mentioned above but the top header menu I see on my desktop site still doesn’t appear on mobile. The URL is http://a-sk.com/en. What am I missing?

Hi,

I don’t mean to drag this on, but I just want to clarify one point. I’m not bothered about what’s in the code, but rather what it says in the UI when editing a page. It says, “Note: The settings from this box only work if you do not use visual composer on this template. The template detects if visual composer is used and it removes the title and sidebars if that’s the case.”

However, that didn’t seem to be the case, which is what sent me to go looking in the code. As I said, for a person who’s just starting out, I think there’s enough stuff to figure out without the confusion over this.

Thanks for the response. The theme is loaded with features, but that also makes it very complicated and confusing to newcomers. It would be great if this were cleaned up, at least in the UI, so that it will be less confusing.

Hi, I’m having the same issue, I too have a child theme. Glad to hear that you were able to solve it, there’s hope for me as well. Can you explain what you mean by “reset on WordPress build”?

Hi,

I’m trying to do the same thing. Where did you place this code?

I think that maybe you checked it while I was testing some more. It looks fine when I set the Template in Page Attributes to Pagebuilder + pagetitle, but the issue is when I use the Default template. I don’t want a page title on my home page. Check now, I’m not fiddling with it.