Forum Replies Created
-
AuthorPosts
-
Anh Tran
KeymasterI've just fixed the docs link. There was a problem with my HTTPS setup.
Just curious, how do you create custom fields? Do you create with the WP-Types plugin?
November 16, 2017 at 5:30 PM in reply to: Post field as checkbox list select_all_none or std do not work #7416KeymasterHi, let me check the code and will fix it soon.
Edit: Just fixed it on Github. Will release new version soon.
Edit 2: New version 4.12.5 has been released. Please update.November 16, 2017 at 12:22 PM in reply to: ✅I can't get FIX Patch update cause my licence is already expired #7410KeymasterHi,
I understand your point and agree with you. However, there are 2 things that we should consider:
1. The extension was released after you purchased the bundle, and it's quite new. We didn't intentionally want to sell buggy extensions.
2. There are sometimes bugs in the extensions and we're trying to fix as fast as possible. This bug was fixed just 1 day after it's reported and Florian (who reported it) was happy with the progress.This fatal bug also relates to the new change of Meta Box plugin. We created a new mechanism (called storage) to handle saving data, which helps reducing a lot of code for term/settings/user meta extension. Unfortunately, the frontend extension didn't use that mechanism at first and we had to update it in version 1.0.3.
If you want to fix the extension work, just add this single line to the file
class-mb-frontend-post.php.Thanks and best regards,
AnhKeymasterHi Bonnie,
The syntax to add fields to existing custom post type is nothing different from new custom post type. In the meta box settings, just add
'post_types' => array( 'your_post_type' ). Please check this docs for more info.Please note that if the fields already exist, then there's no way to track their previous values. The extension can track values from now on.
November 15, 2017 at 10:29 PM in reply to: ✅I can't get FIX Patch update cause my licence is already expired #7400KeymasterHi, this bug was reported and fixed. Please renew your license to get the update.
Thanks,
AnhKeymasterHi,
Sorry for late reply. I had a personal problem yesterday and couldn't be online.
I've just read your reply and I think
max_input_varsmakes sense. It's the PHP configuration, which limits the number of variables submitted via$_POST. By default, this number is set to 1000. If you have a lot of groups (clones), with many fields inside each clone, the total variables might be greater than 1000. Also note that the number of variables includes WordPress variables (title, categories, post status, etc.).This is a good discussion on StackOverflow about this problem. I think, rewrite the code to reduce number of fields / inputs is a good way to get rid of this issue. Or you can try increasing the
max_input_vars.November 13, 2017 at 11:09 AM in reply to: Cloneable group inheriting values from previous group #7370KeymasterHi again,
I've just tried your code and it works properly. Have you tried the latest code on Github? (not on wordpress.org cause I haven't released new version yet)
KeymasterHi again,
I tried to add images to this post and it still works. Looks like you set up
max_clone. Do you see any error on that page?KeymasterHi,
I'm not sure if you want to talk about "terms" or "taxonomies". I think it's "terms". So:
1. To select multiple terms, just set
multiplesetting totruefor thetaxonomyfield.
2. Unfortunately the UI for creating new terms are not available. The field only allows users to select existing ones.Best regards,
AnhKeymasterHi Florian,
I've just updated both MB Frontend Submission (version 1.1.1) and Meta Box (on Github) to make the post thumbnail deletable. Can you please try them?
The old technique is removing files via ajax, which is not doable in the frontend. The new version of
filefield uses simple hidden input field to store value, and makes it deleteable. It also allows us to clonefilefield if needed.Please just try and let me know the result.
Thanks,
AnhKeymasterCan you please take a screenshot?
KeymasterHi Saqib,
Does it not work with a simple WordPress installation? Have you checked the meta box is hidden in the "Screen" options tab (on the top right)?
November 9, 2017 at 5:39 PM in reply to: Cloneable group inheriting values from previous group #7344KeymasterCan you please post your code here? I tried with some configurations and they worked. Probably I missed something.
KeymasterHi again,
I've just checked the code and looks like the problem comes from the field ID. For cloning fields, we add suffix "_1", "_2" to the ID of new clones. In this situation, your fields have exactly the same pattern ("inhalt_1") and that breaks the naming of new clones. Please just change the field ID to something else, without the suffix "_x" and it will work.
PS: I understand that might be something unusual, but we have to have a way to make ID unique.
KeymasterHi,
Sorry to miss your topic. I'm checking it. It should have done before as we already targeted this issue.
-
AuthorPosts
