Forum Replies Created
-
AuthorPosts
-
October 12, 2019 at 8:38 AM in reply to: ✅MB Term Meta does not change version number after update 1.2.5 to 1.2.6 #16493
Anh Tran
KeymasterHi Robert, thanks for your feedback. I've just reuploaded the zip file to the server. Please try again.
Anh Tran
KeymasterThat probably relates with the permission that WordPress gives to the author. Please try with the code that adjust capabilities in this docs.
Anh Tran
KeymasterHi Robert,
If you don't have any premium extension installed, then the plugin is smart enough to hide the License menu for you. In that case, you don't need to enter any license key at all.
Anh Tran
KeymasterHi Kevin, the
stdparam should work on both back end and front end. I added some docs on settingstdfor groups a couple of days ago, please take a look.Anh Tran
KeymasterI may decide to only let the form input one at a time, and make sure it’s done via AJAX so it’s done fast enough that the user doesn’t mind…
Good idea. I didn't think about it.
If you go with event = post (with custom table), then you'll have 2 row in the DB. One in the posts table, which looks like a normal post. One in the custom table for event details. The custom table will help you query fast, while the default posts table helps you to have UI in the back end.
Anh Tran
KeymasterYou probably don't need to implement custom solution for ajax anymore. We have added ajax support for object fields in version 5.2. See this blog post for details.
October 11, 2019 at 2:38 PM in reply to: ✅Warning on metabox for relationship to multiple CPTs #16476Anh Tran
KeymasterHi,
When creating relationship, please set the
post_typeparameter to a single post type. It doesn't accept multiple post types.Anh Tran
KeymasterHi Austin, I've just checked and don't see the bug. Can you give me some details on that? What code do you use to register the meta box?
Anh Tran
KeymasterJust fixed this issue in the latest version of MB Geolocation.
October 10, 2019 at 2:46 PM in reply to: The "Meta Box" way to disable Autocomplete & Autofill? #16458Anh Tran
KeymasterUnfortunately, it's not possible, since the form is not created by the plugin. The form is created by WP, so I think your solution here is the best one if you want to add
autocompleteattribute to the entire form.Anh Tran
KeymasterHi,
Do you mean showing the data dynamically, based on the user selection of related posts/terms? If yes, then I think you'll have to do that your way with JS + custom HTML field.
Anh Tran
KeymasterHi,
I still can't replicate the bug. I recorded a video here: https://www.loom.com/share/bd04f3fd07654d88a22b37bfb54881dc. Please take a look.
Anh Tran
KeymasterHi, I'm very sorry to make you feel bad. We're finalizing some issues today and will release a new version now. We're trying my best to prevent such bugs to happen again and that's why it takes some time.
The reason I marked this topic resolved is just for tracking the issues on the support forums. So we know if there's any bug that we haven't fixed yet (this is similar to Github issues).
Please understand. Thanks.
October 8, 2019 at 5:03 PM in reply to: ✅Minor fix needed: Labels displaying for hidden fields on term/taxonomy forms #16434Anh Tran
KeymasterThanks for your feedback. I've just fixed it. I'll release the new version after fixing this bug.
October 8, 2019 at 4:12 PM in reply to: The "Meta Box" way to disable Autocomplete & Autofill? #16433Anh Tran
KeymasterHi,
I see you already have solutions for that by adding
autocompleteattribute for the fields, don't you? I think that's a good way to fix this issue on Chrome. -
AuthorPosts