[jellycode]

Worked perfectly. Thanks.

[jellycode]

I’m still waiting for an answer from the support team, meanwhile I had to change all fields to text fields, so it won’t validate them as integers, phone numbers, emails, etc..

[jellycode]

Found the solution on the following link, from another user: http://user-meta.com/forums/topic/fields-required-on-front-end-but-not-back-end/

• This reply was modified 11 years, 3 months ago by jellycode.
• This reply was modified 11 years, 3 months ago by jellycode.

[jellycode]

This is an excellent answer to this problem and exactly what I was looking for.
Like the OP, I think it would be great if this code was implemented as a built-in feature.

[jellycode]

Since I got no response from the support, I made a hack.
The plugin still doesn’t support a default value, so I injected my HTML default value (a table) using jQuery.

This is working for my current project, but it’s not the best way. User Meta Pro team should check this bug for next release.

[jellycode]

My console presents no errors, I don’t believe this is a js conflict.

[jellycode]

That works perfectly, I will wait for the next version and in the mean time I will use the dev version.
However, the default value for the rich text field still doesn’t work.

Thank you for your support.

• This reply was modified 11 years, 3 months ago by jellycode.

[jellycode]

I’m also interested is this answer.

[Author]

Posts