Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revisionLast revisionBoth sides next revision | ||
drupal_notes [2008-03-20 14:00] – 81.188.78.24 | drupal_notes [2008-03-31 13:18] – 81.188.78.24 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | |||
- | |||
==== setup on debian ==== | ==== setup on debian ==== | ||
* http:// | * http:// | ||
- | |||
* creating the database user: http:// | * creating the database user: http:// | ||
Line 73: | Line 70: | ||
now if you visit the new-site.example.com, | now if you visit the new-site.example.com, | ||
+ | |||
==== themes ==== | ==== themes ==== | ||
- | * overviews | + | * overviews |
+ | * http:// | ||
* http:// | * http:// | ||
* http:// | * http:// | ||
- | * theme constructatron | + | * theme construction |
+ | * A collection of ' | ||
+ | * Neem-tree tutorials on themes & theming.. . | ||
+ | * http:// | ||
+ | * http:// | ||
+ | * theming a particular content type: http:// | ||
+ | |||
+ | |||
+ | |||
==== modules ==== | ==== modules ==== | ||
* timeline http:// | * timeline http:// | ||
* development 5.x release http:// | * development 5.x release http:// | ||
+ | * views_multiblock: | ||
+ | * allegedly allows blocks to take arguments from the currently viewed node (eg, taxonomy) | ||
+ | * http:// | ||
+ | * http:// | ||
+ | * http:// | ||
+ | * http:// | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ==== tutorials etc ==== | ||
+ | * some screencasts on CCK/ | ||
+ | * http:// | ||
+ | * drupal api | ||
+ | * http:// | ||
+ | * creating new node types in 5.x: http:// | ||
+ | * node_example.module: | ||
+ | * node_example.install: | ||
+ | * embedding two views in one view (by putting php in the header.. good trick) | ||
+ | * http:// | ||
+ | * with paging: http:// | ||
+ | * documentation for contributed modules... if something is listed here it's probably a good sign of support. | ||
+ | * http:// | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
Line 91: | Line 130: | ||
* flickr integration? | * flickr integration? | ||
* special arrangements like our frontpage picture selection idea? | * special arrangements like our frontpage picture selection idea? | ||
+ | * http:// | ||
+ | * module that uploads to flickr and drupal at the same time: http:// | ||
+ | * how to get the flickr filter working? | ||
* how to do lists of related links | * how to do lists of related links | ||
* will they be made manually? or based on tags? or... | * will they be made manually? or based on tags? or... | ||
Line 96: | Line 138: | ||
* and only have them show up on the correct pages | * and only have them show up on the correct pages | ||
* block configuration? | * block configuration? | ||
+ | * about tags: http:// | ||
+ | * " | ||
* what is cck? ;) | * what is cck? ;) | ||
* http:// | * http:// | ||
+ | * for making structured kinds of content... but what is the structure of our content? | ||
+ | * can you link to the page of a paged view that contains a particular node? | ||
+ | * looking at the code in includes/ | ||
+ | * would this work with an image gallery? | ||
+ | * seems to use the same pager code. finding this out would require an extra query from the database. | ||
+ | * how do you use imagecache? | ||
+ | * it normally seems to need custom theming, but you can access the generated pics at / | ||
+ | * from the imagecache README.TXT: < | ||
+ | * can a normal image_gallery work with a non "image gallery" | ||
+ | * yes, / | ||
+ | * but since galleries can't really be included in anything else (views, panels etc) they are kind of useless. | ||
+ | * how would i do a view-like taxonomy query in mysql? (doesn' | ||
+ | * < | ||
+ | * < | ||
+ | * nicer: < | ||
+ | * how do breadcrumbs work? are they like a back button, or is there some other hierarchy? how is it defined? | ||
+ | * seems that they are set by modules. there are a few different ways of doing it. | ||
+ | * it looks like the menu defines breadcrumbs by default..? | ||
+ | * http:// | ||
+ | * http:// | ||
+ | * manually setting the teaser breakpoint: http:// | ||
+ | * what happens when you upload two images with the same name? | ||
+ | * the clash gets resolved automatically _0 (etc) is appended. | ||
+ | * where do you set the front page? | ||
+ | * admin/ | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ==== delta specific ==== | ||
+ | |||
+ | === questions === | ||
+ | * should there be a name_of_activity: | ||
+ | * there should be some tag to differentiate between internal events (workshops) and other events. where internal events are not displayed in upcoming events (eg, residencies). | ||
+ | * overview images: should all of the images take you to a gallery, where images are viewed with lightbox? | ||
+ | * eg, images shouldn' | ||
+ | * what type will " | ||
+ | * maybe most things should be overview nodes? | ||
+ | * but don't show striking/ | ||
+ | * how to link to non-overview images in that case? | ||
+ | * where have all of the links for authenticated users come from? it looks like some module breaks something. | ||
+ | * a special node type for section pages or do them manually? | ||
+ | * the query is mentioned in the first factoid below. | ||
+ | |||
+ | === factoids === | ||
+ | * " | ||
+ | * Overview nodes will list/link Overview pages tagged child terms of their name_of_activity term. | ||
+ | * A workshop is an Event node with type_of_activity: | ||
+ | * an "Event Series" | ||
+ | * There exists both a Event node type and an type_of_activity: | ||
+ | * an Image node, for example may be tagged with type_of_activity: | ||
+ | * Overview nodes should only have one name_of_activity tag. | ||
+ | * Section nodes should only have one type_of_activity tag. | ||
+ | * there should be no two Overview nodes with the same name_of_activity tag. | ||
+ | * there should be no two Section nodes with the same type_of_activity tag. | ||
+ | * the display of " | ||
+ | * http:// | ||
+ | * EventOverview | ||
+ | * upcoming and past events | ||
+ | * i did this with a node-specific theme.. the events node is node 114. the theme is in node-114.tpl.php. | ||
+ | |||
+ | === todo === | ||
+ | * logos on overview pages | ||
+ | * add the image galleries to correspond to name_of_activity tags (nik) | ||
+ | * by the way, the heirarchy doesn' | ||
+ | * story pages..? | ||
+ | * section overview images? | ||
+ | * events should pull in images too? | ||
+ | * prosaic tag block | ||
+ | * the problem with tags like " | ||
+ | |||
+ | == would be nice... == | ||
+ | * (probably just for section pages) find out the image gallery that an image is in and add that as the lightbox link. | ||