New Beta Version

[martinr]

I ve tested the Betaversion and the most is workoing fine. Thanks for this.

But I get an error when I want to work with customize Login Forms.

When I create a Form and embedding it with [user-meta-login form="Kundenlogin"] I get this error:

Warning: Illegal offset type in isset or empty in /www/htdocs/XXX/XXX/wp-content/plugins/user-meta/models/umSupportModel.php on line 57

Warning: Illegal offset type in isset or empty in /www/htdocs/XXX/XXX/wp-content/plugins/user-meta/models/umSupportModel.php on line 57
Fields are not found.

Is it correct to create the Form with the Default WordPress E-Mail and Password Fields? Then it seems to be an error.

• This topic was modified 10 years ago by martinr.
• This topic was modified 10 years ago by martinr.
• This topic was modified 10 years ago by martinr.

[martinr]

I tested it with [user-meta-login] and it is working.

Is there a problem with [user-meta-login form="Kundenlogin"] ??
It would be nice if you could give me an answer.

Thanks and best regards

[martinr]

Uploading Photos:

Warning: getimagesize(http://www.XXX.de/wp-content/uploads/files/Bildschirmfoto.png) [
function.getimagesize
]: failed to open stream: HTTP request failed! HTTP/1.1 401 Authorization Required in /www/htdocs/XXX/XXX/wp-content/plugins/user-meta/framework/models/PluginFrameworkWPSupport.php on line 562

[martinr]

Next question: When I use a range field. Where can I put in for example “onchange=”range.value=value”?
This is an important thing 🙁

Best regards

• This reply was modified 10 years ago by martinr.
• This reply was modified 10 years ago by martinr.
• This reply was modified 10 years ago by martinr.
• This reply was modified 10 years ago by martinr.

[martinr]

Next problem:

HTML Fields adds “/” to tag:

Example:

<div id=\”um_field_114_test\”></div>

[martinr]

After much testing, I have come to the conclusion that the beta version for me is not usable in the least. Unfortunately, because I would like to use the Range Fields.

Other errors:

Some shared fields do not change the settings when you change settings at the field the form, for example HTML.

THe whole classes are a mess, sorry;-) (which is also in the current version something is so). It would be better if User Meta Pro would make no formatting and no classes, IDs etc. applies. Or you could exhibit it. That would be cleaner code I think.

Thank you for your interest. I’ll now return the old version.

Martin

[Khaled]

Hi Martin,

Thanks a lot for your testing. I have just update dev containing fixes for your reported issues.

To add “onchange” with any field, please see following example (with new dev version)

add_filter( 'user_meta_field_config', 'addEvents', 10, 3 );
function addEvents( $field, $fieldID, $formName ){ 
    if ( $fieldID <> 'Target_Field_ID' ) return $field;
    $field['events'] = array(
        'onchange' => 'custom_js_function()'
    );
    return $field;
}

[Author]

Posts