This website is composed of information connected through taxonomy. It is simultaneously a proof-of-concept and a means to allow Agaric to share and store information both within the collective and the world as part of our open documentation philosophy.

User login

This website is composed of information connected through taxonomy. It is simultaneously a proof-of-concept and a means to allow Agaric to share and store information both within the collective and the world as part of our open documentation philosophy.

Typical Agaric Customer Service

Here's the bulk of an e-mail sent to an Agaric customer just tonight, following up on the client's questions about having trouble formatting and such. The questions the client had are probably apparent in our answers to her, as should be our respect for what she is able to understand about the site Agaric built for her:

I found some stray HTML markup:

<strong>.</blockquote>

Here's the bulk of an e-mail sent to an Agaric customer just tonight, following up on the client's questions about having trouble formatting and such. The questions the client had are probably apparent in our answers to her, as should be our respect for what she is able to understand about the site Agaric built for her:

<

blockquote>I found some stray HTML markup:

<strong>.</blockquote>

Do non-enabled modules matter?

Agaric wants to know...

can a module that is not enabled harm a Drupal site in any way, by breaking a site if something is wrong in the module or just slowing performance down. Or is a disabled module only relevant on the admin/build/modules page?

In other words, is there any point to keeping modules you are not using out of your modules directories?

Agaric thanks you!

(as posted to http://drupal.org/node/13670 )

Agaric wants to know...

can a module that is not enabled harm a Drupal site in any way, by breaking a site if something is wrong in the module or just slowing performance down. Or is a disabled module only relevant on the admin/build/modules page?

In other words, is there any point to keeping modules you are not using out of your modules directories?

Agaric thanks you!

(as posted to http://drupal.org/node/13670 )

drupal can a disabled module destroy a site
drupal can a not enabled module destroy a site
drupal can a not enabled module break a site

Get a node's taxonomy terms that are in a given vocabulary

well, duh:

taxonomy_node_get_terms_by_vocabulary

(No, I am not making that function name up! This is a function provided by Drupal's core taxonomy module.)

Definition
taxonomy_node_get_terms_by_vocabulary($nid, $vid, $key = 'tid')
modules/taxonomy/taxonomy.module, line 744

Description:

Find all terms associated with the given node, within one vocabulary.

Code:

Inexplicable Access Denied Errors

I'm getting an inexplicable access denied error on the front page page node and a few others.

access denied drupal for full html?
drupal access denied on page don't know why

This assumes that you don't think you have any access control modules operating and don't want access control.

This comment seems to be the way to go:
http://drupal.org/node/128935#comment-212424

I'm getting an inexplicable access denied error on the front page page node and a few others.

access denied drupal for full html?
drupal access denied on page don't know why

This assumes that you don't think you have any access control modules operating and don't want access control.

This comment seems to be the way to go:
http://drupal.org/node/128935#comment-212424

One thing it leaves out, delete all node_access rows in your Drupal database except one.

node_access table to the following

nid 0
gid 0
realm all
grant_view 1
grant_update 0
grant_delete 0

Imagecache images not showing up?

Imagecache images not showing up? Check your /files .htaccess

SetHandler Drupal_Security_Do_Not_Remove_See_SA_2006_006
Options +FollowSymlinks
# None
#
# RewriteEngine off
#

All that stuff commented out? Shouldn't even be there.

Thanks to CogRusty's comments.

Imagecache images not showing up? Check your /files .htaccess

SetHandler Drupal_Security_Do_Not_Remove_See_SA_2006_006
Options +FollowSymlinks
# None
#
# RewriteEngine off
#

All that stuff commented out? Shouldn't even be there.

Thanks to CogRusty's comments.

GIMP Tutorials

These are GIMP tutorials and resources, in addition to the GIMP Tutorials on the official site:

These are GIMP tutorials and resources, in addition to the GIMP Tutorials on the official site:

Using GIMP for editing Indexed Images

Problem: Gradient tool won't work
GIMP remove index channel
GIMP remove indexing
GIMP indexed channel

Some very commonly used types of files (including GIF and PNG) produce indexed images when they are opened in GIMP. Many of GIMP's tools don't work very well on indexed images–and many filters don't work at all–because of the limited number of colors available. Because of this, it is usually best to convert an image to RGB mode before working on it. If necessary, you can convert it back to indexed mode when you are ready to save it

Problem: Gradient tool won't work
GIMP remove index channel
GIMP remove indexing
GIMP indexed channel

<

blockquote>Some very commonly used types of files (including GIF and PNG) produce indexed images when they are opened in GIMP. Many of GIMP's tools don't work very well on indexed images–and many filters don't work at all–because of the limited number of colors available. Because of this, it is usually best to convert an image to RGB mode before working on it. If necessary, you can convert it back to indexed mode when you are ready to save it

Agaric's SVN repository structure for site maintenance and web development

ben@server:~$ cd drupal
ben@server:~/drupal$ svn add drupaldev
svn: warning: 'drupaldev' not found
ben@server:~/drupal$ mkdir drupaldev
ben@server:~/drupal$ mkdir drupaldev/modules
ben@server:~/drupal$ mkdir drupaldev/themes
ben@server:~/drupal$ mkdir vendor
ben@server:~/drupal$ mkdir vendor/drupal-contrib
ben@server:~/drupal$ mkdir vendor/drupal-contrib/modules
ben@server:~/drupal$ mkdir vendor/drupal-core-5
ben@server:~/drupal$ mkdir vendor/drupal-core-5/5.1
ben@server:~/drupal$ svn add drupaldev

<

blockquote>ben@server:~$ cd drupal
ben@server:~/drupal$ svn add drupaldev
svn: warning: 'drupaldev' not found
ben@server:~/drupal$ mkdir drupaldev
ben@server:~/drupal$ mkdir drupaldev/modules
ben@server:~/drupal$ mkdir drupaldev/themes
ben@server:~/drupal$ mkdir vendor
ben@server:~/drupal$ mkdir vendor/drupal-contrib
ben@server:~/drupal$ mkdir vendor/drupal-contrib/modules
ben@server:~/drupal$ mkdir vendor/drupal-core-5
ben@server:~/drupal$ mkdir vendor/drupal-core-5/5.1
ben@server:~/drupal$ svn add drupaldev
A drupaldev
A drupaldev/modules

Setting up a new Drupal site or upgrading from command line

Drupal untar tar.gz using ssh:

cd /var/www/

wget http://ftp.osuosl.org/pub/drupal/files/projects/drupal-5.1.tar.gz

(Drupal version is just a for-instance.)

tar -xzvf drupal-5.1.tar.gz

cp -r drupal-5.1/* drupaldev/

cd drupaldev/sites/

The following applies if you have a subversion repository set up in which you keep your sites projects.

(A lot of redundancy in the paths here but quit yer whining.)

Drupal untar tar.gz using ssh:

cd /var/www/

wget http://ftp.osuosl.org/pub/drupal/files/projects/drupal-5.1.tar.gz

(Drupal version is just a for-instance.)

tar -xzvf drupal-5.1.tar.gz

cp -r drupal-5.1/* drupaldev/

cd drupaldev/sites/

The following applies if you have a subversion repository set up in which you keep your sites projects.

(A lot of redundancy in the paths here but quit yer whining.)

Using the New Server

New databases should be created for different sites, unless there is there is even the remotest chance the sites will be related. If the sites are for potentially related projects, we should put them in one database to facilitate single-sign-on.

New databases should be created for different sites, unless there is there is even the remotest chance the sites will be related. If the sites are for potentially related projects, we should put them in one database to facilitate single-sign-on.