Documentation contributors

For speed-up your work with a huge *.po files You always can do some optimization

Clearing untranslated messages (especially if Your file greater than 2M 8))

very usefull tip - remove duplicates

Good luck!

I have been looking for a single point where we can get the comprehensive documentation about Drupal Installation. I am proposing creation of a Wiki. This will help new-bies like me as well as maintainers/developers as most of the issues will be solved within the WIKI.

Swapnil Bhartiya

Services 6.x-2.x-dev on Drupal 6.14. Uses the XML-RPC for PHP library at http://phpxmlrpc.sourceforge.net/. Thanks to clues from http://drupal.org/node/303285 and the services tester, it includes some code for populating CCK fields ("field_publication", "field_byline", etc.). This is pre-production code for importing articles to a newspaper website, designed to run on the command line. I just left the parseXML() function as an example.

I'm developing my custom modules and templates and hit a bug when trying to create a region on my theme called 'Navigation'. Since I was unable to find any Drupal reserved word list (and can't find that information on any other place), I did a try-and-error process.

I plan to put here any other word that I found and I hope that this could help someone in the future, if more people helps.

Since I'm using Drupal 6, this is the Drupal 6 Reserved words list.

• Navigation: when trying to call a region as 'Navigation', nothing happens and no content is assigned to '$navigation', despite the fact that there is blocks assigned to 'navigation' section.

Before you open a new or add to an existing issue, please follow these guidelines:

• Search for duplicate issues.
• Do not hijack issues. It's confusing to everyone involved in the original issue, to other people who might have the same issue as you, and it's rude.
• Support requests should be very specific, narrow scope items. Broad or vague support requests or general pleas for help are best left to the forums, where you will get more eyes.

When opening a new issue, failure to completely fill out all fields may result in the immediate closure of your issue due to lack of information.

Reasons your issue may be summarily closed:

1. Your issue has been left marked "Postponed, maintainer needs more info" for more than 30 days.
2. You have failed to provide enough information to begin to even guess what the problem may be. The Views queue is hugely active, and there are not enough individuals helping to maintain it at a sustainable level. Issues that can be summarized as "it's broken. Fix it." will be closed with a pointer to this page.
3. You are combatative or argumentative in the queue, or bump your issue (make comments that are intended to raise your issue back to the top without adding further details).

The Views issue queue is one of the larger queues within the Drupal Project (see the statistics page)

Make sure that your issue is a Views issue! Views provides the ability to list data - if your data is provided by a module other than Drupal Core, please enter your issue in that module's issue queue instead. If your problem deals exclusively with fields or filters provided by another module (CCK, Image, VotingAPI are common) please post the issue under the queue for that module first; all modules are responsible for telling Views about their own fields. It's possible Views IS at fault, but the module maintainers are the best people to make that determination, and they can kick the issue into the Views queue with an explanation of what's wrong if that is the case. If there is a more recent version of Views that is supported, please try that version if at all possible.

Before you open a new or add to an existing issue, please follow these guidelines:

• Search for duplicate issues.
• Do not hijack issues. It's confusing to everyone involved in the original issue, to other people who might have the same issue as you, and it's rude.