Forum Replies Created
-
AuthorPosts
-
April 9, 2018 at 11:39 AM in reply to: cloneable oEmbed fields doesn't save empty data as "NULL" #9126
Anh Tran
KeymasterHi,
When a field is cloneable, the value should be always an array. That's why the plugin stores value as
a:0:{}- the serialized of empty array.I'll add more options to the MB Builder extension.
KeymasterIt's the MB Builder extension. I've just updated the Meta Box AIO as well 🙂
KeymasterI've just updated the plugin, making a drop-zone for sub-fields of groups, so you can drag and drop sub-fields easier (and make things obvious).
Please update the plugin.
KeymasterHi,
I've made a video to demonstrate how to create child fields for groups with the Builder extension:
Please take a look. After doing that, the code will be available in the Code export tab.
Update: I've just updated the plugin, making a drop-zone for sub-fields of groups, so you can drag and drop sub-fields easier.
KeymasterIf you're using the
image_advancedin the frontend, it will include the scripts to trigger the media modal when you click on the image.In other cases, I'm not sure how to display the media modal alone :(.
KeymasterI got it.
I think in this situation, the best solution is using
postfield. It works the similar way and works well with groups.Technically, because it's inside groups, the data will be saved in groups. So it can't be saved in the relationship table (where the relationships are saved).
KeymasterDo you mean copy the code generated by the MB Builder?
If the code is not for user profile, settings page or taxonomies, then you can just copy it and deactivate the builder extension. It will work.
If the code is for user profile, settings page or taxonomies, you'll need the corresponding plugin activated (MB User Meta, MB Settings Pages, MB Term Meta). The builder extension then can be deactivated.
In either cases, you still need to keep Meta Box activated.
KeymasterOops, there was a bug in the new added filter in the 4.14.4 version. I've just fixed and pushed a new version. Please update.
Sorry for this 🙁
KeymasterHello,
I'm checking the problem. Looks like there's a bug with pulling the data. I'll check and fix it now.
Update: There was a bug in the Meta Box plugin that cause the bug in MB Frontend Submission. I've just updated the plugin to version 4.14.4 to fix this. Please update Meta Box.
KeymasterHi,
Can you give more details of the problem? Which objects do you want to build relationship between?
KeymasterHi,
There are some plugins that hide admin menus, which should work in this situation:
https://wordpress.org/plugins/admin-menu-editor/
https://wordpress.org/plugins/adminimize/
https://codecanyon.net/item/wordpress-hide-admin-menu-plugin/290744 (my plugin)KeymasterHi Hazmi,
The "image_size" param is there to make sure the images are not blurry. It's not meant to display images with exact width and height. Actually, the style for images mimics the Media Library, that's why you see it 284x284 square.
KeymasterAh, I see.
The storage is an abstract layer between the data and custom fields. With the implementation in the Meta Box plugin, we can create a custom storage to decide where to save data. As you can see, we have implemented storages for post/term/user/comment meta, settings pages (option) and custom table.
In that thread, @Jackky wants to create a custom storage for a custom table, which has a different structure than the one provided by the MB Custom Table extension. That's why I instructed him to create a custom storage for his custom table.
Hope that make things clearer 🙂
KeymasterHi,
Because of some limitation in the media modal, only simple fields such as text, select, radio, checkbox work. Other fields, including the color field, that require custom JS don't work, unfortunately.
KeymasterHi, I'm not really clear about the situation. Can you please take a screenshot, upload it on imgur.com and paste the link here?
-
AuthorPosts