Forum Replies Created
-
AuthorPosts
-
July 16, 2019 at 2:53 PM in reply to: Metabox switch not saving when in Metabox grouping on MB settings page #15362
Anh 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.
Anh Tran
KeymasterI got it. I didn't notice it was for background. Let me check that.
Anh Tran
KeymasterI think the main problem with your settings is the unknown (probably huge) number of settings. There must be some way to resolve it beyond the custom table or options table. Because both solutions probably don't work well with this kind of data structure (options table uses serialized array, while custom table requires fixed columns).
I'm not sure about how you save data. IMHO I'd suggest reworking on the data structure first, then choose a way to store data.
If you need any help from my side, I'm happy to do so.
Anh Tran
KeymasterThanks for your feedback. Regarding the speed, yes, I optimized it several months ago. I'll take a look more about this.
Anh Tran
KeymasterAnh Tran
KeymasterHi Gary,
The Conditional Logic extension works only for fields in one page. So if you have a settings page, you can set conditions for the fields inside. But you can't set conditions from another settings page. The purpose of the Conditional Logic extension is make a field visible/hidden in real time, and thus, it has to know the fields in the current page.
As the settings page is created by you, you can control how many fields are there and can avoid a super large array of settings. WordPress supports quite well for the length of option value in the database.
Anh Tran
KeymasterHi Gary,
Thanks for choosing Meta Box!
In Meta Box, code that you're using in your PHP files and the field groups you created in the MB Builder work independently and simultaneously. There's no connection between the code and the fields created in MB Builder.
Unless you export the code from the MB Builder and put it in your theme/plugin. In that case, what loads first will take effect. But you should avoid this as it's confusing. If you want to use code, you should move the field group in MB Builder to Trash (or switch to Draft) to prevent it from loading.
Besides, in MB Builder, the custom attributes feature is powerful enough for you to add custom settings for the meta box or for the fields. Using this feature will help you achieve the same effect as using code. However, if you want to use code, please just use it.
-
AuthorPosts