Forum Replies Created
-
AuthorPosts
-
Anh Tran
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.
KeymasterI know this is a stupid question, but have you activated the MB Admin Columns extension? Some users forget to do this.
KeymasterHi Peter,
These errors happen because some meta box is mis-configured. Please check the code for meta box registration to make sure it follows the docs. These are usual problems:
- Forget to return the
$meta_boxesvariable from the callback for therwmb_meta_boxesfilter. - Forget to add fields to the meta boxes.
KeymasterHi,
Please use the
'require' => trueparameter for the field. The validation doesn't work in this case.KeymasterHi Ben,
These are interesting questions!
- CSS: in the MB Frontend Submission extension, the CSS is outputted in the same location as the form. It's not in the header nor footer. The plugin uses
wp_enqueue_styleto output the CSS. Unfortunately, this function doesn't support the location of the CSS (header, footer). I'd suggest optimizing the CSS with a minify plugin like Autoptimize. - jQuery: jQuery is registered by WordPress and you should not remove it. A safe way to use the latest version of jQuery is using the plugin Use Google Libraries or this technique. In either way, please test it first.
KeymasterHi Ben,
Sorry, the contact form and the forum doesn't accept attachments, just for security reason. You can upload the file to https://send.firefox.com or https://wetransfer.com and send me the link.
KeymasterHi Adrien,
It's not possible with WordPress. However, you can do this with a help of LH User Taxonomies plugin.
KeymasterHi,
Passing IDs directly in the
post__inparameter will generate a SQL query like this:SELECT * FROM wp_posts WHERE ID IN (1,2,3)It doesn't generate
ORstatement as you thought.Because the ID is the primary key of the posts table, this query is performant and faster than normal queries.
If you're worry about getting 5000 records from the DB, then imaging this technique as breaking a very slow query (if you do the normal way with WP_Query and JOIN) into 2 fast SQL queries. Although the number of queries increases, the performance is much better.
KeymasterPlease send me the credentials via the contact form (link above). It's secured.
July 6, 2019 at 10:46 AM in reply to: ✅Serialized array for select_advanced saves incorrectly on front-end submission #15271KeymasterThanks a lot for your debug info! I'm going to check it now and hopefully will get it fixed soon.
Updated: I recorded a video for this problem: https://www.loom.com/share/8ec338cc383b4917973967f27c177971. I couldn't replicate it. Can you see and let me know if I did anything different from your side.
- Forget to return the
-
AuthorPosts
