Any wordpress/paglines devs
- Thread starter JGBR
- Start date
I am a reasonably experienced dev myself but just can't get over a problem i have:
Basically (im using a framework called platform pro by pagelines) I want when you click a main nav button, that the second nav button (IE below it) goes and pulls all posts and categories under that parent by using the menu system. Obviously this changes as you click through the top menus.
However the current system does not use the menu, it uses the page parent system only instead of calling the menu.
Basically (im using a framework called platform pro by pagelines) I want when you click a main nav button, that the second nav button (IE below it) goes and pulls all posts and categories under that parent by using the menu system. Obviously this changes as you click through the top menus.
However the current system does not use the menu, it uses the page parent system only instead of calling the menu.
Not sure if I understood you correctly - Top level Nav as categories and second level nav the posts within that category?
I don't think thats advisable as its going to create a lot of extra DB queries.
Or is it that pagelines does not use the new 3.0+ menu system?
If you don't have many posts you could redirect pages to posts instead with a plugin:
http://wordpress.org/extend/plugins/page-links-to/
I would probably need to get my hands on the theme and look through the code to offer a more elegant solution.
I don't think thats advisable as its going to create a lot of extra DB queries.
Or is it that pagelines does not use the new 3.0+ menu system?
If you don't have many posts you could redirect pages to posts instead with a plugin:
http://wordpress.org/extend/plugins/page-links-to/
I would probably need to get my hands on the theme and look through the code to offer a more elegant solution.
Don't do it dynamically using some weird AJAX solution when the top-level is clicked on. Just build it normally and have jquery reveal the sub-level.
It does appear that you're using categories and posts wrong though. In the example image all of those links should be pages, not posts.
It does appear that you're using categories and posts wrong though. In the example image all of those links should be pages, not posts.
If you have a high volume of posts and they're all featuring that menu system that menu system will start looking ridiculous.
Have pages for everything, but the blog part of the site. Simple. Everything you're currently trying to achieve with categories can be achieved by just keeping a sensible heirarchy to your pages.
It's also dead simple to explain to the client when handing over if you do it the correct way. You just tell them to use a post if they want a blog post and a page if they want to add a new web page (though normally they shouldn't need to touch this part).
Have pages for everything, but the blog part of the site. Simple. Everything you're currently trying to achieve with categories can be achieved by just keeping a sensible heirarchy to your pages.
It's also dead simple to explain to the client when handing over if you do it the correct way. You just tell them to use a post if they want a blog post and a page if they want to add a new web page (though normally they shouldn't need to touch this part).
Last edited:
Man of Honour
- Joined
- 16 May 2005
- Posts
- 31,297
- Location
- Manchester
As has been said, posts (at least the standard WP post type) shouldn't be used for anything but blog posts. For static pages, you should be using....pages.
The only crafty thing about it is that it's the correct way to do things in WP.
The only crafty thing about it is that it's the correct way to do things in WP.
