Posted by jbernat on July 15, 2005 at 12:59am
I have been experimenting with Flexinode, but noticed that my taxonomy categories are not available for selection on the content form of a Flexinode content type. Is there a way to enable taxonomy support on a Flexinode instance, or must I use a page?
Thank you,
Jim Bernatowicz
jim.bernatowicz.net
Comments
Categories
administer --> categories // edit vocabulary .... and then check off the boxes for the nodes the vocabulary should apply to. That's it.
===
Laura
pingV
_____ ____ ___ __ _ _
Laura Scott :: design » blog » tweet
What if there's a lot of categories? e.g. thousands?
I just asked about dynamically generating a hierarchy: http://drupal.org/node/26792
I suppose from your answer that I could instead make categories for each of the hierarchy places I'm thinking of. However in my case the hierarchy is geographical: continent,country,province,city from all over the world. My current database has 8000 entries with a geographical hiearchy over it to match.
David Herron - http://7gen.com/
- David Herron - 7gen.com/, davidherron.com/drupal-blogging-hints
A lot of work, but it would work
And you could navigate it using taxonomy_dhtml.
===
Laura
pingV
_____ ____ ___ __ _ _
Laura Scott :: design » blog » tweet
Simple and Elegant. Thank you.
Laura,
Thank you for your help! Worked like a charm.
I also took an opportunity to visit your site (pingV) and I was quite impressed with what you've produced.
I have been trying to figure out how to have completely different layouts from one page to another in a single Drupal installation. (Example: Each of the main tabs on drupal.org have significantly different layout, and I would love to know how this was achieved.)
Right away I took notice of what you had done with pingV. For example, your navigation menus on the right are context-sensitive and your main content pane has a very different structure in a blog vs. a comment page.
If you do not mind, I'd like to ask how you did a few things... :)
I suspect you may have themed a Flexinode to achieve the different formats of the main content pane. True? This was one reason I have been looking at Flexinode.
How did you achieve the context-sensitive nature of the right nav? Is it simply a matter of using a wildcard in the blocks' Page specific visibility settings?
I also noticed that your urls have very well-defined structure. For example, about and service pages appear in '.../about/' and '.../services/'. Do you manually maintain these conventions using path alias, or is Drupal doing this for you? Do you have custom modules called about and services? (Guessing based on the way the forum and blog module have '.../forum/' and '.../blog/' in them.
Thank you for your time and assistance.
Jim Bernatowicz
jim.bernatowicz.net
Jim Bernatowicz
Thanks for the compliments
To answer your questions, the context-sensitive blocks are configured in the admin-blocks area. We also used flexinode, books, pathauto and taxonomy to do the other stuff. phpTemplate gave us the easy ability to make different posts appear in different styles.
If you have more questions, feel free to contact me through here or there. Thanks again! Always nice to hear nice things about one's work.
===
Laura
pingV
_____ ____ ___ __ _ _
Laura Scott :: design » blog » tweet
It would be great if you
It would be great if you could answer his question (more fully), and preferably here rather than at your site, so other Drupal users can benefit.
OK
===
Laura
pingV
_____ ____ ___ __ _ _
Laura Scott :: design » blog » tweet
Answering in more detail
I suspect you may have themed a Flexinode to achieve the different formats of the main content pane. True?
Yes. I created some custom node types and then themed them specifically using node-flexinode-x.tpl.php files. (This relates to phpTemplate-powered theming only. If you're modifying one of the default themes, I do not believe this approach would work.)
How did you achieve the context-sensitive nature of the right nav?
The books navigation block will do this for you if you pull your posts into a books hierarchy.
Is it simply a matter of using a wildcard in the blocks' Page specific visibility settings?
Books are always shown only when a book node is being displayed. That's default. The other display settings are set using the basic settings available under admin->blocks->//configure. The handbooks talk in detail about how this works, but the on-screen help on the configure pages seems pretty clear.
I also noticed that your urls have very well-defined structure.
That was done using pathauto module, which I would recommend on all but the most highly trafficked sites. (It does seem to put a small hit on performance that can add up if you're getting thousands of hits a day.) You can rewrite paths automatically for each node type, each category and each user. This also plays well with the block configurations, so you can set conditional display of sidebar blocks based on your rewritten path urls.
As for different entire page displays, there's a sections module people have liked. I have simply placed conditionals at the top of the page.tpl.php template to point to a different page template based on conditional criteria. For example:
<?phpif (arg(0)=="admin") { include('page-admin.tpl.php');
return;
}
?>
This allows me to create a separate page-admin.tpl.php template.
I hope this is helpful.
===
Laura
pingV
_____ ____ ___ __ _ _
Laura Scott :: design » blog » tweet
Very helpful - thanks!
Very helpful - thanks!