Support

August 31, 2016 at 2:40 pm

Hi Ruby,

The first thing to check is plugin conflicts, and it sounds like you’ve already identified some potential conflicting plugins. So the next step is verify whether those are actually conflicting or not.

September 5, 2016 at 3:28 pm

Can you check for a JavaScript error in the console when you get to the point where the modal should load, but it doesn’t?

September 7, 2016 at 4:39 am

Hi Ruby,

It looks like the problem is due to a style setup within your theme.

EE adds a class of ‘hidden’ and sets that to display: none; using CSS which hides the element, then when you click the button it uses some JavaScript to add display: block; to the element so it becomes visible.

However your theme adds an additional style to the class ‘hidden’ – http://take.ms/KjekV

It sets visibility: hidden; too.

When that is removed the login form displays – http://take.ms/rVSYC

So basically EE sets the display attribute to block but because the theme has set the visibility to hidden it remains hidden.

To fix this you can just override what the theme is doing for that specific element – http://take.ms/V1WQg

You can use this code:

.ee-admin-dialog-container.hidden {
    visibility: initial;
}

We recommend using either the My Custom CSS or Reaktiv CSS Builder plugins to add custom styles such as these.

September 7, 2016 at 5:05 am

Do you have reCAPTCHA enabled on the site?

Go to Event Espresso -> Registration Form -> Reg Form Settings

There you will find the option ‘Use reCAPTCHA’, is that set to yes?

Do you have both the Site and Secret Key setup from your reCAPTCHA account?

Either way, if its enabled temporarily disable it so I can run another test please.

September 7, 2016 at 5:14 am

What plugin are you using for reCaptcha currently?

The JS errors being thrown on the page are from reCaptcha scripts that are being added to the login form, digging a little deeper they don’t appear to be from EE.

September 7, 2016 at 6:01 am

Where is it set to No?

If you mean the setting within EE above then that is EE’s own reCaptcha module that would be included if it was set to Yes. EE loads a reCaptcha form on the registration page, like this – http://take.ms/ozIBu

EE will not allow the registration to continue if the reCaptcha is not valid in that case.

‘Login No Captcha reCAPTCHA’ is adding its own version of reCaptcha to the login forms which is completely separate from EE’s setting. In this case the script the plugin adds to the login form is throwing a JS error and breaking the login modal from EE.

I’ve just tested this locally and get the same problem with that plugin activated, I’ll check if its possible for us to work around this with a snippet, however currently you can not use that plugin with the EE4 Users add-on.

September 13, 2016 at 3:51 pm

You could try this plugin as an alternative:

https://wordpress.org/plugins/webdesignby-recaptcha/

September 16, 2016 at 2:18 pm

The Blackhole for Bad bots plugin is helpful for keeping spam bots at bay.

Since you’re also looking to better secure your site’s WordPress admin, you can do a lot better than a reCaptcha form. This includes:

For admin accounts, don’t use a username “admin”.
Use strong passwords
Secure the site with https (i.e. get a SSL certificate)

These and more suggestions can be found here:

http://www.wpbeginner.com/wp-tutorials/11-vital-tips-and-hacks-to-protect-your-wordpress-admin-area/