iheggaton

Not at this stage. I’ll revert my staging environment to the state that it was breaking. And perform some tests.

One thing that may help is I’ve now got 2 sites and both are running Elementor.

Hello?

Deleted

Hi, I too am getting 404’s on CSS. It appears that the site is generating a new minified CSS file but the cache isn’t aware of the file creation; still references the old minified CSS file and this results in a 404.

I’ve not confirmed it yet as I don’t keep track of what filenames are being created but that’s my best guess.

I’ve been trying any number of settings changes but nothing is working so far.

• This reply was modified 3 years, 6 months ago by iheggaton.

This has recently started happening for us too. We also have page caching. Looks to be the issue.

Unfortunately, we have a form at the bottom of every page. Sigh…

@wpexpertssupportteam Thanks heaps for that! It’s working again ????

100% this is bad! I can’t search my users with this plugin enabled. I’ve got hundreds of users.

Every (admin based) user search results in a search containing the following search query attached to a 302 redirect:
[email protected]&new_user_approve_filter-top=view_all&ure_add_role&ure_revoke_role&primary_role=api_user&paged=1&new_user_approve_filter-bottom=view_all&ure_add_role_2&ure_revoke_role_2

Please fix it asap!

Ditto. And based on the report, it’s not a false alarm. Attached to the report is a proof of concept video showing the issue in action.

Thanks Danny, yeah, I decided to fix the issue rather than just whinge about it ??

Thanks again mate!

Apparently, WordPress changed how the errors are accessed and made the member arrays private. As such, what used to work in removing the username error doesn’t any more.

However, there is a hack I came up with – plugin code editing required:
Edit the plugin file rpr-login.php
Find the line (Line 374?):

if ( is_array( $errors->errors ) && isset( errors->errors['empty_username'] ) ) unset( $errors->errors['empty_username'] );

Add below it with:

if ( is_array( $errors->errors ) && isset( $errors->errors['empty_username'] ) ) {
					$temp = $errors->errors;
					unset( $temp['empty_username'] );
					$errors->errors = $temp;
				}

It’s a hacky way to fix the issue. It may not work properly under all circumstances.

I’ve also discovered that after account verification, no further emails appear to be sent – such as a successful registration or email containig the password.

Use at your own risk!