Before you start

I'm still learning the ins and outs, so forgive me. I am interested in using an external script to route incoming mail into the CMS, give it one or more "tags," and make it a "private" page (tags viewable only by certain users or groups).

I see there is some action going on with modules named folksonomy and taxonomy-on-the-fly. Permissions, on nodes or taxonomy -- it's not clear to me where that stands.

I guess my question is, is there a general sense of how easy this would be?

Hello,

Hey all,

My current website is located at http://www.edinw.com

What it currently has:
-A list of dealers & employees that are allowed to access the members page which contains 3 seperate download pages (reg price lists, specials, close outs)
-A front page with the latest news
-A section that contains public downloads in 4 sections (delivery schedule, policies, etc.)

Now here is what I mean: I need a site that is really two sites. One that would be invisible to the public were an admin could doctor with everything and writers could submit content (this I know that Drupal can do, and well), BUT then a second "site" or section that would be for the reading public which just presented the content and not option to submit content and no user login or anything like that.

I guess basically I would just need a way for Drupal to remove a few blocks from the left bar. But how?

So is Drupal the choice or is there another option?

Hello,

I'm using XAMPP's PHP/Apache/MySQL bundle. I went through the Drupal pre-installation instructions outlined in the INSTALL.txt file. My site seemed to work prior to until I set the session.save_handler value to "user" as requested in the instructions. Now my pages run into the following error:

Fatal error: session_start(): Failed to initialize storage module: user (path: .;c:\apachefriends\xampp\tmp)

How do i fix this?

RS

I don't need a CMS to render or serve a web site. What I need is a good CMS to manage the content-creation side of an existing site. That means either (a) working with an existing non-Drupal schema, or (b) in the worst case converting all the content to a Drupal schema. In the latter case, however, I still need to extend the schema substantially, both by adding columns to tables and even adding new tables. Yes, I need page rendering, but only for author/admin preview. I'll continue to render the web site statically and dynamically from the database using the existing code.