you are familiar theme of Omega 3? I have just finished creating a sub-theme and I configured the regions that I need on a page suitable for my content type.
I joined two regions, in which I would like the content that I would like to take with php from my content type.
But at this point I lies the dilemma. As with the other themes I used a single page .tpl.php with inside the div block to control the layout now how do I break the contents of the content type in different regions?
Check out Display Suite. You can arrange different parts of your content types into different theme regions.
http://drupal.org/project/ds
Related
I have created two different pages in WP which are using two different templates that I have created. I now want to create a third page in which those two pages are listed underneath each other, but should have the design of the two other templates.
How do I have to create this third template file? If I get the two pages with the get_children() function, I have to reproduce the templates for these two different children pages in my third template. How can I solve this?
Thanks
I'm not sure if this is possible or not, but I'm wondering if when creating a new piece of content (say, an Article), is it possible to show similar pieces of content (which have the same tag(s) as the content you are creating) so that the content creator can pick these items to use as related content.
In other words, it will show related content in the admin view (say, as a list) when you are creating a new piece of content (and not in the normal site view that everyone sees).
The list of related content would need to be ordered by most terms matched.
Thanks, Jamie
Views, similar_by_terms, similar and other modules provide that functionality. See how to create such a block with views at this article http://www.metachunk.com/blog/adding-related-content-view-drupal-7
I am looking to create a 3-column home page design for my site that segregates 3 different items of a given taxonomy type (News, Training Alerts, and Advisories) into 3 separate columns. Each column shows not only the taxonomy term, but pulls the content associated with it (e.g. a teaser view of each item marked 'News').
I am not very familiar with Drupal themes, but currently I have been able to accomplish everything I've wanted with my site using the Bartik theme. Are there any ways I can accomplish this using Views and without having to change much about the Bartik theme? Or alternatively, is there a way to just create a table with PHP code that pulls the content associated with each taxonomy type into each column of a 3-column table?
The simplest way I can think of:
Create 3 separate block displays, one for each term, using the Content -> Teaser output.
Download/enable Blockgroup and create a new block region (called "Front Categories") and place it wherever and assign it to
Put those 3 block displays inside the new block group region in whatever order you would like.
Add some simple CSS to give the blocks an even width, like: .region-blockgroup-front-categories .block-views {width: 33%;}
That should get you about 90% of the way there, if not completely work out for you.
Intro
I am in the process of trying to convert my first HTML/CSS design into a theme for Drupal. I have used ModX for quite a few designs and appreciate the ability to create different page templates and custom variables to be assigned to those templates. However I seem to be having some issues making the transition.
The site I am working on theming in Drupal is for a real estate agent. Each page/section will have a different set of content associated with it and will need to display only that content. For example, there will be a page for current listings, each of which will be formatted by a custom content type. However, when I call the content on the home page (or on other pages) I do not want to see this listing data.
Layout
The layout of the site and the regions associated with each page/section is as follows:
Home
Spotlight
Featured 1
Featured 2
About
Spotlight
Bios - Profiles of each agent (each will be a node with name, contact info, pic, etc) listed on the page; multiple nodes listed
Sidebar
Listings
Spotlight
Listings - Profiles of properties (each will be a node with locations, basic info, pic, etc) listed on the page; multiple nodes listed
Sidebar
Services
Spotlight
Content - general paragraph text area
Sidebar
News/Blog
News/Blog Items - List of stories with summaries and links to full article
Sidebar
Each page/section will use the same header and footer.
Issue
I have done some reading on Drupal, custom content types (and CCK), Views, and Pathauto. However I have not been able to get a clear picture of how to put it all together to accomplish what I am attempting. What I really would like to know is which modules to use, how best to use them, which elements I need to use where, and what template files I should be using to theme the elements I need to use. Any help or reference to useful resources would be much appreciated.
This is a rather general question, and your description is a kind of vague on important distinctions like page vs. site section vs. page region. That said, some general advice: start by installing the admin module. Then get all your content generally in the right places with someone else's theme, e.g. Garland, before you start doing any of your own theming. You should be able to get pretty far without touching code. Use CCK to define your content structure. You should already have a type for page and it sounds like you'll want to add a type for feature, bio, listing, and blog post. Depending on the details, you may need to add some additional field modules, e.g. if you have images, you'll probably want the imagefield module.
Once you have the content types defined, configure pathauto, and start adding content.
Once you have some content, you'll want to create some lists of it with views. You may want to start with the simpleviews module, as the views UI can be overwhelming. Save your views as block display, and then use the blocks admin to put the in the right page region, and configure them to show up only on the right pages.
At that point, you'll want to start controlling how the individual items (nodes) look in different contexts. That's when you start theming. For that, I'd install the devel module, look at what other themes do, and call dsm() on any variables you don't understand to see what they look like.
You can generally get quick help with specific questions on the Drupal IRC channels.
The easiest way to do what you want to do may be to put your custom content in blocks and set the access settings for the blocks to be only on certain pages. So, for instance if you have content that you want to appear at /spotlight or /node/22 or such, you would just create a custom block (Site Building -> Blocks) and then in the settings, set the block to only show for that node.
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.