Thread Starter
llucax
(@llucax)
BTW, some other custom metaboxes I create (using Developer’s Custom Fields plug-in) are not shown either.
Hi llucax,
I have to check. Probably the problem is with actions priority. I’m guessing that my hook executes before hooks in Developer’s Custom Fields. I’ll let you know as soon as it possible.
Regards,
Hi llucax again,
Have just checked Developer’s Custom Fields and I need some time to understand how it works. And as I see you are trying to add some custom fields for custom post type.
Try to understand, I’m not pushing my style, but I’m recommending to look into MP Former Custom Post Type Manager.
Now it allows to add custom post types, taxonomies and statuses without codding. I almost finished with additional features like – custom metaboxes and custom fields (the same – no codding).
If you are interested in participating in this project, I’m always open.
Thread Starter
llucax
(@llucax)
Right now I’m using custom fields for regular post types. I understand you can’t debug its interaction with your plug-in but for now I’m not a position where I can switch.
About custom taxonomies, I’m using WP API directly, I’m registering the new taxonomies using an “init” action in my theme, without using an explicit priority. Should I change the priority? Should I register them in another action hook?
Thanks!
No, you understood me wrong. I’m really interested in debugging with issue and find my fault.
You’ll help me a lot if you send me a part of your code where you define taxonomies or a whole plugin. In such way I’ll be able to give you updated even today.
Use my email from Access Manager option page (on side metabox “Support”).
Thanks a lot for your cooperation.
Regards,
Thread Starter
llucax
(@llucax)
BTW, it looks like DCF add metaboxes with this action hook:
add_action( ‘add_meta_boxes’, ‘slt_cf_display_post’, 10, 2 );
AFAIK 10 is the default priority. One particularity about DCF is that you can show fields only for post with a particular taxonomy term, so fields are conditional to a particular post. But I guess that’s why you can scan for metaboxes using a custom URL, right? How are the metaboxes scanned?
Thanks again for your time!
Yeap I know that.
My priority is 999. So it should scan in last order. I really don’t know how DCF works and I have to check that. Are you using the url to edit post page with particular taxonomy term?
Thread Starter
llucax
(@llucax)
Yes, I’ve tried that. BTW, the custom taxonomy metaboxes are not shown in the Advanced Access Manager and they are not even conditional, so that’s even more weird.
Ok. I’ll do some test at let you know in couple of hours.
Thanks
Thread Starter
llucax
(@llucax)
About DCF, if you are scanning for metaboxes looking for the text class=”postbox” in the URL, maybe it’s failing because DCF uses this:
class=”postbox hide-if-js”
Custom taxonomies boxes appear as:
class=”postbox ”
Actually I’m not searching for any kind of class=”postbox” on page. I’m using global variable $wp_meta_boxes. And if some plugin register metaboxes and taxonomies correctly and in proper order, this variable should have these metaboxes.
To see exactly what I’m talking about you can open a file mvb_wp_access.php and function is metaboxes (line 298).
Thread Starter
llucax
(@llucax)
OK, thanks for the info.
dumping $wp_meta_boxes there, show all metaboxes (DCF and custom taxonomies metaboxes appear). Weird. I’ll keep investigating…
Thread Starter
llucax
(@llucax)
OK, going to the URL of the post and adding &grab=metaboxes to the end of the URL, does grab the metaboxes correctly, so I guess the bug is somewhere there.
Probably I know what is going on now. It takes me some time to find the solution.
Thanks for feedback. This is very helpful.
Thread Starter
llucax
(@llucax)
You are very very welcome 🙂
