Forum Replies Created
-
AuthorPosts
-
Anh Tran
KeymasterHi all,
I've just updated the Updater extension which solves the problem. Please update it.
Anh Tran
KeymasterHi again,
I think I found the problem and fixed it here. The fix is available on Github. Can you please test it?
Anh Tran
KeymasterI understand. The problem that made me choose meta box for settings page is keeping the consistency in the code as they share the same API for meta boxes. This is also applied in some famous frameworks such as Genesis or Hybrid Theme.
Anyway, I will think more about using tabs/sections as another option (later). WordPress uses tabs/sections for its settings page, while using meta boxes for edit pages. This inconsistency of WordPress itself makes developers like us harder to make a good decision. Also the API WordPress offers for them are totally different which make things more inconsistent.
Anh Tran
KeymasterCan you post the code?
Anh Tran
KeymasterI see. I will check the updater plugin and the updating system. There might be an issue in the first check.
Anh Tran
KeymasterI couldn't read the error when updating. Can you tell me which one? Also, it works when you refresh the browser, doesn't it?
Anh Tran
KeymasterHi, I've just added this to Github [issue](https://github.com/rilwis/meta-box/issues/803) to keep tracking the development. We will work on this later. Please be patient.
Anh Tran
KeymasterCan you post the code to register meta boxes? I want to test that.
Thanks
Anh Tran
KeymasterHi Rik,
I think it's a good feature. However, do you think it will confuse user if they enable it for both default WP editor and WYSIWYG, or 2 WYSIWYG fields?
Anh Tran
KeymasterHi,
Currently, we have an internal caching mechanism, that will get all fields (by ID) and store in a static variable. This caching mechanism allows us to speed up the
rwmb_metafunction. Due to field ID is used as the key in the cache, field ID must be unique.However, as you said, there can be a situation that 2 post type can have a similar meta box where fields can have the same ID. Therefore, the helper function doesn't know which field it should get meta value for.
I have just pushed a fixed for this on Github, please try and let me know if it works for you:
https://github.com/rilwis/meta-box/commit/747375eb1d08176ace49c954de2b8d4a9d1d43d5
March 7, 2016 at 4:15 PM in reply to: ✅Wysiwyg editor in clonable groups and nested clonable groups #2423Anh Tran
KeymasterFYI, WYSIWYG field now is cloneable. Please update to v4.8.3 and Group extension to 1.0.6.
For more info, please check this blog post.
Anh Tran
KeymasterFYI, the version 4.8.3 was released. Please update to get rid of the bug.
March 4, 2016 at 7:45 AM in reply to: Media Type Field not showing Images after Upgrade from Version 4.7.3 to 4.8.2 #2417Anh Tran
KeymasterOh, the
mediatype is not a real type. It's an abstract type which will be extended byfile_advancedorimage_advanced. Please usefile_advancedorimage_advancedinstead.Anh Tran
KeymasterHi,
We're working on
plupload_imagefield to make it simpler just likefile_advancedandimage_advancedso it can work with group. Please wait.March 3, 2016 at 3:48 PM in reply to: Taxonomy - select_advanced - multiple => true ---- Problems #2412Anh Tran
KeymasterHi, the
js_optionsparameter is used for displaying only. To store multiple values of taxonomies, you should add'multiple' => trueto the field's param, as following (I also rewrite the parameters to match new version of Meta Box):array( 'id' => 'event_category', 'type' => 'taxonomy', 'taxonomy' => 'event-categories', 'field_type' => 'select_advanced', 'query_args' => array(), 'js_options' => array( 'multiple' => true, ), 'multiple' => true, 'placeholder' => 'Select ...', 'columns' => '4', 'tab' => 'general', ), -
AuthorPosts