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.
Related
New to Drupal. Installed it, set Bartik theme as default, created a few pages with a menu. Now I would like to do something like this:
where the pictures with descriptions link to either other pages or articles. Each of them should have custom size.
What is the simplest way to do it?
For the testing I have created 4 articles on my home page, but obviously they sit one on top of each other. The same happens when I add blocks.
There is not better option to this than to install and use Views module. You can achieve exactly what you want using the nice UI it provides.
You need Views if
You like the default front page view, but you find you want to sort it differently.
You like the default taxonomy/term view, but you find you want to sort it differently; for example, alphabetically.
You use /tracker, but you want to restrict it to posts of a certain type.
You like the idea of the 'article' module, but it doesn't display articles the way you like.
You want a way to display a block with the 5 most recent posts of some particular type.
You want to provide 'unread forum posts'.
You want a monthly archive similar to the typical Movable Type/Wordpress archives that displays a link to the in the form of "Month, YYYY (X)" where X is the number of posts that month, and displays them in a block. The links lead to a simple list of posts for that month.
P.S - Views module is the most used and installed module in Drupal, hence, it will be a part of Drupal 8 core.
I have a Wordpress-blog with gift ideas where I write text based articles. I recently discovered Custom Post types which I believe is the solution to an feature I want to create.
What I want:
Be able to tag each custom post using the normal "Categories" and "Tags".
Create a 3x3 matrix with product images (custom posts) to be shown on top of each Category-view or Tag-view (followed by the typical article list in the category or tag).
Example:
Lets say I have a category "Gifts for mom" and tags "Pink", "Cheap"
In the category "Gifts for mom" I have 10 text articles (normal posts) discussing the difficulties of buying gifts for your mom
I create nine custom posts, each is a specific gift (e.g. A pink hairbrush). I want to place them in the Category "Gifts for mom" and tag them with "Pink".
When I view myrandomgiftblogname.com/category/gifts-for-mom I want to be able to get a view:
Gifts for mom
Product Product Product
Product Product Product
Product Product Product
Articles:
- This awesome article
- That awesome article
- Etc
I assume this is possible but don't really know where to begin. Could you point me in the right direction? Which Plugins do I need? Do I need to do any programming myself (or just plugin configuration)? Is this even possible?
The description is a bit broad, hence a bit broad answer.
Two things are needed:
1) A plugin to create the Custom Post Type.
It is considered best practice to let CPT's in Plugin territory. So you can swap designs and preserve your CPT functionality. In reality, you are asking for future problems letting this be handled by the theme.
Create your own plugin, which would contain a register_post_type and any extra configs.
Use an existent plugin, like Custom Content Type Manager.
Its Custom Fields features are quite handy as well.
Allows users to create custom content types (also known as post types) and standardized custom fields for each, including dropdowns, checkboxes, and images.
2) Learn how to use and customize WordPress Templates
http://codex.wordpress.org/Templates
Templates are the files which control how your WordPress site will be displayed on the Web. These files draw information from your WordPress MySQL database and generate the HTML code which is sent to the web browser. Through its powerful Theme system, WordPress allows you to define as few or as many Templates as you like all under one Theme. Each of these Template files can be configured for use under specific situations.
You can try the following:
Add a new Page for each category with the exact same name as the category.
In the Images menu attach to each of those pages the images you want.
In your script query for a page with a name identical to the current category, and pull all of its attachments
I'm attempting to build module that allows a user access to manage jobs/departments and post them to our website. It will also allow end users to apply for a given position.
The hierarchy is as follows:
About Us Page (standard drupal page)
-Careers (overview with list of all openings)
-Department Pages (if one or more jobs are available, they'll be displayed here)
-Individual Job posting with form to submit resume
I am currently using two custom tables for jobs and departments.
I have all the administration (CRUD) stuff working just fine -- my question lies in the 'drupal' way of integrating the department pages and individual career pages.
Should I create a custom content type that stores all the job/department data in the node? Or should I keep with my custom tables and integrate with the Path module to setup all the department pages and the application page? Also, what would be the best way to integrate the job application form into the module?
I appreciate any help!
You could create a custom node type for jobs and then create a taxonomy vocabulary for careers with terms for departments inside it so that you can then assign the taxonomy terms to a job. That would be very quick and easy to do.
This also means that you could output nice categorised breadcrumbs using the Custom Breadcrumbs module. Custom Breadcrumbs contains a submodule called Custom Breadcrumbs Taxonomy so you could output career/department information in the breadcrumbs.
You could also use Pathauto to output nicely structured SEO friendly URLS using this method.
Edited to say that with this method you could use Views to show taxonomy term specific lists simply by enabling the taxonomy term View, so you could show all openings at www.example.com/careers and all departmental openings at www.example.com/careers/department-name.
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.
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.