2001-03-10 11:07:52 +00:00
<?php
2001-10-20 18:57:09 +00:00
// $Id$
2000-12-23 15:20:10 +00:00
2004-08-21 06:42:38 +00:00
/**
* @file
* Controls the boxes that are displayed around the main content.
*/
2004-05-11 20:10:14 +00:00
/**
* Implementation of hook_help().
*/
function block_help($section) {
2003-08-05 18:33:39 +00:00
switch ($section) {
2003-10-09 18:53:22 +00:00
case 'admin/help#block':
2004-10-31 07:34:47 +00:00
return t('
The Input formats - filter patch has landed. I still need to make update instructions for modules and update the hook docs.
Here's an overview of the changes:
1) Multiple Input formats: they are complete filter configurations (what filters to use, in what order and with which settings). Input formats are admin-definable, and usage of them is role-dependant. For example, you can set it up so that regular users can only use limited HTML, while admins can free HTML without any tag limitations.
The input format can be chosen per content item (nodes, comments, blocks, ...) when you add/edit them. If only a single format is available, there is no choice, and nothing changes with before.
The default install (and the upgrade) contains a basic set of formats which should satisfy the average user's needs.
2) Filters have toggles
Because now you might want to enable a filter only on some input formats, an explicit toggle is provided by the filter system. Modules do not need to worry about it and filters that still have their own on/off switch should get rid of it.
3) Multiple filters per module
This was necessary to accomodate the next change, and it's also a logical extension of the filter system.
4) Embedded PHP is now a filter
Thanks to the multiple input formats, I was able to move the 'embedded PHP' feature from block.module, page.module and book.module into a simple filter which executes PHP code. This filter is part of filter.module, and by default there is an input format 'PHP', restricted to the administrator only, which contains this filter.
This change means that block.module now passes custom block contents through the filter system.
As well as from reducing code duplication and avoiding two type selectors for page/book nodes, you can now combine PHP code with other filters.
5) User-supplied PHP code now requires <?php ?> tags.
This is required for teasers to work with PHP code. Because PHP evaluation is now just another step in the filter process, we can't do this. Also, because teasers are generated before filtering, this would result in errors when the teaser generation would cut off a piece of PHP code.
Also, regular PHP syntax explicitly includes the <?php ?> tags for PHP files, so it makes sense to use the same convention for embedded PHP in Drupal.
6) Filter caching was added.
Benchmarking shows that even for a simple setup (basic html filtering + legacy URL rewriting), filtercache can offer speedups. Unlike the old filtercache, this uses the normal cache table.
7) Filtertips were moved from help into a hook_filter_tips(). This was required to accomodate the fact that there are multiple filters per module, and that filter settings are format dependant. Shoehorning filter tips into _help was ugly and silly. The display of the filter tips is done through the input format selector, so filter_tips_short() no longer exists.
8) A more intelligent linebreak convertor was added, which doesn't stop working if you use block-level tags and which adds <p> tags.
2004-08-10 18:34:29 +00:00
<p>Blocks are the boxes visible in the sidebar(s) of your web site. These are usually generated automatically by modules (e.g. recent forum topics), but you can also create your own blocks.</p>
2004-10-31 07:34:47 +00:00
<p>The sidebar each block appears in depends on both which theme you are using (some are left-only, some right, some both), and on the settings in block management.</p>
<p>The block management screen lets you specify the vertical sort-order of the blocks within a sidebar. You do this by assigning a weight to each block. Lighter blocks (smaller weight) "float up" towards the top of the sidebar. Heavier ones "sink down" towards the bottom of it.</p>
<p>A block\'s visibility depends on:</p>
<ul>
<li>Its enabled checkbox. Disabled blocks are never shown.</li>
<li>Its throttle checkbox. Throttled blocks are hidden during high server loads.</li>
<li>Its path options. Blocks can be configured to only show/hide on certain pages</li>.
<li>User settings. You can choose to let your users decide whether to show/hide certain blocks.</li>
<li>Its function. Dynamic blocks (such as those defined by modules) may be empty on certain pages and will not be shown.</li>
</ul>
<h3>Administrator defined blocks</h3>
<p>An administrator defined block contains content supplied by you (as opposed to being generated automatically by a module). Each admin-defined block consists of a title, a description, and a body which can be as long as you wish. The Drupal engine will render the content of the block.</p>');
2004-06-18 15:04:37 +00:00
case 'admin/modules#description':
2004-05-11 20:10:14 +00:00
return t('Controls the boxes that are displayed around the main content.');
2004-06-18 15:04:37 +00:00
case 'admin/block':
2004-10-31 07:34:47 +00:00
return t("
<p>Blocks are the boxes in the left and right side bars of the web site. They are made available by modules or created manually.</p>
<p>Only enabled blocks are shown. You can position the blocks by deciding which side of the page they will show up on (region) and in which order they appear (weight).</p>
2004-11-14 20:20:09 +00:00
<p>If you want certain blocks to disable themselves temporarily during high server loads, check the 'Throttle' box. You can configure the auto-throttle on the <a href=\"%throttle\">throttle configuration page</a> after having enabled the throttle module.
2004-10-31 07:34:47 +00:00
", array('%throttle' => url('admin/settings/throttle')));
2004-06-18 15:04:37 +00:00
case 'admin/block/add':
2004-10-09 06:29:16 +00:00
return t("Here you can create a new block. Once you have created this block you must make it active and give it a place on the page using <a href=\"%overview\">blocks</a>. The title is used when displaying the block. The description is used in the \"block\" column on the <a href=\"%overview\">blocks</a> page.", array('%overview' => url('admin/block')));
2003-08-05 18:33:39 +00:00
}
2001-01-13 16:33:19 +00:00
}
2004-05-11 20:10:14 +00:00
/**
2004-05-17 22:00:06 +00:00
* Menu callback; presents the block-specific information from admin/help.
2004-05-11 20:10:14 +00:00
*/
2003-11-20 21:51:23 +00:00
function block_help_page() {
2004-05-11 20:10:14 +00:00
print theme('page', block_help('admin/help#block'));
2003-11-20 21:51:23 +00:00
}
2004-05-11 20:10:14 +00:00
/**
* Implementation of hook_perm().
*/
2001-06-20 20:00:40 +00:00
function block_perm() {
2004-05-11 20:10:14 +00:00
return array('administer blocks');
2001-06-29 22:08:57 +00:00
}
2004-04-21 13:56:38 +00:00
/**
2004-06-18 15:04:37 +00:00
* Implementation of hook_menu().
2004-04-21 13:56:38 +00:00
*/
2004-09-16 07:17:56 +00:00
function block_menu($may_cache) {
2004-06-18 15:04:37 +00:00
$items = array();
2004-09-16 07:17:56 +00:00
if ($may_cache) {
$items[] = array('path' => 'admin/block', 'title' => t('blocks'),
'access' => user_access('administer blocks'),
'callback' => 'block_admin');
$items[] = array('path' => 'admin/block/list', 'title' => t('list'),
'type' => MENU_DEFAULT_LOCAL_TASK, 'weight' => -10);
2004-10-31 07:34:47 +00:00
$items[] = array('path' => 'admin/block/configure', 'title' => t('configure block'),
2004-09-16 07:17:56 +00:00
'access' => user_access('administer blocks'),
2004-10-31 07:34:47 +00:00
'callback' => 'block_admin_configure',
'type' => MENU_CALLBACK);
$items[] = array('path' => 'admin/block/delete', 'title' => t('delete block'),
'access' => user_access('administer blocks'),
'callback' => 'block_box_delete',
2004-09-16 07:17:56 +00:00
'type' => MENU_CALLBACK);
2004-11-15 11:16:39 +00:00
$items[] = array('path' => 'admin/block/add', 'title' => t('add block'),
2004-09-16 07:17:56 +00:00
'access' => user_access('administer blocks'),
2004-10-31 07:34:47 +00:00
'callback' => 'block_box_add',
2004-09-16 07:17:56 +00:00
'type' => MENU_LOCAL_TASK);
}
2004-06-18 15:04:37 +00:00
return $items;
2001-06-20 20:00:40 +00:00
}
2004-05-11 20:10:14 +00:00
/**
* Implementation of hook_block().
*
* Generates the administrator-defined blocks for display.
*/
2004-10-31 07:34:47 +00:00
function block_block($op = 'list', $delta = 0, $edit = array()) {
switch ($op) {
case 'list':
$result = db_query('SELECT bid, title, info FROM {boxes} ORDER BY title');
while ($block = db_fetch_object($result)) {
$blocks[$block->bid]['info'] = $block->info;
}
return $blocks;
case 'configure':
$box = block_box_get($delta);
if (filter_access($box['format'])) {
return block_box_form($box);
}
break;
case 'save':
block_box_save($edit, $delta);
break;
case 'view':
$block = db_fetch_object(db_query('SELECT * FROM {boxes} WHERE bid = %d', $delta));
$data['subject'] = $block->title;
$data['content'] = check_output($block->body, $block->format);
return $data;
2002-05-02 19:13:45 +00:00
}
}
2000-12-23 15:20:10 +00:00
function block_admin_save($edit) {
2002-10-26 15:17:26 +00:00
foreach ($edit as $module => $blocks) {
foreach ($blocks as $delta => $block) {
2004-10-31 07:34:47 +00:00
db_query("UPDATE {blocks} SET region = %d, status = %d, weight = %d, throttle = %d WHERE module = '%s' AND delta = '%s'",
$block['region'], $block['status'], $block['weight'], $block['throttle'], $module, $delta);
2002-10-26 15:17:26 +00:00
}
2000-12-23 15:20:10 +00:00
}
2002-11-17 06:42:52 +00:00
2004-10-31 07:34:47 +00:00
return t('The block settings have been updated.');
2000-12-23 15:20:10 +00:00
}
2002-10-30 08:12:28 +00:00
/**
2004-05-11 20:10:14 +00:00
* Update the 'blocks' DB table with the blocks currently exported by modules.
2002-11-01 10:47:20 +00:00
*
2003-12-08 06:32:19 +00:00
* @param $order_by php <a
* href="http://www.php.net/manual/en/function.array-multisort.php">array_multisort()</a>
* style sort ordering, eg. "weight", SORT_ASC, SORT_STRING.
2003-11-24 22:46:03 +00:00
*
2004-05-11 20:10:14 +00:00
* @return
* Blocks currently exported by modules, sorted by $order_by.
2002-10-30 08:12:28 +00:00
*/
2004-05-11 20:10:14 +00:00
function _block_rehash($order_by = array('weight')) {
$result = db_query('SELECT * FROM {blocks} ');
2002-10-26 15:17:26 +00:00
while ($old_block = db_fetch_object($result)) {
$old_blocks[$old_block->module][$old_block->delta] = $old_block;
}
2004-05-11 20:10:14 +00:00
db_query('DELETE FROM {blocks} ');
2002-10-26 15:17:26 +00:00
foreach (module_list() as $module) {
2004-05-11 20:10:14 +00:00
$module_blocks = module_invoke($module, 'block', 'list');
2002-10-26 15:17:26 +00:00
if ($module_blocks) {
foreach ($module_blocks as $delta => $block) {
2004-05-11 20:10:14 +00:00
$block['module'] = $module;
$block['delta'] = $delta;
2002-10-26 15:17:26 +00:00
if ($old_blocks[$module][$delta]) {
2004-05-11 20:10:14 +00:00
$block['status'] = $old_blocks[$module][$delta]->status;
$block['weight'] = $old_blocks[$module][$delta]->weight;
$block['region'] = $old_blocks[$module][$delta]->region;
2004-10-31 07:34:47 +00:00
$block['visibility'] = $old_blocks[$module][$delta]->visibility;
$block['pages'] = $old_blocks[$module][$delta]->pages;
2004-05-11 20:10:14 +00:00
$block['custom'] = $old_blocks[$module][$delta]->custom;
$block['throttle'] = $old_blocks[$module][$delta]->throttle;
2002-10-26 15:17:26 +00:00
}
else {
2004-05-11 20:10:14 +00:00
$block['status'] = $block['weight'] = $block['region'] = $block['custom'] = 0;
2004-10-31 07:34:47 +00:00
$block['pages'] = '';
2002-10-26 15:17:26 +00:00
}
// reinsert blocks into table
2004-10-31 07:34:47 +00:00
db_query("INSERT INTO {blocks} (module, delta, status, weight, region, visibility, pages, custom, throttle) VALUES ('%s', '%s', %d, %d, %d, %d, '%s', %d, %d)",
$block['module'], $block['delta'], $block['status'], $block['weight'], $block['region'], $block['visibility'], $block['pages'], $block['custom'], $block['throttle']);
2002-10-26 15:17:26 +00:00
$blocks[] = $block;
2002-11-01 10:47:20 +00:00
2002-10-30 08:12:28 +00:00
// build array to sort on
$order[$order_by[0]][] = $block[$order_by[0]];
2002-10-26 15:17:26 +00:00
}
}
}
2002-10-30 08:12:28 +00:00
// sort
array_multisort($order[$order_by[0]], $order_by[1] ? $order_by[1] : SORT_ASC, $order_by[2] ? $order_by[2] : SORT_REGULAR, $blocks);
2002-10-26 15:17:26 +00:00
return $blocks;
}
2001-01-26 13:38:46 +00:00
2004-05-11 20:10:14 +00:00
/**
* Prepare the main block administration form.
*/
2002-10-26 15:17:26 +00:00
function block_admin_display() {
2002-10-30 08:12:28 +00:00
$blocks = _block_rehash();
2002-10-26 15:17:26 +00:00
2004-10-31 07:34:47 +00:00
$header = array(t('Block'), t('Enabled'), t('Throttle'), t('Weight'), t('Region'), array('data' => t('Operations'), 'colspan' => 2));
2002-12-29 16:03:01 +00:00
2002-10-26 15:17:26 +00:00
foreach ($blocks as $block) {
2004-10-31 07:34:47 +00:00
if ($block['module'] == 'block') {
$operation = l(t('delete'), 'admin/block/delete/'. $block['delta']);
2002-05-02 19:13:45 +00:00
}
2003-01-02 06:08:05 +00:00
else {
2004-10-31 07:34:47 +00:00
$operation = '';
2003-01-02 06:08:05 +00:00
}
2002-12-29 16:03:01 +00:00
2004-10-31 07:34:47 +00:00
$rows[] = array($block['info'], array('data' => form_checkbox(NULL, $block['module'] .']['. $block['delta'] .'][status', 1, $block['status']), 'align' => 'center'), array('data' => form_checkbox(NULL, $block['module'] .']['. $block['delta'] .'][throttle', 1, $block['throttle'], NULL, module_exist('throttle') ? NULL : array('disabled' => 'disabled')), 'align' => 'center'), form_weight(NULL, $block['module'] .']['. $block['delta'] .'][weight', $block['weight']), form_radios(NULL, $block['module'] .']['. $block['delta'] .'][region', $block['region'], array(t('left'), t('right'))), l(t('configure'), 'admin/block/configure/'. $block['module'] .'/'. $block['delta']), $operation);
2000-12-23 15:20:10 +00:00
}
2001-01-26 13:38:46 +00:00
2004-05-11 20:10:14 +00:00
$output = theme('table', $header, $rows);
$output .= form_submit(t('Save blocks'));
2000-12-23 15:20:10 +00:00
2004-06-18 15:04:37 +00:00
return form($output, 'post', url('admin/block'));
2000-12-23 15:20:10 +00:00
}
2002-05-02 19:13:45 +00:00
function block_box_get($bid) {
2004-05-11 20:10:14 +00:00
return db_fetch_array(db_query('SELECT * FROM {boxes} WHERE bid = %d', $bid));
}
/**
2004-10-31 07:34:47 +00:00
* Menu callback; displays the block configuration form.
2004-05-11 20:10:14 +00:00
*/
2004-10-31 07:34:47 +00:00
function block_admin_configure($module = NULL, $delta = 0) {
2004-05-11 20:10:14 +00:00
$edit = $_POST['edit'];
$op = $_POST['op'];
2004-10-14 15:28:24 +00:00
switch ($op) {
case t('Save block'):
2004-10-31 07:34:47 +00:00
db_query("UPDATE {blocks} SET visibility = %d, pages = '%s', custom = %d WHERE module = '%s' AND delta = '%s'", $edit['visibility'], $edit['pages'], $edit['custom'], $module, $delta);
module_invoke($module, 'block', 'save', $delta, $edit);
drupal_set_message('The block configuration has been saved.');
2004-10-14 15:28:24 +00:00
cache_clear_all();
drupal_goto('admin/block');
2004-10-31 07:34:47 +00:00
default:
// Always evaluates to TRUE, but a validation step may be added later.
if (!$edit) {
$edit = db_fetch_array(db_query("SELECT pages, visibility, custom FROM {blocks} WHERE module = '%s' AND delta = '%s'", $module, $delta));
}
// Module-specific block configurations.
if ($settings = module_invoke($module, 'block', 'configure', $delta)) {
$form = form_group(t('Block-specific settings'), $settings);
}
// Get the block subject for the page title.
$info = module_invoke($module, 'block', 'list');
drupal_set_title(t("'%name' block", array('%name' => $info[$delta]['info'])));
2004-10-14 15:28:24 +00:00
2004-10-31 07:34:47 +00:00
// Standard block configurations.
$group = form_radios(t('Show on specific pages'), 'visibility', $edit['visibility'], array(t('Show on every page except the listed pages.'), t('Show on only the listed pages.')));
$group .= form_textarea(t('Pages'), 'pages', $edit['pages'], 40, 5, t("Enter one page per line as Drupal paths. The '*' character is a wildcard. Example paths are '<em>blog</em>' for the blog page and '<em>blog/*</em>' for every personal blog. '<em><front></em>' is the front page. "));
$group .= form_radios(t('User options'), 'custom', $edit['custom'], array(t('Users may not turn on or off this block.'), t('Users may turn this block on or off, on by default.'), t('Users may turn this block on or off, off by default.')), t('Users can decide which blocks they want on or off on their account editing page.'));
$form .= form_group(t('Visibility settings'), $group);
$form .= form_submit(t('Save block'));
print theme('page', form($form));
}
}
/**
* Menu callback; displays the block creation form.
*/
function block_box_add() {
$edit = $_POST['edit'];
$op = $_POST['op'];
switch ($op) {
case t('Save block'):
block_box_save($edit);
drupal_set_message(t('The new block has been added.'));
drupal_goto('admin/block');
default:
$form = block_box_form();
$form .= form_submit(t('Save block'));
$output .= form($form);
}
print theme('page', $output);
}
/**
* Menu callback; confirm and delete custom blocks.
*/
function block_box_delete($bid = 0) {
$op = $_POST['op'];
$box = block_box_get($bid);
switch ($op) {
2004-10-14 15:28:24 +00:00
case t('Delete'):
db_query('DELETE FROM {boxes} WHERE bid = %d', $bid);
2004-10-31 07:34:47 +00:00
drupal_set_message(t('The block %name has been deleted.', array('%name' => '<em>'. $box['info'] .'</em>')));
2004-10-14 15:28:24 +00:00
cache_clear_all();
drupal_goto('admin/block');
default:
2004-10-31 07:34:47 +00:00
$form = '<p>'. t('Are you sure you want to delete the block %name?', array('%name' => '<em>'. $box['info'] .'</em>')) ."</p>\n";
$form .= form_submit(t('Delete'));
$output = form($form);
2004-05-11 20:10:14 +00:00
}
print theme('page', $output);
2002-05-02 19:13:45 +00:00
}
function block_box_form($edit = array()) {
2004-10-14 15:28:24 +00:00
$output = form_textfield(t('Block title'), 'title', $edit['title'], 50, 64, t('The title of the block as shown to the user.'));
$output .= filter_form('format', $edit['format']);
$output .= form_textarea(t('Block body'), 'body', $edit['body'], 70, 10, t('The content of the block as shown to the user.'));
$output .= form_textfield(t('Block description'), 'info', $edit['info'], 50, 64, t('A brief description of your block. Used on the <a href="%overview">block overview page</a>.', array('%overview' => url('admin/block'))));
2002-05-02 19:13:45 +00:00
2004-10-31 07:34:47 +00:00
return $output;
2002-05-02 19:13:45 +00:00
}
2004-10-31 07:34:47 +00:00
function block_box_save($edit, $delta = NULL) {
The Input formats - filter patch has landed. I still need to make update instructions for modules and update the hook docs.
Here's an overview of the changes:
1) Multiple Input formats: they are complete filter configurations (what filters to use, in what order and with which settings). Input formats are admin-definable, and usage of them is role-dependant. For example, you can set it up so that regular users can only use limited HTML, while admins can free HTML without any tag limitations.
The input format can be chosen per content item (nodes, comments, blocks, ...) when you add/edit them. If only a single format is available, there is no choice, and nothing changes with before.
The default install (and the upgrade) contains a basic set of formats which should satisfy the average user's needs.
2) Filters have toggles
Because now you might want to enable a filter only on some input formats, an explicit toggle is provided by the filter system. Modules do not need to worry about it and filters that still have their own on/off switch should get rid of it.
3) Multiple filters per module
This was necessary to accomodate the next change, and it's also a logical extension of the filter system.
4) Embedded PHP is now a filter
Thanks to the multiple input formats, I was able to move the 'embedded PHP' feature from block.module, page.module and book.module into a simple filter which executes PHP code. This filter is part of filter.module, and by default there is an input format 'PHP', restricted to the administrator only, which contains this filter.
This change means that block.module now passes custom block contents through the filter system.
As well as from reducing code duplication and avoiding two type selectors for page/book nodes, you can now combine PHP code with other filters.
5) User-supplied PHP code now requires <?php ?> tags.
This is required for teasers to work with PHP code. Because PHP evaluation is now just another step in the filter process, we can't do this. Also, because teasers are generated before filtering, this would result in errors when the teaser generation would cut off a piece of PHP code.
Also, regular PHP syntax explicitly includes the <?php ?> tags for PHP files, so it makes sense to use the same convention for embedded PHP in Drupal.
6) Filter caching was added.
Benchmarking shows that even for a simple setup (basic html filtering + legacy URL rewriting), filtercache can offer speedups. Unlike the old filtercache, this uses the normal cache table.
7) Filtertips were moved from help into a hook_filter_tips(). This was required to accomodate the fact that there are multiple filters per module, and that filter settings are format dependant. Shoehorning filter tips into _help was ugly and silly. The display of the filter tips is done through the input format selector, so filter_tips_short() no longer exists.
8) A more intelligent linebreak convertor was added, which doesn't stop working if you use block-level tags and which adds <p> tags.
2004-08-10 18:34:29 +00:00
if (!filter_access($edit['format'])) {
$edit['format'] = FILTER_FORMAT_DEFAULT;
2002-10-26 15:17:26 +00:00
}
2004-10-31 07:34:47 +00:00
if (isset($delta)) {
db_query("UPDATE {boxes} SET title = '%s', body = '%s', info = '%s', format = %d WHERE bid = %d", $edit['title'], $edit['body'], $edit['info'], $edit['format'], $delta);
2002-05-02 19:13:45 +00:00
}
else {
The Input formats - filter patch has landed. I still need to make update instructions for modules and update the hook docs.
Here's an overview of the changes:
1) Multiple Input formats: they are complete filter configurations (what filters to use, in what order and with which settings). Input formats are admin-definable, and usage of them is role-dependant. For example, you can set it up so that regular users can only use limited HTML, while admins can free HTML without any tag limitations.
The input format can be chosen per content item (nodes, comments, blocks, ...) when you add/edit them. If only a single format is available, there is no choice, and nothing changes with before.
The default install (and the upgrade) contains a basic set of formats which should satisfy the average user's needs.
2) Filters have toggles
Because now you might want to enable a filter only on some input formats, an explicit toggle is provided by the filter system. Modules do not need to worry about it and filters that still have their own on/off switch should get rid of it.
3) Multiple filters per module
This was necessary to accomodate the next change, and it's also a logical extension of the filter system.
4) Embedded PHP is now a filter
Thanks to the multiple input formats, I was able to move the 'embedded PHP' feature from block.module, page.module and book.module into a simple filter which executes PHP code. This filter is part of filter.module, and by default there is an input format 'PHP', restricted to the administrator only, which contains this filter.
This change means that block.module now passes custom block contents through the filter system.
As well as from reducing code duplication and avoiding two type selectors for page/book nodes, you can now combine PHP code with other filters.
5) User-supplied PHP code now requires <?php ?> tags.
This is required for teasers to work with PHP code. Because PHP evaluation is now just another step in the filter process, we can't do this. Also, because teasers are generated before filtering, this would result in errors when the teaser generation would cut off a piece of PHP code.
Also, regular PHP syntax explicitly includes the <?php ?> tags for PHP files, so it makes sense to use the same convention for embedded PHP in Drupal.
6) Filter caching was added.
Benchmarking shows that even for a simple setup (basic html filtering + legacy URL rewriting), filtercache can offer speedups. Unlike the old filtercache, this uses the normal cache table.
7) Filtertips were moved from help into a hook_filter_tips(). This was required to accomodate the fact that there are multiple filters per module, and that filter settings are format dependant. Shoehorning filter tips into _help was ugly and silly. The display of the filter tips is done through the input format selector, so filter_tips_short() no longer exists.
8) A more intelligent linebreak convertor was added, which doesn't stop working if you use block-level tags and which adds <p> tags.
2004-08-10 18:34:29 +00:00
db_query("INSERT INTO {boxes} (title, body, info, format) VALUES ('%s', '%s', '%s', %d)", $edit['title'], $edit['body'], $edit['info'], $edit['format']);
2002-05-02 19:13:45 +00:00
}
}
2004-05-11 20:10:14 +00:00
/**
2004-05-17 22:00:06 +00:00
* Menu callback; displays the block overview page.
2004-05-11 20:10:14 +00:00
*/
2000-12-23 15:20:10 +00:00
function block_admin() {
2004-05-11 20:10:14 +00:00
$edit = $_POST['edit'];
$op = $_POST['op'];
2001-06-20 20:00:40 +00:00
2004-05-11 20:10:14 +00:00
if ($op == t('Save blocks')) {
drupal_set_message(block_admin_save($edit));
cache_clear_all();
2004-09-17 22:07:17 +00:00
drupal_goto($_GET['q']);
2001-06-20 20:00:40 +00:00
}
2004-05-11 20:10:14 +00:00
print theme('page', block_admin_display());
2000-12-23 15:20:10 +00:00
}
2001-11-01 11:00:51 +00:00
2004-05-11 20:10:14 +00:00
/**
* Implementation of hook_user().
*
* Allow users to decide which custom blocks to display when they visit
* the site.
*/
2004-06-27 19:10:52 +00:00
function block_user($type, $edit, &$user, $category = NULL) {
2002-05-02 19:13:45 +00:00
switch ($type) {
2004-05-17 14:50:58 +00:00
case 'form':
2004-06-27 19:10:52 +00:00
if ($category == 'account') {
2004-10-31 07:34:47 +00:00
$result = db_query('SELECT * FROM {blocks} WHERE status = 1 AND custom != 0 ORDER BY weight, module, delta');
2004-06-27 19:10:52 +00:00
while ($block = db_fetch_object($result)) {
$data = module_invoke($block->module, 'block', 'list');
if ($data[$block->delta]['info']) {
2004-10-31 07:34:47 +00:00
$form .= form_checkbox($data[$block->delta]['info'], 'block]['. $block->module .']['. $block->delta, 1, isset($user->block[$block->module][$block->delta]) ? $user->block[$block->module][$block->delta] : ($block->custom == 1));
2004-06-27 19:10:52 +00:00
}
2002-05-12 15:40:57 +00:00
}
2004-06-27 19:10:52 +00:00
if (isset($form)) {
return array(array('title' => t('Block configuration'), 'data' => $form, 'weight' => 2));
}
2002-05-02 19:13:45 +00:00
}
2002-11-16 14:28:22 +00:00
break;
2004-05-11 20:10:14 +00:00
case 'validate':
if (!$edit['block']) {
$edit['block'] = array();
2002-09-30 09:19:50 +00:00
}
return $edit;
2002-05-02 19:13:45 +00:00
}
}
2003-11-19 16:13:07 +00:00
/**
* Return blocks available for current $user at $region.
*
2003-12-08 06:32:19 +00:00
* @param $region main|left|right
2003-11-19 16:13:07 +00:00
*
2003-12-08 06:32:19 +00:00
* @return array of block objects, indexed with <i>module</i>_<i>delta</i>
2003-11-19 16:13:07 +00:00
*
2004-06-18 15:04:37 +00:00
* @see <a href="http://drupal.org/node/1042" target="_top">[feature]
2003-11-19 16:13:07 +00:00
* Generic template design difficult w/o block region "look-ahead"</a>
2003-12-08 06:32:19 +00:00
* @todo add a proper primary key (bid) to the blocks table so we don't have
2003-11-19 16:13:07 +00:00
* to mess around with this <i>module</i>_<i>delta</i> construct. currently,
* "blocks" has no primary key defined (bad)!
*/
function block_list($region) {
2004-06-02 18:49:22 +00:00
global $user, $base_url;
2003-11-19 16:13:07 +00:00
static $blocks = array();
if (!isset($blocks[$region])) {
$blocks[$region] = array();
2004-10-31 07:34:47 +00:00
$result = db_query('SELECT * FROM {blocks} WHERE status = 1 '. ($region != 'all' ? 'AND region = %d ' : '') .'ORDER BY weight, module', $region == 'left' ? 0 : 1);
2003-11-19 16:13:07 +00:00
while ($result && ($block = db_fetch_array($result))) {
2004-10-31 07:34:47 +00:00
// Use the user's block visibility setting, if necessary
if ($block['custom'] != 0) {
if ($user->uid && isset($user->block[$block['module']][$block['delta']])) {
$enabled = $user->block[$block['module']][$block['delta']];
}
else {
$enabled = ($block['custom'] == 1);
}
}
else {
$enabled = TRUE;
2004-02-25 21:19:31 +00:00
}
2004-08-06 11:10:15 +00:00
// Match path if necessary
2004-10-31 07:34:47 +00:00
if ($block['pages']) {
2004-08-06 11:10:15 +00:00
$base = parse_url($base_url);
$session = session_name() .'='. session_id();
2004-08-06 11:11:30 +00:00
$url = str_replace(array($base['path'], '?'. $session), '', request_uri());
2004-08-06 20:15:32 +00:00
$url = ereg_replace('^/(\?q=)?', '', $url);
2004-10-31 07:34:47 +00:00
$regexp = '/^('. preg_replace(array('/(\r\n?|\n)/', '/\\\\\*/', '/(^|\|)\\\\<front\\\\>($|\|)/'), array('|', '.*', '\1\2'), preg_quote($block['pages'], '/')) .')$/';
$matched = !($block['visibility'] xor preg_match($regexp, $url));
2004-08-06 11:10:15 +00:00
}
else {
2004-10-31 07:34:47 +00:00
$matched = TRUE;
2004-08-06 11:10:15 +00:00
}
2004-10-31 07:34:47 +00:00
if ($enabled && $matched) {
// Check the current throttle status and see if block should be displayed
// based on server load.
2004-11-07 22:47:00 +00:00
if (!($block['throttle'] && (module_invoke('throttle', 'status') > 0))) {
2004-08-22 17:03:42 +00:00
$array = module_invoke($block['module'], 'block', 'view', $block['delta']);
2004-09-08 15:38:26 +00:00
if (is_array($array)) {
2004-08-22 17:03:42 +00:00
$block = array_merge($block, $array);
}
2003-11-28 20:03:00 +00:00
}
2003-12-04 20:53:19 +00:00
if (isset($block['content']) && $block['content']) {
2003-11-19 16:13:07 +00:00
$blocks[$region]["$block[module]_$block[delta]"] = (object) $block;
}
}
}
}
return $blocks[$region];
}
2003-06-24 15:55:22 +00:00
?>
