Forum Replies Created
-
AuthorPosts
-
Anh Tran
KeymasterHi,
The problem is the plugin doesn't handle very well the case when a field's ID contains another field's ID. In this case the ID of the input contains the ID of the radio field. The plugin make some guests to find the correct elements. And in this case, it gets the wrong elements 🙁
To prevent this bug, please set the IDs so no one contains another.
KeymasterHi Jason,
Any reason for using the validation library for custom rules? Because the plugin already has it in the core. And you can just set the rules and messages.
KeymasterHi Marcel, unfortunately it's not possible for now. I'm thinking a better way to enter options for the fields in the Builder. Probably via a textarea instead of many label/value pairs as it is now.
Update: a new way to enter options is available. Please update the Builder and take a look at this instruction video:
KeymasterHi Marcel,
Unfortunately, it's not possible at the moment. The builder supports export and import for meta boxes created by the plugin only.
KeymasterHi Marcel,
Please send me the link via Contact page.
The tabs is showing means the form is rendered. It might be an issue with settings of the meta boxes.
KeymasterHi Marco,
The case an email exists is checked by the plugin and it will return an error message "Your email already exists" if it fails. Currently, there's no filter to change that message.
KeymasterHi,
After debugging your code, I found that it's an edge case where the plugin cannot get the correct value of the radio. The problem is when the plugin tries to get the radio inputs, it gets the number input as well. This is because the ID of the number field contains the id of the radio field.
In this case, please change the id of the number field and the bug will go away.
KeymasterHi,
We actually don't block any feature. The code you see it the code for backward compatibility. Back in the history, a year ago (Meta Box 4.12), we created an abstraction layer for storage. This layer allows us to interact with many storage in WP easier, such as term meta, user meta, settings and custom table. Without it, we had to created many filters just for saving and getting the values.
Since then, we have updated all the extensions to use this feature, including Group and Term Meta. I'd suggest you update the group extension to the latest version 1.2.16. What you're having is 1.1.5, which behind 18 versions. And Meta Box core plugin is now 4.15, 3 minor versions have been released.
Update: I found a quick and dirty fix for MB Term Meta that makes it works with old version of Group. Please update to version 1.2.3.
KeymasterHi, I've fixed this bug in the latest version. Please update.
Thanks
August 1, 2018 at 2:28 PM in reply to: shortcode does not accept all wp_login_form parameters #10823KeymasterHi Kevin,
I've just updated the plugin. Now it supports all parameters from
wp_login_form. Please update and check out the documentation.KeymasterHi David, I received it. I'll answer you soon.
KeymasterPlease go to Dashboards -> Updates and check for updates. You'll see AIO available. Just update it as normal plugins.
Regarding the settings pages, there's no menu item for it. The screenshot shows the Meta Box menu correctly.
KeymasterHi,
That action doesn't fire for login form, because the form doesn't need to create or update user info.
The login form users WordPress's function
wpsignonto log user in. And it auto checks the email address. I wonder the use case that you manually check for email exists. Is that really needed?KeymasterCan you please try again? The update for AIO comes a little bit later.
KeymasterHello,
Did you set the correct
idattribute for the form shortcode? -
AuthorPosts