Forum Replies Created
-
AuthorPosts
-
January 26, 2018 at 9:39 AM in reply to: single image field abilty to save image url to database #8347
Anh Tran
KeymasterGotcha! In this case, I think
file_inputworks best. You still can use the media library to upload/select images while still seeing the image URLs. If you have multiple images, probably need to make the field cloneable.KeymasterHi,
The "context" term is created by WordPress only for the editing screen in the admin area. It very much depends on the layout of the editing screen. In the frontend, there's no such layout which makes the "context" useless.
KeymasterOh, sorry. jo.on is right. There's a syntax error in the code. Please just remove the last ");". I supposed to write code for PHP 5.3, but then changed to the normal syntax (and forget to remove the last ");").
KeymasterHi,
The relationship is bi-directional by default. That means you can query back and forth with the same API without any problem (or performance issue).
However, to make the UI clear, the plugin only allows to select the connection from an object to others (the forward direction), and displays the backward connections in another meta box. It's the same behavior in Posts 2 Posts plugin, so I just brought it 🙂
January 25, 2018 at 5:20 PM in reply to: single image field abilty to save image url to database #8327KeymasterWhy do you want this? Using ID allows us to get other info of the image easily. Besides, you still can get the URL of the images.
KeymasterHi, we've just updated the extension with support for multiple meta boxes. Please update and let me know what you think.
KeymasterHi, it's not possible at the moment. I'll make a note. Thanks for your suggestion.
KeymasterHi, the help tabs need to be defined like this:
'help_tabs' => array( array( 'title' => 'General', 'content' => '<p>This tab displays the general information about the theme.</p>', ), array( 'title' => 'Homepage', 'content' => '<p>This tab displays the instruction for setting up the homepage.</p>', ), )Then it will display like this:
https://imgur.elightup.com/c7bIf3P.png
I will update the docs. Thanks for your question!
KeymasterHi Guy,
For now there's no options for those placeholders.
January 23, 2018 at 1:47 PM in reply to: Prevent sortable nested group being able to be moved outside of its parent. #8304KeymasterJanuary 23, 2018 at 10:30 AM in reply to: Prevent sortable nested group being able to be moved outside of its parent. #8302KeymasterHave you cleared the browser cache? The fix is in JS and requires to clear cache to get the fresh version.
KeymasterHi,
The script need to wait until DOM ready (like
jQuery(document).ready()) to apply the conditions on elements. So, all elements must be loaded in order to run. I'm trying to optimize the JS part to make it runs faster to reduce the delay time.In the meantime, I think your CSS solution is good. CSS is loaded before JS and applied very early.
KeymasterHi,
The similarity:
- Both fields display terms to users to select.
The difference:
The only difference is how they store selected terms in the database:
-
taxonomy: doesn't store any terms in the post meta. Instead, it sets post terms. Think about it like a replacement of "Category" or "Tag" meta box of WordPress.
-taxonomy_advanced: store terms' IDs in the post meta and doesn't set post terms.Hope it's clear.
KeymasterHi, I've just fixed this bug in version 1.5.5. Some of your select fields share the same part, which breaks the logic for select tree (supported in 1.5.2). The fix added a better check for select tree.
Please test it.
KeymasterHi Adam, I've just fixed it on Github. Can you test it?
-
AuthorPosts
