Forum Replies Created
-
AuthorPosts
-
Anh Tran
KeymasterWe've just fixed this bug on Github. Can you please try it?
KeymasterHi @Saquib,
Sorry, I was working on some issues and didn't remember to answer 🙁
Your problem is related to this issue where the previous code add extra empty
<option>tag which allows users to clear selected option. However, it's not the default behaviour of<select>tag because<select>only shows options and force users to choose one of them. So I made the code work the same way.I suggest you switch to
select_advancedwhich has option for users to clear the selection.KeymasterYes, I'm still working on it. I will try my best to resolve this problem soon.
KeymasterThanks, @Flikweert. The video is very helpful. I will check the problem and fix it.
KeymasterHi @melfisher,
Question 1:
Can you please give me more info about:
- Do you put the Meta Box plugin into a child theme? Or in a parent theme?
- Where do you put the code to register meta boxes?Basically, if you put the Meta Box plugin into a theme (no matter a parent theme or child theme), you will lose it when the theme is updated.
So, my advice is installing the plugin as a normal WordPress plugin to get updates for both themes and plugins correctly.
Question 2:
The builder extension doesn't show the meta value in the frontend automatically. Neither do other extensions or the Meta Box plugin. You have to do that manually.
There are 2 ways to do that:
- Using
rwmb_meta()helper function as instructed here, but this is more technical and might not suitable to you.
- Using[rwmb_meta]shortcode. You can put the shortcode into the post content at the place you want to show the meta value. Please follow this documentation to know how to do it.KeymasterHi @brightcreations, I've just updated the Group extension with support for cloning sub-fields in a group. There is still 1 thing that doesn't work: either the group or sub-field is not cloneable, e.g. if both the group and sub-field are cloneable - the code won't work.
More details:
- If group & sub-fields are not cloneable - WORKS
- If group is cloneable & sub-fields are not cloneable - WORKS
- If group is not clonable & sub-fields are cloneable - WORKS
- If group is cloneabe & sub-fields are cloneable - NOT WORKSPlease update the extension and try. Thanks.
KeymasterHi Saroj, please read this thread for the information. Thanks a lot.
KeymasterI haven't resolved the problem with JavaScript yet. Please wait. It's harder than I thought.
KeymasterMaybe, I'm not sure cause it works for me. Can you post your code here?
KeymasterHi, you can use the function wp_get_attachment_image_url like this:
foreach ($image as $img ) { $img = wp_get_attachment_image_url( $img, 'full' ); echo $img; }Change
fullto another image size if you don't want full size.April 28, 2016 at 10:34 PM in reply to: Lots of images in an image_advanced can wipe all images in that field on save #2956KeymasterHi Sam, thanks for describe the problem in details :). It helps a lot.
I think you're right about the problem: when images are not loaded, there are no inputs for images which stores image IDs, so when push the Update button, empty field is submitted and thus, no images are saved.
I will think more about your solution and make a fix for that.
KeymasterJust checked the problem and it seems to work for me: http://prntscr.com/axxtl4
Can you post your code so I can check more carefully?
KeymasterI will do that in a couple of days. Thanks!
KeymasterHi @weseo, thanks for your suggestion. I've just added that to version 1.1.1. Enjoy!
KeymasterHi again, I've just tested with the latest version on Github and it seems to work. Can you please try the Github version?
-
AuthorPosts