Forum Replies Created
-
AuthorPosts
-
July 16, 2019 at 2:36 PM in reply to: ✅can not work "rwmb_get_object_fields" with MB User Meta #15357
Anh Tran
KeymasterKeymasterJust 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 #15348KeymasterI'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 #15346KeymasterI 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 #15344KeymasterAre you using Gutenberg? I think the fullscreen mode of the TinyMCE is not compatible with Gutenberg.
KeymasterI got it. I didn't notice it was for background. Let me check that.
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.
KeymasterThanks for your feedback. Regarding the speed, yes, I optimized it several months ago. I'll take a look more about this.
KeymasterKeymasterHi 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.
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.
KeymasterHi Gary,
Thanks for a great question. The settings page doesn't support for saving to a custom table yet. The problem (technically) is the storage set for a setting page is fixed to use only options table.
Besides, the custom table also maps fields with an entry (post, term or user) via its ID. In case of the settings page, there's no such an ID. Thus, breaking the structure of the custom table.
I'm curious why do you want to save settings to custom table? I don't see any benefit using it over standard options table.
KeymasterHi, Elementor already has the image size option, please use it:
KeymasterHi Peter,
Glad that you found the problem. That's what I said in the previous comment. However, I've added a simple check for the Meta Box plugin that allows you to have a meta box with no fields. Try it here.
July 10, 2019 at 9:08 AM in reply to: ✅Conflict with Yoast and/or GravityView front end submission #15308KeymasterOK, let me take a look.
-
AuthorPosts
