importing static site content into categories/taxonomies

I have some perl code that cheerfully parses a static html/php site and puts the content into drupal. So far, so good. What i need to do now is to be able to assign categories to content on the fly. Can someone explain how the taxonnomy module stores content in the db? or even a tutorial on it? I've searched a lot of stuff about it's flaws, but cant seem to find a description of how the taxonomy interacts with the node table.

preg_match ???

So I get everything working, and config'd (at least that's what I think). Mysql, php, apache, etc all working. When I try to go to http://server/drupal/index.php, I get this weird error that points to a unicode.inc file.

The error is "Fatal error: Call to undefined function preg_match() in /usr/local/www/data-dist/drupal/includes/unicode.inc on line 32".

I vi the file and find that the function says:

30 // Check for outdated PCRE library
31 // Note: we check if U+E2 is in the range U+E0 - U+E1. This test returns TRUE on old PCRE versions.
32 if (preg_match('/[\xc3\xa0-\xc3\xa1]/u', '\xc3\xa2')) {
33 if ($errors) {
34 form_set_error('unicode', t('The PCRE library in your PHP installation is outdated. This will cause problems whe
n handling Unicode text. If you are running PHP 4.3.3 or higher, make sure you are using the PCRE library supplied by PHP. Ple
ase refer to the PHP PCRE documentation for more information.', array('%url' => 'http://www.php.net/pcre'))
);
35 }
36 return UNICODE_ERROR;
37 }

The error is actually coming from the "if(preg_match)..." line of code. The comments say to upgrade my PCRE, but it doesn't even look like it's getting to that error message. It seems like it's erring before the code can be run. Anybody have a clue what might be going on here?

Hundreds of groupings

I have a site to build where the content falls into a hundred (or more) clumps. I'm stating this generally because I don't want to get attached to a specific solution just yet.

The site is going to cover a field, in which there are a hundred (or more) sub-fields. Each of the subfields is a clump of content. I want to organize the content by these sub-fields. In some cases content will apply to multiple sub-fields, hence content should be able to appear in each clump to which it's appropriate. In some cases there is content whose general outline is the same (e.g. contact info for schools teaching that subfield) but the details are different for each subfield.

In any case ... I'm wondering about advice on implementing this.

I've thought about organic groups and have installed it on one site and I'm not entirely happy with it for this use. I just read through this issue: http://drupal.org/node/28224 and tend to agree with what's said there. If you have hundreds of groups, then the content submission page is going to get a checkbox for each and that's untenable. It might be a little better to have them grouped in a hierarchy like that page suggests, but I'm having a hard time visualizing that. Also in my case few/none of the groups need to be private.

This http://drupal.org/node/28480 generalized relationship module looks to be interesting but so vaporous that I'm not sure what it does. The general concept is interesting from a theory standpoint. But it doesn't seem to have a concrete representation that I can grab onto.

My Drupal book has arrived!

Today I received a very nice package in the mail; my Drupal book is finally available!

Robert Douglass' Drupal bookWhen I first met Dries Buytaert, in February in Antwerp, we discussed the need for a book explaining how to use Drupal. We agreed that such a book would be a great asset to the many people who are becoming interested in our great software. Since I had already decided that it was my goal to write a Drupal book, I expressed this to Dries.

Soon after the conference, Dries was approached by Matt Wade, an editor at Apress, about writing 1/3 of a book about building online communities. The other 2/3 would discuss phpBB and WordPress, two other immensely popular projects that address different niches. As Dries was too busy with his studies to write a book, he introduced me to Matt.

The result was a project that lasted until October; writing the first book about Drupal. I knew that I would need lots of support, and therefore asked James Walker to be the technical editor. This turned out to be a very good move, as James is a "Drupal Rockstar" who always knows the smallest technical details, and has worked with many many clients and other people to know which parts of Drupal are hard to grasp, and where the hidden sticking points are. He helped me decide how to present the many concepts and capabilities that are not always intuitive.

classifieds for drupal

hi guys,

i want a have a simple kind of classifieds on my site and i am unable to find an appropriate module for it.

i have a bike site where users could sell or buy bikes:
so they just fill a form with name of the bike, description, image and a price. i don´t need categories. so it could be something like a guestbook but each post could have a thumbnail.

what could i use for that? thank you.

stefan

Handle large number of RSS requests

I'd like to share our experience in dealing with a sharp increase in RSS feed requests including the solution we finally implemented and a feature request for Drupal core. Before getting into the subject, let me say that we have been running Drupal since last year. In terms of both functionality and performance, I don't see any other CMS system out there that's better for our needs.

What happened

* Ours is a literature site in Chinese with 18000 registered users. We have been publishing online since 1995. The current host is a dedicated 2.6 GHz Celeron server with 768 MB RAM running PHP 4.3.3 and MySQL 3.23.58. The Drupal installed is a CVS version (4.7?) that has been running for about 4 months.

* An email application used by many in China has added a RSS reader. One of our RSS feed is one of the preset feeds in the application. Starting in mid November, RSS requests started to increase very fast within a week. Before we can respond the HTTP server had to be shut down for the better part of 3 days because the server would overload within minutes. Weblogs show that hits had increased about 5 times over the two months.

* Drupal based solutions that we tried were not successful. One of the major reasons is the SQL calls generated for each Drupal URL hit. It is the database calls that invariably killed the server in the end. This in part has to do with a problem/bug in MySQL which failed to kill "sleep" connections during server overload (persistent connection is turned off).

Pages

Subscribe with RSS Subscribe to RSS - Drupal 4.7.x