Differences

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

--- drupal_notes [2008-03-19 16:41] – created 81.188.78.24
+++ drupal_notes [2008-03-31 11:42] – 81.188.78.24
@@ Line 2: / Line 2: @@
 ==== setup on debian ====
   * http://www.debian-administration.org/articles/544
+  * creating the database user: http://drupal.org/getting-started/5/install/create-database/mysql
+=== multisite setup on debian ===
+the drupal5 package installs drupal in /usr/share/drupal5, with config files in /etc/drupal/5. with a multi-site setup, this is the codebase that will be used by all of the sites. in theory it will be updated by the package-manager.
+the following is based on http://drupal.org/getting-started/5/install/multi-site
+to make a new site:
+make a VirtualHost in /etc/apache2/sites-available/new_site
+<file>
+<VirtualHost *>
+        ServerAdmin admin@example.com
+        DocumentRoot /usr/share/drupal5
+        ServerName new-site.example.com
+        <Directory "/">
+               Options FollowSymLinks
+               AllowOverride None
+        </Directory>
+        <Directory "/usr/share/drupal5">
+               Options Indexes FollowSymLinks MultiViews
+               AllowOverride None
+               Order allow,deny
+               allow from all
+        </Directory>
+        ErrorLog /var/log/apache2/error.log
+        LogLevel warn
+        CustomLog /var/log/apache2/access.log combined
+        ServerSignature Off
+</VirtualHost>
+</file>
+then symlink this VirtualHost from /etc/apache2/sites-enabled
+<code>
+cd /etc/apache2/sites-enabled
+ln -sf ../new-site 001-new-site
+</code>
+also you need to make a new site config directory in /etc/drupal/5/sites. the easiest way to do this is to copy the "default" site:
+<code>
+cp -r /etc/drupal/5/sites/default /etc/drupal/5/sites/new-site.example.com
+</code>
+the name of the directory needs to be the domain under which the site will be accessed.
+make sure that both the dbconfig.php and settings.php files are writeable by www-data.
+<code>
+chown .www-data /etc/drupal/5/sites/dbconfig.php /etc/drupal/5/sites/settings.php
+chmod g+w /etc/drupal/5/sites/dbconfig.php /etc/drupal/5/sites/settings.php
+</code>
+before you have a real domain setup, you can edit your /etc/hosts file on your local machine and add an entry that points the domain at the ip address of the server. eg:
+<code>
+.46.38.135 new-site.example.com
+</code>
+//possibly you also need to add this to the server /etc/hosts file???//
+now if you visit the new-site.example.com, it should run the installation script and set up the database.
 ==== themes ====
-  * http://drupal.org/project/Themes
+  * overviews
+    * http://themegarden.org/drupal50/
+    * http://alldrupalthemes.com/
+    * http://drupal.org/project/Themes
+  * theme construction >> http://drupal.org/project/atck
+  * A collection of 'How-to' articles on subjects relevant to theme developers >> http://drupal.org/node/22803
+  * Neem-tree tutorials on themes & theming.. .
+    * http://neemtree.com.au/drupal-theming-designers
+    * http://neemtree.com.au/drupal-theming-designers-continued
+  * theming a particular content type: http://drupal.org/node/17565
+==== modules ====
+  * timeline http://drupal.org/project/timeline
+    * development 5.x release http://drupal.org/node/77900/release
+  * views_multiblock: http://drupal.org/project/views_multiblock
+    * allegedly allows blocks to take arguments from the currently viewed node (eg, taxonomy)
+  * http://drupal.org/project/imagecache (for cropping down thumbnails to squares)
+  * http://drupal.org/project/devel
+  * http://drupal.org/project/image_exact (for cropping down thumbnails to squares.. needs less work than imagecache)
+  * http://drupal.org/project/pathauto (even nicer cleanurls.. based on tag name etc)
+==== tutorials etc ====
+  * some screencasts on CCK/nodereference (building a node out of several other nodes)
+    * http://geoffhankerson.com/drupal
+  * drupal api
+    * http://api.drupal.org/api/5
+  * creating new node types in 5.x: http://drupal.org/node/132845
+    * node_example.module: http://api.drupal.org/api/file/developer/examples/node_example.module/5/source
+    * node_example.install: http://api.drupal.org/api/file/developer/examples/node_example.install/5/source
+  * embedding two views in one view (by putting php in the header.. good trick)
+    * http://drupal.org/node/42599
+    * with paging: http://drupal.org/node/85720
+  * documentation for contributed modules... if something is listed here it's probably a good sign of support.
+    * http://drupal.org/handbook/config/contribmodules
+==== things to find out ====
+  * flickr integration?
+    * special arrangements like our frontpage picture selection idea?
+    * http://www.lullabot.com/articles/how_to_build_flickr_in_drupal
+    * module that uploads to flickr and drupal at the same time: http://drupal.org/project/flickrup
+      * how to get the flickr filter working?
+  * how to do lists of related links
+    * will they be made manually? or based on tags? or...
+    * views?
+    * and only have them show up on the correct pages
+      * block configuration? if the pages have urls that can be selected with a wildcard, then it will be easier.
+    * about tags: http://drupal.org/handbook/modules/taxonomy/
+    * "Displaying related nodes using Views and Contemplate" > http://drupal.org/node/134320
+  * what is cck? ;)
+    * http://drupal.org/project/cck
+    * 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/pager.inc it looks like no.
+    * 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 /files/imagecache/NAMESPACE/FILENAME
+    * from the imagecache README.TXT: <code>print theme('imagecache', $ruleset_namespace, $image['filepath'], $alt, $title, $attributes)</code>
+  * can a normal image_gallery work with a non "image gallery" tag?
+    * yes, /gallery/tid/XX where XX is the id of the tag.
+    * 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't the devel module tell you this stuff?)
+    * <code>select * from node join term_node where node.nid=term_node.nid and tid=63;</code>
+    * <code>select * from node join term_node, term_data where node.nid=term_node.nid and term_node.tid=term_data.tid and term_data.name="xmedk";</code>
+    * nicer: <code>select * from node join term_node on  node.nid=term_node.nid join  term_data on term_node.tid=term_data.tid where term_data.name="xmedk";</code>
+  * 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://drupal.org/project/nodehierarchy
+      * http://drupal.org/project/taxonomy_breadcrumb
+  * manually setting the teaser breakpoint: http://drupal.org/node/176829
+  * 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/settings/site-information
+==== delta specific ====
+=== questions ===
+  * should there be a name_of_activity:potential_projects ?
+  * 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't turn up in the list of "related" things under the overview text.
+  * what type will "normal" nodes be? will they all include related images etc?
+    * maybe most things should be overview nodes?
+      * but don't show striking/overview images if they are not available.
+        * 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 ===
+  * "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.
+  * A workshop is an Event node with type_of_activity:workshop tag.
+  * an "Event Series" is actually an Overview node, with a type_of_activity:event tag.
+  * There exists both a Event node type and an type_of_activity:event tag.
+    * an Image node, for example may be tagged with type_of_activity:event.
+  * 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 "submitted by xxx" is controlled in the global theme settings, i have turned it off on most pages
+    * http://delta.fo.am/admin/build/themes/settings
+  * 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't have to match, just the text of the names.
+  * story pages..?
+  * section overview images?
+  * events should pull in images too?
+== 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.