Closed 10SexyApples closed 14 years ago
I haven't looked at the Custom Field Template plugin, but it sounds like it could be a timing issue. I'm registering the custom post_types on init at priority 1. If the Custom Field Template is running the code to remove the support for the custom meta boxes before the post_types are registered, like on plugins_loaded, it won't work. You can try to changing line 44 of cp-custom-content-core.php of cms-press to run priority 1 for plugins_loaded or trying to change the Custom Fields Template plugin to run its code on init instead.
I hope that helps.
hmmm. well, no luck heading in that direction. Custom Field Template is already loading on init, though the priority isn't set, just default. I tried all of your suggestions and then some, but, to no avail. I have to use the custom field template, so, I really need to figure this out tomorrow or go back to rolling my own darnit. If you could take a look that would really be swell Michael. Just hit me up on my email address for login info if you can - on a side note, is the CMS press code putting all of its info into the same table areas as the core does when I register post types and taxonomies myself? It would be really great if any of these custom content plugin GUIs would recognize previously registered custom types, but, alas, none so far. It's been a real pain in the arse having to make a definitive decision which way to go before I can take a next step in building out this site ... especially with everything up in the air and me developing on a nightly build. Anywho, wha right? heh. Last but not least, I'm feeling a little idiotic regarding the custom permalink structures - I was reading the trac discussions about having it in core, and I have to agree it would make life a heck of a lot more intuitive. In the CMS Press admin area, I am not sure what to do. Stupid little question mark hanging over my head. The site I am developing currently is for free lesson plans for teachers to help them integrate art into the classroom. My custom post types are: lesson, howto and workshop. My custom taxonomies are, for example: art subject - terms: creative writing, yadda yadda, yadda academic subject - terms: science, yadda yadda educational standard - terms: science 1.b, yadda grade level - terms: grade three, ya
You get the idea. I would like to have the structure for the whole site as such - foobar.com/custom post type ... for archive page of all lessons, howtos, or workshops I'll use lesson instead of custom post type from here out - foobar.com/lesson/custom-tax/tax-term ... for taxonomy page foobar.com/lesson/custom-tax/tax-term/lesson-name ... for single pages
I'm not sure what to put on my regular permalink setting page any more, or what to put in the CMS Press permalink setting option or how the two interact exactly. Perhaps I just haven't had enough sleep ;-) Any more clues to help my sicheeashion would be greatly appreciated, of course. Angie
With both CMS Press custom field in support array and using Custom Field Template being used in post type, with default fields set not to show, Custom Field Template values disappear on save draft. argh.so much for continuing to work while I get this sorted. ;-)
I'm testing the Custom Field Template plugin, without CMS Press installed, and it doesn't seem to work correctly with custom post types by itself. I can't even get it to save the custom post type list in the options.
I am using WP3.0 nightly, twentyten theme, all default options, no other plugins, and it works beautifully for me on my custom post types. I'm not giving it a list of custom post types though, just one per template. What's your setup? Email me for login info if you want to take a look on my setup. Until it's a little less cumbersome to deal with additional meta boxes, Custom Post Template is going to be pretty standard, and pretty important for someone like me. I usually write my own meta boxes, but, the amount and complexity of them that I need for this build makes it counterproductive and I bring in CPT. I need multiple file uploads, multiple rich text editors etc. this time around. If it comes down to no way to get these two to play nice, it would be more time consuming to put in all of those custom meta boxes than to figure out how to rewrite the urls for my custom post types, so, I guess I'll have to go that route, but, man, I'm really hoping we can figure this out. I'm going to keep looking at it today and crossing fingers~
I did this testing off of HEAD with no other plugins running. Though, it may be that I'm unfamiliar with the plugin and wasn't doing something correctly. I'm sorry I don't have more time to look into the conflict at the moment.
I know this doesn't help you in your timeline, but my goal is to simplify the metabox api in WP core for version 3.1 and incorporate something similar to Custom Post Templates directly into CMS Press in future releases.
Hi Michael, thanks so much for your help. I contacted Hiroaki ( Custom Field Template ) about it, and it was a bug. He fixed it right away and now all is working wonderfully. I'll be looking forward to the metabox implementations you are planning ;-). All your hard work is VERY appreciated!
Oh yeah, did you have any advice for the permalink question? That's really confusing me~
Ya, sorry, I missed that. You won't be able to use the custom taxonomy in the url of the custom post types, at least for this version. I didn't add that support yet, because it requires setting a default term for each taxonomy, or else you could end up with some content without a term set, messing up the URL. Hopefully I can add it in the future.
You can still have a URL structure like foobar.com/lesson/lesson-name/ by setting the identifier field to 'lesson' and then setting up the permastructure as '/%identifier%/%postname%/
Hi Michael, I've been developing on the WP nightly builds and was rolling my own while everything was getting wrangled out with custom post types. I noticed that you've had a heavy hand in the development of the newer code, and wanted to say thank you for that. Everything looks great! The time has come in development of this site however to really get crackin' and I'm hitting walls on permalinks, so, since you've already got those worked into CMS Press, I've wiped the database, installed your most recent version, updated the post type support arrays in your code to include the most recent terms, and set everything up through your plugin. I'm also using the Custom Field Template plugin to ease the pain of setting up quite a complex custom meta box arrangement on these custom post types. However, there seems to be a conflict with Custom Field Template and CMS Press. When I ask Custom Field Template to disable the default custom field meta box, it doesn't work and I end up with the Custom Field Template custom fields as well as the defaults. If I disable support in CMS Press for custom fields, then, of course they don't show up, but, this isn't a good idea. Custom Field Template was performing this function flawlessly with my previously home rolled but permalinkless custom post types, and they had custom fields in the support array. Any help fixing this would be greatly welcome. Brain is fried and deadline is pending~