gamepres
Forum Replies Created
-
All right, I was in a hurry with this problem so I hired a hourly dev to fix it during the night.
We found together that the code for the Password Reset page was already taking in account WPML, but for some reasons the option was not added.
So here’s my simple fix (has to be added to um-admin-actions.php in “@add option for WPML section”):<h4><?php _e(‘This is a translation of UM password reset?’,’ultimate-member’); ?></h4>
<p>
<span><?php $instance->ui_on_off( ‘_um_wpml_password-reset’, 0 ); ?></span>
</p>It is important to not change “_um_wpml_password-reset” for this to work.
I hope it helps other people who face the same issue, and it’s fixed in a future version of Ultimate Member.
Any chance to get support with this issue?
Forum: Plugins
In reply to: [Contact Form 7] Hidden field and validation errorThank you for your kind feedback. Following your advice, I’m trying to hide the email field using CSS.
But I am still a bit confused, as I thought the [hidden] tag were useful to hide fields from the user.
May I ask a very simple question?
If the field is hidden, how can the user can still modify the value while using the form?
Thank you in advance.This is quite a critical problem. I’ve installed Ultimate Member and started to use it all over my site, just to discover people who doesn’t read Japanese cannot reset their password.
I’m thinking about using Ultimate Member with WooCommerce, so any feedback or support is welcome.
Thank you.Forum: Plugins
In reply to: [Contact Form 7] Hidden field and validation errorWhat if the “subscribers_only: true” is activated?
Maybe this would be a good compromise to say there’s no need to show an error when using default:user_mail as the reply mail?
What do you think?Forum: Plugins
In reply to: [Contact Form 7] Hidden field and validation errorThank you for your quick reply.
In case the field is [hidden your-email default:user_email], the field is not visible and the email address is always the visitor’s registered email address.
So I feel using the default:user_mail should be treated as a legitimate and unmodified field.