Forum Replies Created
-
AuthorPosts
-
July 17, 2019 at 11:57 AM in reply to: Metabox switch not saving when in Metabox grouping on MB settings page #15380
Anh Tran
KeymasterHi,
Here is a video that I created for testing:
https://www.loom.com/share/e519722638ed4cb299106b56ee83be8f
Just a note that if you clone a group and if all the child fields have no values, then that clone won't be save. That might be the case.
Anh Tran
KeymasterHi FED,
Here is the video I recorded with your code:
https://www.loom.com/share/2c4fe91c390c4faab2a638454a06df90
As you see, the switch field works. I tested with Gutenberg (WordPress 5.2.2) and also tested with the classic editor (with Disable Gutenberg plugin activated). There's also no errors in the console.
July 17, 2019 at 11:24 AM in reply to: ✅Registration: username as email, duplicated fields, avatar, visibility issue #15378Anh Tran
KeymasterHi Mauro,
This is a great feedback. I'll make the change and update the plugin soon.
Anh Tran
KeymasterHi, at the moment there's no params to delete files when a post is permanently deleted from the Trash. However, WordPress has a hook
delete_post(https://codex.wordpress.org/Plugin_API/Action_Reference/delete_post) to let you do custom actions. In this case, you can get the post files and delete them.July 17, 2019 at 10:23 AM in reply to: ✅Feature Suggestion: one query to get all custom fields in a group #15376Anh Tran
KeymasterHi Mauro,
If performance is your concern, then using Meta Box helper functions or get_post_meta is totally fine. WordPress will query all post meta only once, cache them and don't make extra queries if you call get_post_meta multiple times.
In case you want a single function that returns all meta value, WordPress has get_post_custom() function:
https://codex.wordpress.org/Function_Reference/get_post_custom
Just a note that it returns the raw values stored in the post meta, the same as get_post_meta.
Anh Tran
KeymasterNew version for Meta Box AIO has just been released! Please update.
July 16, 2019 at 2:53 PM in reply to: Metabox switch not saving when in Metabox grouping on MB settings page #15362Anh Tran
KeymasterHi,
Did you mean 'toggle switch' = the group bar collapse element, or is that a switch field type?
Can you post a screenshot/video here?
Anh Tran
KeymasterHi pza,
Thanks a lot for your feedback. These are great suggestions. I'll do that and update the extension.
Update: the changes are added in the 3.1.0 version.
July 16, 2019 at 2:44 PM in reply to: ✅Conflict with Yoast and/or GravityView front end submission #15360Anh Tran
KeymasterHi pza,
I answered you via email. Probably you haven't checked. I'll post it here so others can see:
The problem is the Yoast SEO plugin, not Gravity or MB Custom Post Type.
I see you use MB Content Type to create a post type Profile, and connect this post type to GEO WP and Gravity. When you edit an entry on the front end, Yoast SEO plugin tries to count links for the post (a profile). This action has bad performance and can't finish.
Here is the screenshot of where the bug happens:
https://imgur.elightup.com/v85FJVU.png
Notice the file names in case you want to find out more.
Briefly, because you need to create a post type for Profile to connect this post type to Gravity View, and Yoast SEO tries to count links for all post types --> break.
It doesn't matter if you MB Custom Post Type to create the post type. As long as the post type exists (you can try creating with just code), Yoast SEO breaks the page.
As this bug belongs to Yoast SEO and it's quite complicated, it's beyond my ability to fix that for you.
Anh Tran
KeymasterHi FED,
I've just tested 2 fields above and they work. Can you post the full code here?
July 16, 2019 at 2:36 PM in reply to: ✅can not work "rwmb_get_object_fields" with MB User Meta #15357Anh Tran
KeymasterAnh Tran
KeymasterJust released a new version of the extension (2.0.2) to return full image URL for the background. Please update.
July 15, 2019 at 2:41 PM in reply to: Block editor overlaps on fullscreen mode of wysiwyg field #15348Anh Tran
KeymasterI'll do it now.
Update: The ticket is here: https://github.com/WordPress/gutenberg/issues/16584
July 15, 2019 at 2:30 PM in reply to: Block editor overlaps on fullscreen mode of wysiwyg field #15346Anh Tran
KeymasterI couldn't find anything on Gutenberg's Github repo. Looks like they haven't known about this yet.
July 15, 2019 at 2:12 PM in reply to: Block editor overlaps on fullscreen mode of wysiwyg field #15344Anh Tran
KeymasterAre you using Gutenberg? I think the fullscreen mode of the TinyMCE is not compatible with Gutenberg.
-
AuthorPosts