drupal

[phpwiki]
It is my pleasure to announce the first release of myVocs box, an integrated collaboration platform. myVocs box is a virtual machine that delivers the technologies that drive myVocs.org wrapped up in a
self-contained system that's ready for you to enjoy.

Please visit http://myvocs-box.myvocs.org for details on the three simple steps to download, run, and enjoy a collaboration platform of your own.

The technologies in this release of myVocs box include:

* A complete Shibboleth 1.3 identity system (IdP and SP)
* Simple collaboration group setup and management via Sympa
* Flexible resource integration powered by YubNub

the myVocs demo went well and along with Jim's work, seems to make a very nice system environment. struck again how clearly bogger.com, technocati's and del.icio.us have the potential to become the major new applications of you desktop with these technologies. amazing to see the type of system experience that can be defined with so many interfaces available. interesting trend graphs to namespace creation and management.

am working on getting the demo in an on-line followable version and will add a link when I ha

[phpwiki]
been looking into the updates that would be needed to support folksonomy in drupal, known as free tagging. i like the idea of letting the end user determine the vocabulary for entries. I looked at the [drupal support for tagging|http://drupal.org/node/20936]. it really needs it to allow end-user control over vocab. from the description of the features, though, it seems like it needs some work to add features. i'd like to get the [wordpress features jim described|https://mywebspace.wisc.edu/jamesphelps/web/WordPress/wordpress_folksonomy.html] because in order to use tags in a meaningful way, you really need to have a list of popular tags to choose from or reference.

i don't understand why drupal separates comments out as a distinct
content type. it seems like it would be better to consider everything as
a node, ie. inherited from a node type. this would potentially enable
a common display framework with different renders. it also seems like
having all node type be identically defined, that is no second class
types, would help make the content rendering easier. eg. the node table
types would be anything defined by the taxonomy and the base set could
be the standard story, blog, page, etc. types. the legit content would
the simply be defined by the type tag. additional tables could be used

ha. since my first drupal msg. with administrator account went to /dev/null I had no way to log in. I deleted the record (for user 1) and created a new account - but no administrative permissions because I was now user 2. I now seem to recall having selected some unique key autoincrement thingy. Wound up exporting the table to a file, editing file by hand to force myself back to user 1, dropped all records in the table, then edited the file to leave only "INSERT" instructions behind, then imported the file which is done under the SQL tab.

[phpwiki]
review how to deal with lab-subscribed groups by individuals

a few problems with this: I want a forum block to tie in specific forum to
a project page; don't seem to be able to restrict no comments on such
forums to prevent responses (or posts) from anyone but the gateway, eg.
must post to mailling list not forum; would be nice to just have a web
interface to news groups, eg. don't delete the messages out of a backend
subscribers folder. don't take them to the web, show them on the web.

working on understanding xtemplate and tools like quanta. the background
image was adequate but needed(s) to be lightened, certainly the green
squares.

remember now that i've seen the xtemplate.inc that this is based on a
generic php templating engine. understanding that should help. see
xtemplate at sourceforge. it draws it's ideas from another template engine
called quicktempalte.

the basic approach seems to have a temptlate html layout that contains
variable names that are then defined with content.

seems to go like this. each object type on the page has a name, eg. node.

http://drupal.org/book/print/274

how to do multiple sites in drupal, also good for clean site nameing. just
name the config file with your site name, eg: http://mysite.org/subir
would have the config file includes/mysite.org.subdir.php

wanted to add blogs to the /project/project-name pages so that they would be listed also, since these are likely (hopefully) to be a good source of daily project progress.

the fix turned out to be easier when the problem was recognized. the project page script already gets all the nodes for a named project, it then sorts them by type. for user-defined types we need to trim down the node list to only those tagged with the specific user defined type. for a core type, like blog, we don't need the extra queries since the type is embedded right in the node table. we can go right to selecting the "blog" subset of project nodes.

drupal 4.4.0 has been released. reviewed the module list. looks like they've updated all modules for 4.4. this includes the listhandler, which is what i'm interested in. there are a number of other interesting modules including an update to the wiki module, a groups module, and others i've reviewed.

would probably be good to keep this testing on a separate site. will ultimately require importing to cvs and migration of main site