Deprecated - Documentation

I can't help but notice that api.drupal.org inevitably goes down just about half an hour before deadlines, so like Pastebin, I'm going to suggest that drupal should organize mirrors for it - api.drupal.ca , or some such.

Just a thought!

hi,

any discussion , we can discuss and improve our knowlegde in php .please join with me..

cheers,
vetrivel

Hi,

I noticed that 2 Drupal-books are currently available:

Drupal: Creating Blogs, Forums, Portals, And Community Websites (Paperback)
http://www.amazon.com/Drupal-Creating-Portals-Community-Websites/dp/1904...

and

Hello,

A couple months back I made some Flash based tutorials introducing basic concepts in Drupal (for potential customers and as demos to customers I have moved to Drupal). The tutorials covered the following, step-by-step:

1. How to log in
2. How to create a page
3. How to edit an existing page
4. How to edit text (TinyMCE)
5. How to insert hyperlinks (TinyMCE)
6. How to upload files
7. How to insert graphics (TinyMCE)
8. How to add a new menu item to the navigation
9. Introducing Taxonomy

You can view an example Flash tutorial for page creation here.

Would the Drupal community be interested in contributed flash tutorials? Someone on another forum suggested I contribute these. I guess they could be helpful Drupal-newbies.

Right now they are "branded" which could be a turn off, or not?

They have some rough spots and if I were to re-do them in the future I would like fix the following:

1. Provide the summary text to accompany audio (which is already available on the demo site itself).

2. Outline each step (e.g. a screen "Step 1" followed by the demonstration and audio, then a "Step 2" screen and so forth; possibly a small menu with a pointer to the step I am on, and possibly "quick nav" buttons to jump back and forth to steps).

3. Audio quality (current program limitation... note all the final "s" that get cut off...)

Please add screenshots and/or sample URLs for all modules

It's extremely hard to understand if specific modules will do what I'm looking for without examples.

This is esp. true when there is more than one module that does the same thing.

I've searched this forum for months and not found anything. Here is the situation...

We have a website with 25,000 articles and 240 categories (http://www.sportbusiness.com/). Each news item is a CCK (written by JonBob) type. I developed a custom module to generate the menu on the left which uses the top terms of the vocabulary by nodes-per-term. When you select a term, it takes you to the taxonomy/term/[tid] page which is provided by the wonderfull Views Module (written by MerlinOfChaos). All this worked perfectly. Whenever a news items gets added (5 or 6 a day) it automatically appears in the correct pages. Fantastic... But life isn't that easy. The RSS feeds would not work correctly with the CCK nodetype. The views_rss.module didn't know what the teaser was - afterall, CCK does not have teasers. Instead, it was taking the HTML of the body and our description field ended up looking like a HTML Entity encoded version of the body! Not ideal...

After talking with robertDouglass, reading through a number of posts including the views documentation and finally looking at the views_rss.module, I realised that the $node->teaser needed setting before the XML was output. In the views_rss.module there was a pair of lines (currently 131-132 at time of writing - version 1.7) which read...