See the Mailing lists or Drupal Issue queue. There are also various working groups on groups.drupal.org

xmlrpc error is not reset

Hi,

why is the xmlrpc error not reset before a new xmlrpc call?
I'ts correct that you can check for errors with xmlrpc() === FALSE, but this does not work if the call itself returns a boolean value,
So it seems impossible to distnguish between the answer FALSE and the FALSE caused by an error.

Is there another way to check for errors besides the xmlrpc_errno(). Or is there a possibility to reset the error?

Edit own content/edit content rule problem!

I've created a role, which has only "Edit own page content/Edit own story content" activated, but I can still edit posts from other users. This is a serious bug or there is something that I can figure out... Anyone had the same problem?

Thanks in advance for your replies!

Is hierarchical ./sites/ organization possible?

Question: Is it possible to organize the ./sites/ directory hierarchically, with inherited permissions, modules, themes, etc.?

Background: Drupal 5.x introduced a much cleaner method for setting up a multisite codebase. Essentially, one sets up a directory under ./sites/ for each domain and subdomain desired. Better still would be a hierarchical arrangement of sites, with inheritance of attributes.

The following excerpt from http://drupal.org/node/53705 summarizes current practice:

In addition to multiple sites, such as www.example1.com and www.example2.com, sub domains are also easily set up. Adding sub3.example2.com and sub3.example2.com/site4, the directory structure for these four sites would be:

/drupal/sites/all/modules
/drupal/sites/all/themes
/drupal/sites/default/files
/drupal/sites/default/settings.php
/drupal/sites/example1.com/files
/drupal/sites/example1.com/modules
/drupal/sites/example1.com/settings.php
/drupal/sites/example1.com/themes
/drupal/sites/example1.com/tmp
/drupal/sites/example2.com/files
/drupal/sites/example2.com/modules
/drupal/sites/example2.com/themes
/drupal/sites/example2.com/tmp
/drupal/sites/example2.com/settings.php
/drupal/sites/sub3.example2.com/files
/drupal/sites/sub3.example2.com/modules
/drupal/sites/sub3.example2.com/settings.php
/drupal/sites/sub3.example2.com/themes

getting tricky with comments

Hi

I am writing a module that lets users create "recommendations" for news stories on the web. "Recommendation" is the node type I am adding. Now, every story has a URL, *but*, there might be more than one recommendation for the same URL.

Drupal 6 Mail Templating System

A mail template is a similar concept to a mail merge document. The mail is written using placeholders for information that changes between each specific instance of the mail. The mail template is stored then when a mail is to be sent values are substituted for the placeholders.

Mail templating in Drupal is currently (as of Drupal 5) implemented by storing a subject and body in the database somewhere (typically in the variable table). Editing the templates is done with code similar to that below:

$default_subject = 'My default subject at !site';
$default_body = "Dear !user,\n\nThis is the default body for the mail.\n\n!site team";

$form['my_mail_subject'] = array(
  '#type' => 'textfield',
  '#default_value' => variable_get('my_mail_subject', $default_subject), ...
);

$form['mail_mail_body'] = array(
  '#type' => 'textarea',
  '#default_value' => variable_get('mail_mail_body', $default_body), ...
);

In the new implementation this becomes much simpler. The form interface is provided by centralised code. You call one function and tell some information about the mail such as the mail type (e.g user welcome mail or shipping notification), title and description of the form's select element and the variable (in the variable table) holding the mail ID.


define('MAIL_VARNAME_MY_MAIL', 'my_mail_variable');
...

Getting an array of nodes

I have a CCK node type called "quotes." Basically, I want to be able to display a random quote within a block.

What is the best way to get this done?

Pages

Subscribe with RSS Subscribe to RSS - Deprecated - Drupal core