I have several different content type nodes (videos, image galleries, stories...) that I would like to categorize and create a top-level page that aggregates these nodes. So for example, the top-level page would have teaser thumbnails very similar to the front page view but of course filtered for that topic (like for instance automobiles, and motorcycles would have its own page, etc...).
What is the best way to accomplish this? Taxonomy? Views?
You would use both Taxonomy and Views.
Taxonomy would categorize the content, and Views would allow you to configure the display however you like.
One possibility is having an Argument of a taxonomy term, (example, /path/path/taxonomy-term/index.htm) where taxonomy term is a passed URL argument. This would filter all content to that term.
You could also just rely on the taxonomy system, where content resides at /taxonomy/tid, but I don't think you get much control of the output that way.
You may also want to look into a module like Taxonomy VTN for a drill down list of taxonomy:
http://drupalmodules.com/module/taxonomy-vtn
There are lots of ways to approach this. Personally, I would use Views.
Related
On a taxonomy term page, the taxonomy term info is shown first, followed by related nodes. I want to add a wrapper div around the related nodes (ex. class="related-nodes").
taxonomy-terms.tpl.php controls the display of the taxonomy term's fields, but I'm not sure how the nodes show up. I was thinking about making a node template for the taxonomy and doing something like render($content['nodes']). However, I'm not sure what the $content key would be for the related nodes.
One approach is to enable the Taxonomy term view display (is disabled by default).
In the view config, you can add classes by clicking in Settings of Format option.
Hope it helps.
Regards.
I have a view that displays teasers of content type X (across all topics). Under each teaser, I would like to display links to instances of content type Y that share the topic (taxonomy) of that teaser. This seems like it should be relatively simple, but I'm having a hard time relating the filter criteria to the taxonomy of each line of the View's output rather than the taxonomy of the whole View page.
You can use the Views Field View module to do the trick: https://drupal.org/project/views_field_view
Is there a way (or a plugin) to make a given content type in WordPress (i.e. posts, pages, media, custom post types) act as a taxonomy? I basically want to setup a one-to-many relationship of one item in a given post type to many items of a different type.
So basically, I have a custom post type, call it Authors. I want to use a Post Type rather than a taxonomy because I need a lot more meta data than a taxonomy allows.
I then have another custom post type called Books.
Is there a way to put a box similar to the Categories or Tags metaboxes on the Author write page that display a list of all the books. I can then choose from a list of all the books, thus creating a relationship.
If this doesn't already exist, I guess I'll write a plugin for it. I thought I'd give this a try first, just in case.
Have you considered adding new meta fields to a custom taxonomy? Unfortunately, you ned to either create a new table for the meta storage or use wp_options, but it does work and is relatively future-friendly. Remember to start your option names with an underscore, though.
http://www.strangework.com/2010/07/01/how-to-save-taxonomy-meta-data-as-an-options-array-in-wordpress/
I'm stuck and need your help!
Setting:
I have a Drupal 6 website and activated the view for taxonomy term pages.
On my website a taxonomy page is composed of several different content types.
All the different content pieces are tight together by the shared taxonomy term and displayed by the taxonomy view.
Problem:
When searching for keywords, I just want the taxonomy pages to show up. All other content types should not be displayed. How do I do that?
Thx 123kit
There are different ways to do search in Drupal. The simple ones, for sites without lots of content is just use the built in search with Drupal, or build a view with exposed filters.
If you do the latter you are able to decide what is searchable, so you can make a search page for taxonomy terms only, one for articles etc. I'm not sure what exactly you want to be searchable, but if it's not too complex. it should be doable by setting up a view and using exposed filters.
I'm thinking about using WP custom post types to create a basic real estate website.
The post type will be for property listings. I've decided to have one post type for For Sale and one for Rentals, simple because they have somewhat different property information.
A typical listing will need to specify some information, ie, is it a house, an apartment or maybe it's just a piece of land.
What are the pros and cons of specifying this info using custom fields (meta data) versus using taxonomy (categories and tags)?
I can see that it's easy to search based on taxonomy, but custom post types meta data can also be queried.
Also, it seems that this question applies to any post data where discrete choices are required: meta data checkbox, select or taxonomy.
Any thoughts?
Thanks.
My preference for what you're trying to do would be taxonomy for the following reasons:
SEO and User Friendly URLs
With categories and tags, WordPress permalinks are setup to put that information in the URL for you. This will go a long way towards the SEO and usability of your site because you'll be able to create URLs like:
http://yoursite.com/rentals
http://yoursite.com/for-sale/two-bedroom/123-fake-street
Hierarchy
I don't know if you have the need for it, but building a hierarchy with categories is easy. This will give you lots of flexibility when it comes to organizing your posts.
Theme Coding
As you said, it's possible to perform custom queries for meta data, but WordPress has many out-of-the-box functions to query and display based on tags and categories. This will mean that you'll have to write less code to get your theme to do what you want.
I've done exactly what you are talking about, both ways (using Custom Fields versus Categories). My view is you should use a mix - use Categories for the most important information (eg For Sale, Type of Property etc) and use Custom Fields for the actual data for the listing.
Wordpress then has many built in functions to organise that data in a really intuitive way, and allows you to easily group properties of the same type together, in exactly the way a user wants to browse the data.