Forum Replies Created
-
Posts
-
@kplaneta– Welcome to the Piklist Community!
We were able to reproduce this bug and it will be fixed in v0.9.9.3 which should be release tomorrow.
Glad you love Piklist. Feel free to tell the world by leaving Piklist a 5 Star review on WordPress.org. It really helps the project!
By setting
'show_ui' => true, WordPress is rendering the taxonomy field twice. You will also have to add'meta_box_cb' => false, which stops WordPress from rendering the default meta box.OR… I’m going to let you in on a little secret.
The latest version of Piklist 0.9.9.x, makes it super easy for you to REPLACE the default Taxonomy meta box with your own.
We call it extending a section, or EXTEND.
Just add this to the comment block of the file that the taxonomy checkbox is in:
Extend: tagsdiv-trip-type Extend Method: replace
By adding this you’re telling Piklist to replace the div with ID tagsdiv-trip-type, which is the default WP meta box.
When we officially release 0.9.9 we’ll formally announce this feature.
Also, WordPress doesn’t like hyphens in taxonomies names. Check out the first parameter in register_taxonomy.
Add this to your wp_options table:
Option Name:
piklist_updates
Option Value::a:1:{s:7:"piklist";a:1:{i:0;s:5:"0.9.9";}}That should trigger it.
@vavakco– In the latest beta we changed how this works and your fix breaks it. We will investigate on how to implement this. Thanks for letting us know.
@justin– I just tested with your code and the script ran great for me. Updated the db just like it was supposed to.
Any other details you can offer would help.
@justin– I just emailed you your updated code with the changes.
WordPress really doesn’t make it easier to control the user profile or edit term pages. Actually, they are pretty much a mess. The code in demos is hiding those fields with CSS on the alternate tabs. Not the best solution, but the only one WordPress gives us right now.
@justin– I’m sorry, I didn’t understand.
Do you have some legacy user meta data you send to us so we can test? The upgrade script was supposed to fix everything.
I believe the notice is going away in our latest beta. Please test and let us know.
@rcreators— Email us at [email protected] to discuss.
@justin– I’m sorry if our initial blog post wasn’t clear. We changed the array structure to make it easier for you. Any custom code you wrote targeting a specific array key will probably not work. You can now loop through this data with standard foreach loops.
We’re sorry for any confusion. But the feedback we’ve received is that making this small change now, will make things better for all Piklist developers in the future.
@justin- It will be easier if I have access to your code. Please zip up and email to [email protected], and I’ll be happy to take a look.
@ndbe– WordPress stores all post statuses in the $wp_post_statuses global, and they all have to be unique. You can’t have two post statuses with the same key and different labels. WordPress doesn’t allow it.
