itestense

Yes, now it’s ok! Thank you.

Me too. It makes a lot of problems with Divi Theme. Looks like $url becomes null.

I confirm the patch DOESN’T work.

However the hint bt @midladnauctions was very useful.

Code around line 3893 in includes/functions-ur-core.php is very bad. It should be:

if(!array_key_exists('urcl_hide_fields', $_POST)){
    return $valid_form_data;
}
$hidden_field = $_POST['urcl_hide_fields'];

if ( empty( $hidden_field ) ) {
    return $valid_form_data;
}
// etc. etc.

Now it works. I hope the author will patch this file soon.

I found the “fix” in the FAQ. Does the line

if ( !isset( $_COOKIE[‘euCookie’] ) ){ return; }

cause trouble to anyone?

• This reply was modified 4 years, 11 months ago by itestense.

I also sent you an email with further details.

Paolo

WP version: 5.3
PHP version: 7.1.29 (and also 7.0.33)
EM version: 5.9.7.1

I think I have the solution. The problem occurs when the URL of your editing form has the querystring “action=”. In my case it’s “action=edit”.

The prolem happens because the form sets the “action” attribute without resetting the querystring completely AND it contains an hidden input having name=”action” and value “event_save”.

The form action is set this way (file templates/forms/event-editor.php line 26):
action="<?php echo esc_url(add_query_arg(array('success'=>null))); ?>"

The new WordPress checks if GET and POST inputs match and, in case of mismatch, it throws the error.

So the form posts to an URL ending with ?action=edit but it also contains the “action” input set to event_save, so WordPress stops the procedure for security reasons.

If you edit (waiting for the fix) the file templates/forms/event-editor.php at line 26 and change the action value to:

action="<?php echo esc_url(add_query_arg(array('success'=>null,'action'=>null))); ?>"

you make it work!

• This reply was modified 5 years, 3 months ago by itestense.
• This reply was modified 5 years, 3 months ago by itestense. Reason: line numbers