[wp-hackers] Enhance WP to use page categories

[ryan fitzer]

Count me interested!

Ryan

On 1/24/07, Mike Purvis <mike at uwmike.com> wrote:
>
> I would implement this in terms of the hierarchy.
>
> You could a have a base page with a slug like "/private/" so that
> pages like "/private/secrets" would be inaccessible. You'd just have
> to have a plugin that ran at boot time and dumped you to the login
> screen if you didn't have authorization to view the given stem.
>
> As for the question about static pages, it's fully possible to wrap
> your theme around *any* content you like, even dynamic stuff, or
> something you wouldn't want to enter through the editor. For example,
> we have source code views that look like this:
>
> http://googlemapsbook.com/chapter6/onResize/map_functions.js.source#l6-10
>
> If you strip off the ".source" portion, it displays a plain JavaScript
> file sitting on the server. But ".source" funnels it into a Wordpress
> plugin page that shows the arbitrary content---in this case,
> prettily-rendered source code.
>
> If there's general interest in how to do this, I'd be happy to publish
> a tutorial.
>
> Mike
>
>
> On 1/21/07, Chris <chris.hearn01 at ntlworld.com> wrote:
> > Hello,
> > Wordpress has expanded from a straight blog app. to include the very
> > useful static pages etc. This seems to me (a newbie to Wordpress, but
> > experienced in PHP/MySQL etc) to allow the opportunity to create
> > complete web-sites which have a consistent theme throughout, many static
> > pages, and _part_ of the site includes blog/news and comments etc. This
> > would make Wordpress a really useful and more generic tool!
> >
> > However, it does not seem possible to categorize pages so that there is
> > a "public view" accessible to all, and a "members" view, which might
> > include the public view, but also show more restricted pages.
> > In $wpdb the wp_posts.post_category is only used for posts at present
> > (and in version 2.1???) - could it also be used for page categories?
> > A solution might be to create categories for the static pages (e.g.
> > public, members), and then give menus of pages based on status of
> > logged-in/not logged in.(i.e. the page category)
> >
> > Has this already been done? Is there any change in 2.1 that would render
> > this idea incompatible? (as I wish to implement it for a club website I
> > am building)
> > Thanks
> > Chris
> > --
> >
> >
> **********************************************************************
> >     Chris Hearn
> >     *Tel:* 01625 827589
> >     *Mob:* 07768 725141
> >     *email:* chris.hearn01 at ntlworld.com
> >
> **********************************************************************
> >     The information transmitted is intended only for the person or
> entity
> >     to which it is addressed and may contain confidential and/or
> privileged
> >     material. Any review, retransmission, dissemination or other use of,
> >     or taking of any action in reliance upon, this information by
> persons
> >     or entities other than the intended recipient is prohibited.
> >     If you received this in error, please contact the sender and delete
> the
> >     material from any computer.
> >
> **********************************************************************
> >
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> >
>
>
> --
> http://uwmike.com // http://googlemapsbook.com
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>



-- 
Ryan Fitzer
Dallas, TX
http://www.ryanfitzer.com