Is there a module or some sort of native functionality available in Drupal that will allow search filtration by book page? (e.g. limit search to a particular section in the book)
Or some easy way to attach taxonomy to a book using page titles?
I think you need this module http://drupal.org/project/rules, with help of it you can create special set of actions when some action was performed in drupal, in your case this is 'Node created'. For example you can create new taxonomy term from title of a book page and then attach this new term to created page. Try it, Rules module can easy solve many problems like yours.
Related
I'm very new to drupal however what I'm trying to achieve I assumed would be relatively straightforward but finding any documentation on the subject is proving difficult.
I am creating an ecommerce site using ubercart, i have installed this and all of the relevant modules and have created custom product pages with not much hassle. What I need to do is create a 'blog' that's articles can relate to one or multiple products. I have managed to set up the blog with no issues but I am struggling to find out how I can first of all link the story to a product in the product creation process (i.e. when creating a product I can choose a blog article from a list to form a relationship). I have kind of managed to provide this required relationship using the References module. But I have no idea how I can use this relationship to, for instance dynamicall display a list of products related to the current blog article or vice-versa.
I have previously asked a similar question but an still unable to figure this out.
Many thanks.
If the field is attached to the blog content type then you'll have a list of related products automatically outputted in the field display. If you haven't, go to the 'Manage Display' section for that content type and make sure that field isn't hidden.
The References module is only uni-directional currently so you'd have to code a solution for the other way around yourself (not particularly tricky). Alternatively you could ditch References altogether and try the Relation Module which defines bi-directional relationships between entities.
Ok, so my problem is that i'm creating an antiques directory and i need some help in reccomedding the tools i'll need to do the job. I'm ok with programming but fairly basic.
I want a user to be able to search my website for a phrase or choose a category and then return images of the antiques that they entered in my directory.
What things should i be looking at to do this? i.e. wordpress/drupal/joomla and if so what plugins would i need?! Can anyone help?
Thankyou =]
Jamie
If you have the patience to learn Drupal & CCK+Views you would have everything you need in a well customizable package, and most likely it could be done with no programming at all, just configuration.
The way you would do it in Drupal is to create a new content type for your antiques, and attach various fields (image, text, this, that, whatever) using the CCK (Content Construction Kit) Module and it's sub modules. Then you would assign taxonomy terms (categories) to individual Antiques when added.
Finally you would create a View or 2 using the Views module and a few views sub modules to filter on taxonomy term categories (using say autocomplete) and then return said catalog however you please...
check it all out at Drupal.org
Drupal loves you
I need help on how to create a 'custom form' using the same fields provided by cck.
Drupal gives you the ability to add fields to 'nodes' and how to theme their output. But I would like to be able to post a data from my own form (that pops-up) and sends data to the drupal database using the same drupal cck.
How do I access the specific form inputs to add data to my content types ? because the default form is kind of 'ugly' and loads on different page(without ajax).
Help would be much appreciated
There are several routes you could go down.
The easier option is to use the Webforms module. While this gives you similar fields to cck, they are not exactly the same, and if you have a module that implements a specific cck field type, it won't be available to webforms.
The second choice is to write your own module using the forms api. This can mean a lot of learning, add it takes time to get up to speed, but ultimately you have total control over how your form will look and behave. The forms api doesn't give you exactly the same fields, but all the tools are there to create them. Sometimes you need to hack open a module to find out haw a specific field is implemented.
A third option would be to use cck itself. You could create a content type and add the field types you want on your form. You would them give users permission to create but not view or edit the content type. The form submissions would them be nodes on your website. This would make me slightly nervous, so make sure all your permissions are correct!
The second part of your question: you can use a theme file to override the appearance of most forms and make them pretty.
James
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 just getting round to converting our static HTML website to Drupal. Our website is currently structured into sections, each section having a header, then a list of sub-sections below (for an example see http://www.eurosafeuk.co.uk/services/).
This ties in very nicely with Drupal's "book" module, but I need to customise the display of child pages; by default they're printed as an unordered list of page titles, whereas what I need is to output:
A teaser image for each page
The page title
The page summary
I've looked through the .tpl files, and found that the children are stored in a $tree variable (already HTML formatted). My question is: where do I start if I want to modify this? Does anyone know of a pre-existing module that would do it, or do I need to dig into the code?
Instead of using the Book module which is specifically for a book structure, you might want to look into modules that are made for your case. I haven't looked very well but the Node Hierarchy module might be useful for you. . Here is an excerpt from its project page:
... allows nodes to be children of other nodes creating a tree-like hierarchy of content. The module offers:
1-Click creation of hierarchical menus
Hierarchical breadcrumbs
Automatic hierarchical urls using Pathauto (and token module)
(eg: q=aboutus/history/beginning).
Automatic creation of hierarchical menus if desired.
Optional Views integration.
Optional Node Access integration.
If you want to theme nodes in specific sections in different ways, it's probably a good idea to make separate .tpl files for every section. The way you name those .tpl files makes them applicable to nodes in a certain section.
Get the devel module, and turn on theme developer. This will tell you the template or function which is used to build the HTML and what templates you can create to override it.