[wp-hackers] Unsubscribe

Sun Apr 18 16:06:05 UTC 2010

On Sun, 2010-04-18 at 07:35 +0000,
wp-hackers-request at lists.automattic.com wrote:
> Send wp-hackers mailing list submissions to
> 	wp-hackers at lists.automattic.com
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.automattic.com/mailman/listinfo/wp-hackers
> or, via email, send a message with subject or body 'help' to
> 	wp-hackers-request at lists.automattic.com
> 
> You can reach the person managing the list at
> 	wp-hackers-owner at lists.automattic.com
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of wp-hackers digest..."
> 
> 
> Today's Topics:
> 
>    1. Re: URL structure for web application with wp (Christian Foster)
>    2. Re: URL structure for web application with wp (Hal Burgiss)
>    3. Re: [GSoC] Comment Moderation (Bumbu Alex)
>    4. Re: Regarding wp markup language (scribu)
>    5. Re: URL structure for web application with wp (scribu)
>    6. Re: Regarding wp markup language (Mike Schinkel)
>    7. Re: URL structure for web application with wp (Mike Schinkel)
>    8. Re: URL structure for web application with wp (scribu)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Sun, 18 Apr 2010 05:59:18 +1000
> From: Christian Foster <christian.foster at gmail.com>
> Subject: Re: [wp-hackers] URL structure for web application with wp
> To: wp-hackers at lists.automattic.com
> Message-ID:
> 	<h2p89a1851d1004171259z6ebabab5nb728871a171dc1d1 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> http://wordpress.org/extend/plugins/taxonomy-metadata/
> 
> This looks like it is done in a pretty clean way, I think I will try it out.
> 
> On Sun, Apr 18, 2010 at 5:40 AM, Charles Frees-Melvin <charles at cefm.ca> wrote:
> > I think you are running into a complexity/limitation of WordPress. That a
> > taxonomy cannot have meta.
> >
> > For example I've been using Wordpress for my photo album. And have been
> > running into the issue that I cannot have a link meta to say that ID 55 of
> > the people tax is user 14. Or I cannot link a thumbnail to a category or tag
> > or tax. I think that this would be the next move to make your project
> > simpler.
> >
> > --
> > Charles E. Frees-Melvin
> > charles at cefm.ca
> > www.cefm.ca
> > 506-640-1007
> >
> > Sent from my iPhone
> >
> > On 2010-04-17, at 16:10, Christian Foster <christian.foster at gmail.com>
> > wrote:
> >
> >> Hi all,
> >>
> >> This has been driving me mad for a couple of days now and I was hoping
> >> for some suggestions or ideas. Apologies for the long question but I
> >> am really looking for the best possible (and most Wordpress-like) way
> >> to set this up.
> >>
> >> I'm building a basic project management system. This is the setup:
> >>
> >> Custom post types: Project, Milestone, Task, Message
> >> Taxonomies: Projects, Task List, Message Categories
> >>
> >> Obviously this app needs to be project-centric - so whatever post,
> >> archive or taxonomy we're viewing generally it should relate to a
> >> project. So - all post types are linked to a project via a term in the
> >> projects taxonomy that has the same name as 1 project.
> >>
> >> Example: Project 1 (post type project) is linked to term "Project 1"
> >> from the projects taxonomy. Message 1...Message 10 are also linked via
> >> term "Project 1" in Projects taxonomy.
> >>
> >> Therefore when viewing any individual post, we can check the term
> >> they're linked to in the "Projects" taxonomy and find out which
> >> project we are talking about. But, when viewing an archive we have no
> >> way to reference which project is being referenced unless we put
> >> something in the URL (or set a session variable which I also played
> >> with).
> >>
> >> Basecamp uses this style:
> >>
> >> /projects/id/ - project single
> >> /projects/id/messages/ - messages archive
> >> /projects/id/messages/id - message single
> >>
> >> Wordpress is using
> >> /project/id - project single
> >> /projects/term - archive for all posts with project term
> >> /message/id - message single (we check project term to get which
> >> project it's linked to)
> >>
> >> So - what do people think the best way of structuring the app might
> >> be? Here are what I see as the options at the moment:
> >>
> >> 1. Create pages as so
> >> /projects/project-id
> >> /projects/messages/project-id
> >> /projects/tasks/project-id
> >>
> >> Create custom rewrite rules, stick a project id on the end of the url
> >> on all of the above and then do custom page templates to look up and
> >> display the correct posts. Or some variation of URL rewriting and
> >> pages with custom templates.
> >>
> >> 2. Try to achieve functionality like categories where project is a
> >> category and we can link all post types into it and get the same style
> >> of paths:
> >> /projects/project-slug/task-name
> >> /projects/project-slug/message-name
> >> /projects/project-slug/project-name
> >>
> >> Wordpress is rewriting all custom post types as /post-type/slug at the
> >> moment, so I am not sure if this is achievable.
> >>
> >> 3. Some other solution using sessions to set the current project and
> >> then relating all queries to that project.
> >>
> >> Having written all of that I guess any of those options would do, I'm
> >> just not quite able to get a neat and tidy solution out though - any
> >> ideas would be appreciated.
> >>
> >> Chris.
> >> _______________________________________________
> >> wp-hackers mailing list
> >> wp-hackers at lists.automattic.com
> >> http://lists.automattic.com/mailman/listinfo/wp-hackers
> >
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> >
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Sat, 17 Apr 2010 16:02:56 -0400
> From: Hal Burgiss <hal at burgiss.net>
> Subject: Re: [wp-hackers] URL structure for web application with wp
> To: wp-hackers at lists.automattic.com
> Message-ID:
> 	<j2y962301c31004171302pc1d6c991q40f09872ef7790c4 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> On Sat, Apr 17, 2010 at 3:50 PM, Christian Foster
> <christian.foster at gmail.com> wrote:
> > Hi Charles,
> >
> > I think you're right - and so what I am doing at the moment is
> > creating a taxonomy and a post type for many things and then making
> > convoluted links between them (the post type only being necessary to
> > store extra information about the terms in the taxonomy). I'm guessing
> > that term meta might be included at some point, it would make building
> > more complex things out of wordpress easier.
> 
> You might look at the pods cms plugin. It has similar functionality to
> custom post types, but gives you more control over the url/routing.
> You can create a class that extends pods, then define the url path
> that will be fed through to your custom class. So something like
> '/projects/*', and then you handle the rest with your code however you
> like.
> 
> -- 
> Hal
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Sat, 17 Apr 2010 23:25:19 +0300
> From: Bumbu Alex <bmbalex at gmail.com>
> Subject: Re: [wp-hackers] [GSoC] Comment Moderation
> To: wp-hackers at lists.automattic.com
> Message-ID:
> 	<k2v13f1fbc61004171325ia63cd4a2p79b2b19f731ba2c5 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> little update for list of todos (some of then got from Eitan Adler thread):
> 
> 
>    - When threaded comments are enabled they are displayed when moderating
>    individual posts comments.
>    - Allow comment re-parenting.
>    - Support should also be added to the XML-RPC api to allow an external
>    app to implement similar functionality.
>    - In case of deleting comment which have child comments - ask user if
>    delete them, or re-parent them.
>    - Allow re-parenting using Drag & Drop in places like post editor.
>    - Create api for changing parent of comment, request all sub-comments and
>    other needed stuff.
>    - Add threaded comments to comments in moderation (more about UI)
>    - Warn(change background of comment row or smth else) moderator/admin if
>    there is post of unlogged user with the same email as registered user and
>    give ability to change the author from unlogged to those registered who own
>    this email.
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Sun, 18 Apr 2010 00:25:13 +0300
> From: scribu <scribu at gmail.com>
> Subject: Re: [wp-hackers] Regarding wp markup language
> To: wp-hackers at lists.automattic.com
> Message-ID:
> 	<q2y349fe48b1004171425j33c5bd48j8e120b6405e44efe at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
> 
> On Sat, Apr 17, 2010 at 8:04 PM, Jeremy Clarke <jer at simianuprising.com>wrote:
> 
> > The only things that aren't dead-simple to insert into themes are the
> > stuff that would be super-complicated to do even with a markup
> > language, the loop itself. In my case I write wrapper functions for
> > that stuff then call it in the templates, stuff like
> > gv_display_post_archive() or gv_display_recent_headlines(). IMHO that
> > is an area where WP has room to improve: it should offer default loop
> > etc functions that can be overridden by themers in functions.php or
> > plugins, similar to how the Comments system works now. I saw a trac
> > ticket in this vein at some point but can't find it now.
> >
> 
> 
> You're probably thinking of Modular themes: Apply template hierarchy to
> folders within a theme <http://core.trac.wordpress.org/ticket/12877>
> 
> 
> -- 
> http://scribu.net
> 
> 
> ------------------------------
> 
> Message: 5
> Date: Sun, 18 Apr 2010 00:31:43 +0300
> From: scribu <scribu at gmail.com>
> Subject: Re: [wp-hackers] URL structure for web application with wp
> To: wp-hackers at lists.automattic.com
> Message-ID:
> 	<j2x349fe48b1004171431q84888d03v65b9c99d97d5fdc2 at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
> 
> To link posts to other posts, I would use a posts2posts table, instead of
> the taxonomy system: fewer tables => better performance, easier to maintain
> consistency.
> 
> 
> On Sat, Apr 17, 2010 at 10:10 PM, Christian Foster <
> christian.foster at gmail.com> wrote:
> 
> > 2. Try to achieve functionality like categories where project is a
> > category and we can link all post types into it and get the same style
> > of paths:
> > /projects/project-slug/task-name
> > /projects/project-slug/message-name
> > /projects/project-slug/project-name
> >
> > Wordpress is rewriting all custom post types as /post-type/slug at the
> > moment, so I am not sure if this is achievable.
> >
> 
> When defining the post type, you can set 'rewrite' => false and then
> manually add whatever rewrite rules you want.
> 
> 
> -- 
> http://scribu.net
> 
> 
> ------------------------------
> 
> Message: 6
> Date: Sat, 17 Apr 2010 19:08:22 -0400
> From: Mike Schinkel <mikeschinkel at newclarity.net>
> Subject: Re: [wp-hackers] Regarding wp markup language
> To: wp-hackers at lists.automattic.com
> Message-ID: <9847379C-C4D3-47B6-A229-C3770B05AEAA at newclarity.net>
> Content-Type: text/plain;	charset=us-ascii
> 
> On Apr 17, 2010, at 1:04 PM, Jeremy Clarke wrote:
> > that is an area where WP has room to improve: it should offer default loop
> > etc functions that can be overridden by themers in functions.php or
> > plugins, similar to how the Comments system works now. I saw a trac
> > ticket in this vein at some point but can't find it now.
> 
> 
> +1
> 
> -Mike
> 
> ------------------------------
> 
> Message: 7
> Date: Sat, 17 Apr 2010 19:59:02 -0400
> From: Mike Schinkel <mikeschinkel at newclarity.net>
> Subject: Re: [wp-hackers] URL structure for web application with wp
> To: wp-hackers at lists.automattic.com
> Message-ID: <C8DC9EEB-3DA5-4239-8A01-A44E107BEF7F at newclarity.net>
> Content-Type: text/plain;	charset=us-ascii
> 
> On Apr 17, 2010, at 3:10 PM, Christian Foster wrote:
> > I'm building a basic project management system. This is the setup:
> > 
> > Custom post types: Project, Milestone, Task, Message
> > Taxonomies: Projects, Task List, Message Categories
> > 
> > Obviously this app needs to be project-centric - so whatever post,
> > archive or taxonomy we're viewing generally it should relate to a
> > project. So - all post types are linked to a project via a term in the
> > projects taxonomy that has the same name as 1 project.
> > 
> > Example: Project 1 (post type project) is linked to term "Project 1"
> > from the projects taxonomy. Message 1...Message 10 are also linked via
> > term "Project 1" in Projects taxonomy.
> > 
> > Therefore when viewing any individual post, we can check the term
> > they're linked to in the "Projects" taxonomy and find out which
> > project we are talking about. But, when viewing an archive we have no
> > way to reference which project is being referenced unless we put
> > something in the URL (or set a session variable which I also played
> > with).
> > 
> > So - what do people think the best way of structuring the app might
> > be? Here are what I see as the options at the moment:
> > 
> > 1. Create pages as so
> > /projects/project-id
> > /projects/messages/project-id
> > /projects/tasks/project-id
> > 
> > Create custom rewrite rules, stick a project id on the end of the url
> > on all of the above and then do custom page templates to look up and
> > display the correct posts. Or some variation of URL rewriting and
> > pages with custom templates.
> > 
> > 2. Try to achieve functionality like categories where project is a
> > category and we can link all post types into it and get the same style
> > of paths:
> > /projects/project-slug/task-name
> > /projects/project-slug/message-name
> > /projects/project-slug/project-name
> > 
> > Wordpress is rewriting all custom post types as /post-type/slug at the
> > moment, so I am not sure if this is achievable.
> > 
> > 3. Some other solution using sessions to set the current project and
> > then relating all queries to that project.
> > 
> > Having written all of that I guess any of those options would do, I'm
> > just not quite able to get a neat and tidy solution out though - any
> > ideas would be appreciated.
> 
> Your need provides a good example use-case for this ticket:
> 
> http://core.trac.wordpress.org/ticket/12935
> 
> On Apr 17, 2010, at 5:31 PM, scribu wrote:
> > To link posts to other posts, I would use a posts2posts table, instead of
> > the taxonomy system: fewer tables => better performance, easier to maintain
> > consistency.
> 
> But that unfortunately requires creating significant admin UI, doesn't it?  Linking posts through the taxonomy system means that at least most of the plugin work can be done as backend code.
> 
> That said, every use case I look at has the need to related posts to other posts so much so that I can't imagine it not being a valuable addition to core. For example, to have a meta box that lets you related a post to posts of another type. Anyone know if there are any trac tickets for this?
> 
> On Apr 17, 2010, at 3:40 PM, Charles Frees-Melvin wrote:
> > I think you are running into a complexity/limitation of WordPress. That a taxonomy cannot have meta.
> 
> I pondered a while back if wp_term_taxonomy shouldn't be deprecated and replaced with a post type of 'term_taxonomy' to which some derided the suggestion. Maybe now that custom post types are more mature considering it might actually make sense?
> 
> -Mike
> 
> ------------------------------
> 
> Message: 8
> Date: Sun, 18 Apr 2010 10:34:56 +0300
> From: scribu <scribu at gmail.com>
> Subject: Re: [wp-hackers] URL structure for web application with wp
> To: wp-hackers at lists.automattic.com
> Message-ID:
> 	<g2s349fe48b1004180034w6fea6416ib36d8964ed05dd50 at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
> 
> On Sun, Apr 18, 2010 at 2:59 AM, Mike Schinkel
> <mikeschinkel at newclarity.net>wrote:
> 
> > On Apr 17, 2010, at 5:31 PM, scribu wrote:
> > > To link posts to other posts, I would use a posts2posts table, instead of
> > > the taxonomy system: fewer tables => better performance, easier to
> > maintain
> > > consistency.
> >
> > But that unfortunately requires creating significant admin UI, doesn't it?
> >  Linking posts through the taxonomy system means that at least most of the
> > plugin work can be done as backend code.
> >
> > That said, every use case I look at has the need to related posts to other
> > posts so much so that I can't imagine it not being a valuable addition to
> > core. For example, to have a meta box that lets you related a post to posts
> > of another type. Anyone know if there are any trac tickets for this?
> >
> 
> It could be made into a sturdy plugin before being added to core.
> 
> 


-- 
James Tarleton <jtarleton at jamestarleton.com>