Drupal 4.7.x

I just would like to create a topic to discuss this feature request.

Looking at the latest version of drupal 4.7b3, there are two relationships among terms: relatedness and synonymy. Since 4.7 appears to support tags and possibly user-defined keywords, I think the notions of relatedness and synonymy should be analyzed very carefully.

First on relatedness, I think this feature is currently implemented "correctly". That term A is related to terms B and C implies terms B and C are related to A. But B is not assumed to be related to C.

On synonymy, I think this notion must be rectified by Drupal before it can be applied effectively to a loosely (user-) defined folksonomy or tagging application. Currently, synonymy is NOT even symmetric. Term A is set to be synonymous to term B, but Drupal can not derive that term B is symmetrically synonymous to term A.

I suggest that synonymy be implemented as follows:

+ Assosciated to each term is a set of senses. In each sense, a term can be caterogized to be synonymous to any number of terms in the vocab.

+ All terms synonymous in a sense must be mutually synomyous to one another.

For example, in the creation of a new term "chair", I can define two senses for this term. In the first sense, I define that the following 4 terms are synonymous to it:

# S: president, chairman, chairwoman, chairperson

Hi

My goal -> allow a user to enter the content of a section in LaTeX markup in the body of a book
node. When its saved, using nodeapi in my module, I want to create a file in /tmp/ with the LaTeX
body, then run LaTeX on it, and eventually upload a created ps or pdf file to the site.

My problem is the backslash.

My module has settings, two textareas which take the LaTeX header and footer,

\documentclass{article}
\begin{document}

and

\end{document}

respectively.

These are stored correctly and show up as I expect in the textarea. Then I added a call in nodeapi to my function:

  case 'insert':
        db_query('DELETE FROM {fhsstadmin}_syllabus WHERE nid = %d', $node->nid);
        db_query("INSERT INTO {fhsstadmin}_syllabus (nid, syllabus) VALUES (%d, '%s')",$node->nid,$node->fhsstadmin_syllabus);
         _prepare_ps_file($node->body);
      break;
    case 'update':
        db_query('DELETE FROM {fhsstadmin}_syllabus WHERE nid = %d', $node->nid);
        db_query("INSERT INTO {fhsstadmin}_syllabus (nid, syllabus) VALUES (%d, '%s')",$node->nid,$node->fhsstadmin_syllabus);
         _prepare_ps_file($node->body);

and my function looks like this:

function _prepare_ps_file($body)
{
$longtext = variable_get("fhsstadmin_bookheader","");
$longtext .= $body;
$longtext .= variable_get("fhsstadmin_bookfooter","");

I have a script from Mitchell Harper that is aimed at managing documents with MySQL and BLOB. I am not able to make it work - if anybody wants to give it a shot I can send it to you!

Let me know.

In order to make my life a bit easier when I wear my drupal site implementation/customization hat, I wrote this simple but dangerous perl script. (It was written in a day, so it is more a working prototype than anything else.)

It is designed to populate a database that it parses from the contents of the drupal modules webpage with module name, (part of) the module description, and the download url for the module. (give it its own db, don't try to have it share your drupal site's db)

The database file I am distributing with the module is based on last weekend's page (jan 13th) of 4.6 modules

Used on the command line, it can be used to simply search for and/or install modules.

drupal_module_installer.pl clear
will remove the contents of the default db so you can repopulate it or change which version you are working with

drupal_module_installer.pl update
will download and parse the module page for the version specified in the config section

for example:
drupal_module_installer.pl info wysiwyg

returns the following:

Results for modules that match your query: wysiwyg
Htmlarea
Allows Drupal to use the HTMLArea WYSIWYG formatter to replace text area fields.
--------------------------------------

quicktags
The quicktags module adds buttons above all your textareas. It uses on-the-fly generated javascript to do the magick. It is not a wysiwyg editor, but something far simpler: It simply inserts the basic HTML into your textarea.

I am going to be setting up quite an extensive site with several different sections that should get thousands of hits a day. Several features of the site will have to be custom coded. This will be a site that is half community and half static content. It will also need may different rss feeds.

Two of the cms solutions I am considering are drupal and plone/zope and I am wondering what people think would be better and why.

A big part of a new site I'm working on will be comments from unregistered users. Upon pressing the submit button for a comment (after they've previewed their comment), I want to send users to a page that gives them a few points to consider before going completely through with their post. Basically it would just be a mini terms of service page that outlines what comments should and should not be and then they can choose to agree or not.

Ideally, the viewing of this page would be cached if they agreed to the terms so they wouldn't have to see the page again (until they cleared their cookies / changed computers). This is not meant as any kind of spambot protection, just a warning for rational people before they make their post. It would be nice if they could optionally go back and modify their post (Agree, Agree & Modify Post, Disagree). I want the warning so people aren't completely stupefied if they are IP banned.

I actually came across this idea on a blog I read frequently: http://www.majornelson.com/. If you see a post there that interests you and you want to comment, do so and see what I'm talking about. However, don't just make some random post to see what it is I'm referring to (though you could make the post, hit submit, view the page, and hit cancel; I suppose).

Does this seem like something easy to incorporate into the Drupal comment system? More specifically, 4.6.5 and the upcoming 4.7 versions. If so, is anybody up for a making a patch that would work or a module?