Forum Replies Created
-
AuthorPosts
-
Anh Tran
KeymasterI know this is a stupid question, but have you activated the MB Admin Columns extension? Some users forget to do this.
Anh Tran
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.
Anh Tran
KeymasterHi,
Please use the
'require' => trueparameter for the field. The validation doesn't work in this case.Anh Tran
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.
Anh Tran
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.
Anh Tran
KeymasterHi Adrien,
It's not possible with WordPress. However, you can do this with a help of LH User Taxonomies plugin.
Anh Tran
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.
Anh Tran
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 #15271Anh Tran
KeymasterThanks 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.
Anh Tran
KeymasterHi Adrien,
I'm afraid the plugin only supports static value. There's no way to make it understand the dynamic value at the moment.
Anh Tran
KeymasterIt's a little rush of you. Let me know if you find anything buggy from now on.
Anh Tran
KeymasterOK. At least it works for now as you can't reproduce the issue. Let me know if you need any help!
Anh Tran
KeymasterHi Cedric,
1st question: It depends. Both ways work. The 1st one seems to show users the content, while the 2nd one seems to be more cleaner.
2nd question: To show the title, but don't want to let users edit them, you can use 2 methods:
- Use a little PHP to output the post title (and exclude post title field from the form shortcode)
- Or modify the template for post title field (see this guide) and add a new param
'readonly' => trueto let users not able to edit it.
- Forget to return the
-
AuthorPosts