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.

Capitalize TRUE, FALSE, NULL per Drupal coding standards?

Are true and false PHP keywords capitalized in Drupal coding standards?

Yes.

TRUE, FALSE, NULL

Agaric doesn't have the citation, but we're pretty sure.

Are true and false PHP keywords capitalized in Drupal coding standards?

Yes.

TRUE, FALSE, NULL

Agaric doesn't have the citation, but we're pretty sure.

Backup solution for iBook, external hard drives, and more

Agaric, in particular myself, whose life is on a 60GB hard drive in this iBook, wants a more redundant, easier backup solution, badly.

Willing to pay to get this set up, and maybe offer the service to others...

back up my Mac to Linux RAID

http://sitening.com/blog/2006/05/23/how-to-backup-your-mac-intelligently/

Tyler Hall Says:

June 12th, 2006 at 11:02 pm

Renegade,

Removing node types from a vocabulary: what happens to terms?

What happens to the terms on nodes of a given node type when you remove that node type from their vocabulary?

What happens to the terms on nodes of a given node type when you remove that node type from their vocabulary?

Invisible characters causing parse errors

Two invisible characters.. the first two characters in the row with "return deb_result..." -- yeah, can you see them? -- gave a parse error on that line until I switched the editor to show invisible characters and deleted whatever they were. That was a half hour I did not have.

Two invisible characters.. the first two characters in the row with "return deb_result..." -- yeah, can you see them? -- gave a parse error on that line until I switched the editor to show invisible characters and deleted whatever they were. That was a half hour I did not have.

/**
* The need for this will go away in Drupal 6
*
*/
function cmt_db_last_insert_id($table, $field) {
switch ($GLOBALS['db_type']) {
case 'mysql':
case 'mysqli':
return db_result(db_query('SELECT LAST_INSERT_ID()'));
break;
// from http://api.drupal.org/api/file/includes/database.pgsql.inc/6/source

Category paths will be determined not by voting on each path in total, but by the sum of its parts

In Community-managed taxonomy, votes for term arrangement are autonomous, not taken as a contextual group.

There are philosophical difficulties with hierarchies, aside from my technical problems. (And I'm not talking about my moral objections to hierarchy in this case, either.)

A term hierarchy, or path, exists as a unit.

First-level > Second-level > Third-level > Term

But we're only recording votes in autonomous steps:

First-level > Second-level
Second-level > Third-level
Third-level > Term

In Community-managed taxonomy, votes for term arrangement are autonomous, not taken as a contextual group.

Representing all hierarchies as sets of linear progressions for a given point in a complex hierarchy- a C programmer's answer

[The answer is most likely here, if I could understand it.]

[The answer is most likely here, if I could understand it.]

TwinStar01: Mornin'
I3IVIIVI: mornin... programming question, been working 24/7, 3 hours left to get code in...
I3IVIIVI: OK, so it's something really basic, and it's taken up a critical 8 or so hours... my brain keeps folding back on itself.
[10:35am] agaric: How do I create an array of all possible hierarchies for a term?
[10:37am] agaric: term A can have n parents, each of which can have n parents, etc. I keep messing with recursion and counting loops and while loops and make a mess out of all of them
TwinStar01: have each term have a linked list (double if you want) where each element is a reference to one of its parents.

Block CSS ID for custom module blocks in Drupal 4.7

drupal 4.7 block id

the ID for that block -- as provided to the theme in a line like this:

<div class="block block-coamod" id="block-coamod-1">

Can be set in a custom module, replacing the delta numbers with whatever text string you want.

Set in the block info part of the hook I think and used in the switch statement deciding what to display.

drupal 4.7 block id

the ID for that block -- as provided to the theme in a line like this:

<div class="block block-coamod" id="block-coamod-1">

Can be set in a custom module, replacing the delta numbers with whatever text string you want.

Set in the block info part of the hook I think and used in the switch statement deciding what to display.

Thoughts at the close of code

Y'all might want to wait for the director's cut of this module...

Yeah, I'm going to try to make CMT really good. It already (pretty much) allows for on-the-fly hierarchical tagging, which is pretty cool. For a number of trusted volunteers, though, you could clean things up with SoC Matthias Hutterer's Taxonomy Manager.

Y'all might want to wait for the director's cut of this module...

Yeah, I'm going to try to make CMT really good. It already (pretty much) allows for on-the-fly hierarchical tagging, which is pretty cool. For a number of trusted volunteers, though, you could clean things up with SoC Matthias Hutterer's Taxonomy Manager.

Still unresolved philosophical/logical issues with the module
I3IVIIVI: you can vote on a terms association with content (node)
I3IVIIVI: you can vote on a name for the term
I3IVIIVI: you can vote on the term's placement in a hierarchy
I3IVIIVI: all independently
I3IVIIVI: So how do we make a term, when only one aspect of its term-ness comes up first?

Always check for "if ($foo = 'bar')" mistakes... red flag, needs ==

Always look for malformed equality statements, that assign rather than compare, when things are going weird. Earlier rather than later. That's the whole lesson for today.

So why is the select statement, that's supposed to prevent this mess below, not working?

SELECT content_id FROM {cmt_term_node} WHERE nid=%d AND tid=%d

Debugging looks all good:

* term Another versus Another
* SELECT content_id FROM {cmt_term_name} WHERE tid=%d AND name='%s'
* Result: Resource id #91
*

Always look for malformed equality statements, that assign rather than compare, when things are going weird. Earlier rather than later. That's the whole lesson for today.

auto_increment columns cannot have a default value

Makes sense I guess...

So this is good:
tid int(10) unsigned NOT NULL auto_increment,

Just make sure you don't have "default '0'" anywhere in there.

You don't want to see this on your site:

Makes sense I guess...

So this is good:
tid int(10) unsigned NOT NULL auto_increment,

Just make sure you don't have "default '0'" anywhere in there.

You don't want to see this on your site:

user warning: Invalid default value for 'tid' query: cmt_install CREATE TABLE joe_cmt_term_data ( tid int(10) unsigned NOT NULL DEFAULT '0' auto_increment, name varchar(255) NOT NULL DEFAULT '', weight tinyint NOT NULL DEFAULT '0' ) /*!40100 DEFAULT CHARACTER SET UTF8 */ in /Applications/MAMP/htdocs/joeaustin/includes/database.mysql.inc on line 172.