WordPress 3.0 new content types
Am interested in this as well.. Will content types be integrated into BP?
So, groups can have instances of able to post text, photos, videos, polls and such…
I think BP needs to be rewritten to use content types. Why settle for just groups or members or forums? I see site owners being able to create a content type and this becomes a slug that can be outputted via theme files.
@Modemlooper – it’s already being rewritten in a way in versions BP1.2.4/BP1.3-bleeding … started between BP trunk-r2990 to trunk-r3000. Pleasant surprise.
Hmm, needs to be some sort of way for front end users to harness the power of content types. Like that pages will be components. It’s merging into WP better.
I couldn’t make it to the chat today, but I just read through the thread. What I couldn’t find was the reasons for using pages instead of post_types. Were those listed off on the audio portion or something?
I’ve spent the last month digging really deep into post_types, and while I don’t have a strong background in bp structure, post_types seems like the perfect fit for bp. Would you kindly give us some of the pro’s/con’s of pages vs types and why the decision was made? Maybe it would help many of us to understand the bp structure and direction in the future a little better.
I can say that post types are for individual pieces of content and not so much slugs. Pages seem a better fit for this. What I’m suggesting is say you create a content type called movies. There would need to be a way via front end of BP for users to add a movie. Right now they can enter posts either in the form of activity or forum updates. With 3.0 content types it opens a ton of options but only if BP allows front end users to add this stuff. Meta data added to post types?
@anointed – There is no audio chat! It’s all text. What you read is what actually happened.
WP 3.0 isn’t even out of the gate yet; when WP 3 actually gets released, we’ll see where Andy and the core devs take it.
@modemlooper – if you check out what the BP Wiki component does, it already uses custom post types (it’s a development version). So custom post types for BP is possible via plugins. However, for the core (as stated above), it’s whatever the dev team decides.
I ‘kind of’ agree with you when you say post_types are for individual pieces of content, but also disagree. Post types allows me to create a new object where I can assign multiple attributes to that object type ‘metadata, taxonomies’. You are also able to easily group individual object types of the post type together much easier than with pages. The real power comes into play when you create multiple post types and link them together. Then I have a ‘pods’ type of system with multi-relational datasets to a given object. There is just 100x more that I can do with a post type than with a page.
For instance, I am building a complete custom forum system using a post type. You could never do that with pages. Well I suppose you could but it would be much more work and not nearly as elegant. basically my goal is to completely dump the bbpress as it’s so far behind that it has no business in my sites. By using post types, I have all the inherent wp tools right at my fingertips for forum posts. Want to add images/video/tags/ to a post.. done… no work needed.
The advantage is then I could easily add that new post type to the activity stream, complete with all its attributes, ‘metadata’ for the individual object. Something else you can’t really do with pages.
Here is a really generic example of 3.0 multi relational post types in action. (It’s only a start, so please don’t complain about layout, have not even started that part yet, this is more concept than anything else)
What you see here is much more than meets the eye
1. This is a custom post type sermons which is related to post types podcasts, preachers, locations.
2. The sermon title, description, and video are part of the sermon post type
3. When on the ‘add sermon’ admin page, you are also able to link it to a pre-existing post type to grab the preacher, podcast, and location. If they do not exist then you can add those attributes within the sermons post type without having to leave. Meaning you don’t have to go to post type podcast to add the audio file to a sermon. Same goes for preachers, locations.
4. sermons and podcast post types also have related taxonomies, ‘series, topics’. which you can directly link within the sermons page.
The easiest way to see how it’s linked is to notice the ‘locations’ link on the sidebar. It goes to:
http://deardaddy.org/locations/his-sanctuary-of-prayer/ which is the post type ‘locations’.
Keep in mind I did not have to manually type in the location when I added the sermon, although I could have, because it already existed. I simply chose it from a drop down of existing locations and they were linked together.
The power of this is simple.
1. I create a location one time
2. I can now add the individual location attribute to any new post type I create so long as I link the post types together, create a relationship in my themes functions file. This means that a user never has to input data more than 1x, it can be used over and over again in any post type.
To wrap up:
You said ‘a way in the front end of bp for users to add a movie’. I am already doing everything but the adding via the front end for the sermon example above. Adding the ability to the bp front end, will take me a bit of work, but it’s possible. I just have not yet had the time to read the bp code close enough. Hence my argument for post types in bp instead of pages. why add a movie page, when I can add a post type movie with all the attributes into the stream. Much much more power that way.
will be interesting to see the direction they take. If they don’t worry about backwards compat well then the doors are wide open.
@r-a-y you’re right, Saw for myself that BP components are rendered as Pages in test install with WPMU2.9.2/BP1.2.3 upgraded to WP3.0beta2/BP1.3-bleeding.
BP components rendered as Pages is not hot for me when I have 100+ Pages in main site of another test install (as I have in some live sites) and the Edit Pages panel and pagemash panel) have the BP components mixing in with “important information/documentation.” In this scenario, it would be more orderly to go multisite and to create a sub-blog and just to activate BP away from main site.
Of course for installs with BP set up primarily for social networking and with only 4 or 5 “static” pages – About, Contact, etc, no problem with components as Pages.
@anointed – great stuffm thanks for sharing Animo post_types.
yeah I’m saying post types need to be able to be written from front end or they are useless for a social network. That way you will be able to create a network so individualized from any other BP network.
Front end creation will prove critical and make the next generation of buddypress way more usable and flexible. If users have to go to a blog dashboard to do something as simple as share a photo or a movie review (examples of custom post types), it’s going to turn people off.
We need front end ability…and, come to think of it…we need it for regular old-fashioned blog posts too.
BP would benefit from some table reduction.
Andy and I talked at WordCamp San Fran about how some components would benefit greatly from using the posts table, like Private Messages and Groups. Other components like XProfile would be more tricky and may not see any performance improvements, but would still be doable similar to the WP3.0 Menus.
So, it’s a likely direction, but don’t quote me yet.
- The topic ‘WordPress 3.0 new content types’ is closed to new replies.