I am converting a site to drupal and on the current site there is a javascript slideshow on the homepage. All it does it fade from one image to another, without any buttons or description. I have had a look at the slideshows available as modules but none of them seem to fulfil what i am looking for (most of them will have Next, Previous buttons).
So i tried to just use the same script as i was using before. I made a block which i placed in the head content containing the HEAD code from the old site. And then i made another block which i put in the header content section (which is where i want the slideshow to be). I have included the two bits of code at the bottom
The problem is that whenever i access the page an error pops up in IE sayin that i cannot load the page. Sometimes it will get as far as half loading the slideshow and fail. In firefox it seems to work fine though. I can also include the head content in page.tpl and it works in firefox but not ie again.
I've been trying to search for a solution to this, but I haven't got a full grasp of the Drupal terminology so I'm not sure I'm searching for the right thing.
I'm converting an existing site that has a really strong data schema already in place. I'm looking for advice on the best way to represent the data structure in Drupal. As an example, the site lists scheduled activities which take place throughout the year. Here is how a small subset of how the data is structured:
Table 2: Activity Dates (dates on which the activities are held throughout the year)
Table 3: Activity Pricing (ability to set one or more prices per activity date)
I'd like to preserve this data integrity in Drupal. Rather than creating a new "Activity" node each time there is a new date added to the schedule, I want users to select from a pre-existing list of available activities. Also when a new price category has been created for a given date, I want users to select from a pre-existing list of available activity/date combinations.
What might be the best way to make this happen? Is it a matter of creating three separate Content Types, then maybe implementing some workflow to ensure dates can't be set without a pre-existing activity? And pricing can't be set without pre-existing dates? Also I'd rather avoid hardcoding lots of duplicate data into Categories. I'm open to whatever will work best.
I do already have a self-made community and I want to migrate to Drupal 5.
I thought of just dropping the Drupal files onto my server root and slowly make the transition from my current site to a new Drupal site. No files except one conflicts with the Drupal, and that is index.php.
What would happen if I renamed the Drupal index.php until Drupal is fairly installed and configured then renaming it back to index.php?
I am trying to convert a newspaper website over to Drupal. The website is currently using an HTML layout that requires you to update each page individually from a template and then update all the index files to point to the new pages. Obviously this is a lot of work and a Drupal installation would be greatly helpful. We have a working install, have installed modules successfully, but cannot seem to get the layout the way we want it.