Before you start

Hello everybody
I am not sure if i am posting in the correct forum, but am sure that i will get help...

I jsut start my website with drupal 6.X, i had 5.x before and i used some modules like
(user points, Private messeges, Invite, Gallery...)
when i tried to upload it to new 6.x it is giving not compatible error, and i can not find 6.X version
is there any way to let it work or i have to wait for a new version.

thanks in Advanced

Hi there,
I am trying to install drupal on mysite. My hosting provider use windows based hosting. I tried everything i

I'm looking into using Drupal for my company, and have a few questions about its capabilities:

1) Is there a web services module that can handle user creation and management?

2) Assume I already have a DB table (in MSSQL2005) that contains a list of shopping stores, with the requisite address information, phone number, home web site, etc., and I wanted to migrate it over to Drupal, where each shopping store has its own page (and I mean that in layman's terms), or node. First off, if I wanted to preserve that information as fields in the MySQL table, do I use CCK to create a new "shopping" node with those fields in it via the web interface? Second, do I need to add them individual through the web interface, or can I just export the table and dump that info into the MySQL table once I've established the node type?

2.5) Along those lines, how easy is it to design the Drupal site backwards? Meaning, if I already have a database schema I want to keep, that I can design nodes in Drupal that uses that database.

I received the following questions from the technology group in my organization. They are trying to implement new technologies and Drupal came up.

1. Is the technology adaptive or flexible enough to allow the integration of technologies in the future as
needed? (ex. can we add to or link to wikis, Adobe Connect sessions, etc.)

What specific technologies / tools are included in the product?

2. Is the graphic user interface (GUI) straightforward or self-evidentially simple?

Is the technology designed to integrate with specific, extant, companion technologies (ex.
GroupWise, MS Exchange)?

3. Cost: Is the technology a one-time purchase?

Is the technology charged per user? Per month / year?

Design/branding costs?

Additional cost information:

4. Is the product hosted and maintained by the vendor (ex. like a Google app.)?

Or do we purchase the product and install it on a SERVE server?

If vendor-based:
What kind of support is included in the purchase price?

What is typical response time to a technical support inquiry?

Can the vendor provide references from clients regarding their support services?

Additional backend information:

5. Is training offered from the provider?

Just need a few questions answered before I am converted to the drupal side...

If I have custom pages, for instance a google maps API driven map, or a single-page movie tracking PHP app. What would I do? Would I be able to place these pages into the drupal site seamlessly? Would the CMS recognize they are there?

Or would my best route be trying to convert it to a drupal module of some sort? I am an experienced PHP/JavaScript programmer. Would it be a moderate amount of work? Difficult? Simple?

situation:
An existing 4.7.* drupal website using a subfolder for drupal. So www.****.com/whatever is a static website
edited with ftp, dav or whatever, and then www.***.com/private/**** is the drupal website with access control
for annoymous removed on everything but frontpage module.

Plan is to be upgrade to 5.* but not 6.* till more modules like TINYmce are available.

Here is the desire. We would like to setup somehow to have drupal(s) do both the 'public' and the 'private' website
designated by a subfolder /private on the domain name.

To have drupal for www.****.com and separate drupal for www.****.com/private I fear may wreak havoc on figuring a sites/***/settings.php configuration.

But it is absolutely essential for anything under /private to not be available for annoymous viewers., hence the thought of having two separate drupal sites.

IF we tried to use some taxonomy module or equivalent to control access but put the 'one' drupal site at the root, /
several issues arise, would need all new content for private, including forums to show up with path /private/****
and several other issues... like uploads will need to be private, system....
ALSO it would be helpful say, anything posted without the path /private/**** meant to be public require user be a privileged role or moderation, because the average user is not carefull about paths..