Forum Replies Created
-
AuthorPosts
-
Peter
ModeratorHello Jacob,
Thank you for your feedback.
I've forwarded this ticket to the development team to consider adding it to the to-do list for the future development of the plugin.
January 23, 2025 at 12:29 AM in reply to: Critical error after custom fields set to display on custom post type #47514ModeratorHello John,
Thank you for your feedback. I can reproduce the issue on my demo site and it looks related to PHP 8.0 or later version. You can try to downgrade PHP to 7.4 and recheck the issue.
ModeratorHello Tanja,
Please share your site admin account by submitting this contact form https://metabox.io/contact/
I will take a look.ModeratorHello Jordan,
Supporting the custom plugin or custom code is beyond our scope of support. Please read more about our support policy here https://support.metabox.io/topic/support-policy/
You can contact an expert developer and ask them to check the 302 redirection for you when using Meta Box. Besides that, we offer a customization service with an extra fee. If you are interested in this service, please contact us here https://metabox.io/contact/
ModeratorHello,
So if you use the frontend submission shortcode, does the warning message
Warning : Undefined array key "label_title" in ...still display?Regarding the post draft, it is the post status. The post will be saved to the status (draft, publish, private ...) which is set by the shortcode attribute
post_status. Please follow the documentation to get more details https://docs.metabox.io/extensions/mb-frontend-submission/#adding-the-submission-formModeratorHello,
The callback function requires to have a return state and value to display the message in the correct position (field appearance). So it is a solution and good to go.
ModeratorHello,
As I mentioned above, the frontend form doesn't have any limitations or restrictions. You can use the action hook
rwmb_frontend_before_processto add your condition before processing the form. Please follow the documentation to get more details https://docs.metabox.io/extensions/mb-frontend-submission/#form-hooksModeratorHello Nick,
I don't see it takes the default WordPress post ID instead of the custom model ID. However, if somehow the first custom model entry ID 1 was deleted, the ID will start from 2 and so on. The WordPress post ID also works like that.
You can create a new post, delete it and create another post to see how the ID is generated.January 22, 2025 at 10:06 PM in reply to: Adjusting Width of Admin Filter and Translating Text in Relation Field #47500ModeratorHello,
Currently, only text in the English language will be displayed. I will inform the development team to improve this feature in future updates.
Thank you.
ModeratorHello Nick,
It looks like the ID 1 was deleted in the database. I test to create the first entry of the custom model, the ID is started from 1 as well. But if I delete the entry in the database and submit a new entry, it will start from 2 as it is.
I'm discussing this case with the development team and get back to you later.January 21, 2025 at 12:46 PM in reply to: ℹ️empy first array value for cloneable group when using rwmb_frontend_validate #47483ModeratorIf you open the Console tab and check the HTML elements, you can see the first entry is the template that will be used for other clone entries. Screenshot https://imgur.com/CwZGTSs
ModeratorHello Michele,
Please try to contact us via this email [email protected], I will help you check the issue.
ModeratorHello Julian,
Thanks for reaching out.
I'm afraid that Meta Box doesn't support an option to validate that the end date is after the start date or any specific case. You can create your own Javascript code to validate the input date, refer to this topic https://stackoverflow.com/questions/68092463/notify-when-the-end-date-is-earlier-than-start-date
ModeratorHello Tanja,
Thank you for your feedback.
I've escalated this issue to the development team to check the warning message when using the Bricks element and frontend form. Meanwhile, you can try to use the frontend form shortcode and remove the title, content from
post_fieldsattribute. Following the documentation
https://docs.metabox.io/extensions/mb-frontend-submission/#adding-the-submission-formJanuary 20, 2025 at 11:07 PM in reply to: ✅'Switch' Element Cannot be Defaulted to "On" within MB Group "Clones" #47473ModeratorHello,
If you want to show the ON switch as the default value for the cloneable entry, please enable the setting "Clone default value" for the group field. Please read more about the cloneable feature in the documentation https://docs.metabox.io/cloning-fields/
and check this screen record https://imgur.com/vO3SxT6 -
AuthorPosts