Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
delta_notes [2008-05-20 15:04] – 81.188.78.24delta_notes [2008-09-07 12:13] (current) – 81.188.78.24
Line 1: Line 1:
 ===== delta.fo.am specific drupal notes ===== ===== delta.fo.am specific drupal notes =====
- 
- 
  
 ==== questions ==== ==== questions ====
Line 17: Line 15:
   * how to associate images with an individual node (eg, an event) without needing to make a new tag?   * how to associate images with an individual node (eg, an event) without needing to make a new tag?
   * where do attachemnts for biblio nodes end up, and is it possible to have a URL alias defined for the attachment.   * where do attachemnts for biblio nodes end up, and is it possible to have a URL alias defined for the attachment.
 +  * what type of node should 'fieldwork' be, and how to provide an overview (ie. 'Overview' vs. 'Section')? should a 'Seciton' node include related 'Article' nodes based on type_of_activity? 
  
 ==== factoids ==== ==== factoids ====
 +  * Most pages should be 'Overview' nodes. The content type 'Overview' is used to make pages that include, or reference other content (eg. images/related projects,etc+)
   * "Productions" page will list all Overview nodes with type_of_activity:Productions tagged with a root term from the name_of_activity vocab.   * "Productions" page will list all Overview nodes with type_of_activity:Productions tagged with a root term from the name_of_activity vocab.
   * Overview nodes will list/link Overview pages tagged child terms of their name_of_activity term.   * Overview nodes will list/link Overview pages tagged child terms of their name_of_activity term.
Line 34: Line 34:
     * upcoming and past events     * 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.     * i did this with a node-specific theme.. the events node is node 114. the theme is in node-114.tpl.php.
- +  * publications overview text is implemented as a block. http://delta.fo.am/admin/build/block/configure/block/4
- +
- +
  
  
 ==== todo ==== ==== todo ====
-  * address field in event (needs CSS improvment) +  * decide what to do about forums & comments 
-  * logos on overview pages +  * check 404 & 403 templates 
-  * add the image galleries to correspond to name_of_activity tags (nik) +  * url redirections from old site 
-    * by the way, the heirarchy doesn't have to match, just the text of the names.+  * add link to subscribe to update list 
 +  * display 'related events' on events pages, as seen on the 'overview' pages. 
 +  * sort 'related events' by most recent -> most ancient 
 +  * positioning of teaser images in 'related' section 
 +  * teaser images for events in 'related' section 
 +  * address field in event (needs CSS improvement)
   * prosaic tag block (providing context for a node in terms of how it relates to other overviews, or types of activity)   * prosaic tag block (providing context for a node in terms of how it relates to other overviews, or types of activity)
-  * timezone in event+    * look at the phptest block... you can determine the nid of the current node by inspecting the url path via the arg(x) values 
 +  * improve layout of publication pages 
 +  * when selecting images from a $tid (eg. using 'get_images' in foam.php) check if the gallery has subgalleries, and include their images also. (possibly: http://api.drupal.org/api/function/taxonomy_get_children/5) 
 + 
 +=== done (as of 2008-05-20)=== 
 +  * (probably just for section pages) find out the image gallery that an image is in and add that as the lightbox link. 
 +    * in ''node-section.tpl.php'' 
 +  * events should pull in images.. but from where? 
 +    * there is now a node-event.tpl.php 
 +    * events can be tagged with an image gallery, a selection of images from that gallery will appear at the bottom of the node
   * don't show "upcoming" unless there are actually upcoming events.   * don't show "upcoming" unless there are actually upcoming events.
-  * events should pull in images..  +    * changed in node-114.tpl.php 
-    * from where? +  * timezone in event (check named div & default tz) 
- +    * this change made in ''modules/event/event.theme:theme_event_nodeapi'' 
- +  * logos on overview pages
-=== done ===+
   * images in teaser block   * images in teaser block
   * section overview images?   * section overview images?
     * working in theory but nothing is tagged appropriately?     * working in theory but nothing is tagged appropriately?
   * the problem with tags like "None", is that they appear quite high in the tag cloud. I think any tag that has a "none" option should just not be set required.   * the problem with tags like "None", is that they appear quite high in the tag cloud. I think any tag that has a "none" option should just not be set required.
 +
  
 === would be nice... === === 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. 
   * end date on event should get set to the start date? or maybe only when opening the calendar to allow leaving the second date blank.   * end date on event should get set to the start date? or maybe only when opening the calendar to allow leaving the second date blank.
- +    * the end date doesn't get displayed if it's the same as the start date
- +
  
  
Line 98: Line 106:
 == on a section page == == on a section page ==
  
-//good question. possibly we should determine the gallery that each image belongs to.. in both cases.// +the images link to the image gallery that the image comes from.
  
  
  

User Tools

Page Tools

Site Tools