Converting to Drupal

Hello All,

I am a Drupal newbie but have found things pretty easy thus far - I am not a PHP, CSS or HTML newbie so that helps. I am in the process of creating content in Drupal for a site that currently runs as a bunch of SHTML pages. Currently, I am developing the new Drupal site using a dummy domain name that I use purely for development purposes. Both the dummy domain and the actual current site domain are hosted on the same VPS. Once I am done with creating the new content I want to place it into my current site.

Deleting a page/story(content item) from edit page is redirecting to a blank page . What might be the root cause??? Is this related to theme which has been integrated??

Had anyone been through this scenario before???? If so, Kindly tell me the solution for this.

Thanks in advance!!

Hi all.

I'm not sure where this question should go, but I figured this was as good as any. Firstly, I'm new to drupal, but I've got a test site up and running on XAMPP which I'm playing with and managed to add pages, modules etc and it's going OK.

I'm attempting to convert a website for an association, which has been hand coded in php, to drupal to make it easier to maintain and extend.

Hi All,
I'm porting job search & recruitment website to Drupal platform. The main functionality deals with structured information only (i.e., forms, checkboxes, radios, short text fields), while I'm planning to leverage existing Drupal modules for unstructured content (such as ads, forums, ecommerce).

I'm new to Drupal and appreciate if experienced developers could provide me some orientation:

Question 1: Is Drupal a right tool/framework for building web apps with mainly structured content (i.e. UI consists of fixed number of forms, the user mgmt consists of few strict roles, etc) as opposed to websites dealing with a stream of documents with unstructured rich-text-formatted content?

Question 2: Do I have to use Form API? Again, I'm looking for "best practice" advice. I wouldn't mind taking its trade offs/overheads if the hardcore Form API (Node API, etc) is considered a "good style" of Drupal programming (remember, I'm coming from web app that has been already fine-tuned for performance, with all CSS and JS static code & text dictionaries being cached locally in browser, and only small piece of dynamic data was really exchanged over network).

Question 3: What are practical rules for creating multiple content types when dealing with structured content in Drupal?

Hello, everyone :)
I'm new to drupal, so don't laugh if my question sounds silly. So, straight to the point:
I was using joomla earlier, so there was an easy way to categorize contents. In drupal everything appears like .../node/1. I'm trying to make it appear like /category1/section1/sectionofsection1/page1, /category1/section1/sectionofsection2/page1-title, /category1/page1/title and etc. I hope you got my mind. I would like everything would be categorized.
So how can I create categories and pages within it.

Hello,

I'm planning a Joomla 1.0 -> Drupal 6 migration and got a little bit confused on image handling.
My Joomla site uses images whithin articels, as clickable attachments to articles and within a special/separated gallary of all available images.
As far as I understand drupal, drupal has a thin core that can be extended by modules, but I've to be careful on choosing modules, since betting on the wrong horse will cause update issues and painful migrations later on.

Since images are a bread-and-butter issue for web cms'es I'd expect drupal's core to support basic image handling (ie inserting into stories, pages and some zoom-on-click functionality).
Is this correct? - Is this functionality somehow limited? Is there a best-practice for importing joomla content including images?
Using core for this task seems to be pretty obvious, since I won't run into module deprecation / update issues on vital content later on.
I hardly found any documentation on how drupal's core is handling images - using external modules seems to be a popular choice.

The next step is finding a replacement for Joomla's "Pony Gallery ML". Since "Pony Gallery ML" does more than simple image handling, there seems to be two options:

• Using a drupal gallery module
• Using a bridging module for another gallery (ie gallery2)