This should work:

<?php
$block = module_invoke('locale', 'block_view', 'language');
print render($block);
?>

Unfortunately, in my D7 it does not. What does work is this:

Add to template.php:

<?php
function block_render($module, $block_id) {
  $block = block_load($module, $block_id);
  $block_content = _block_render_blocks(array($block));
  $build = _block_get_renderable_array($block_content);
  $block_rendered = drupal_render($build);
  return $block_rendered;
}
?>

Add to page.tpl.php

<?php
  print block_render('locale', 'language');
?>

Now that the language switcher is rendering, you might want to customize its appeareance

By default, it produces an unordered list with each item in a new line and a bullet before each item. Not a big fan of this look.

With the following CSS code you’ll have an inline language switcher, with li items separed by “/”.

/* language switcher */
ul.language-switcher-locale-url{
list-style: none;
display: inline;
}
 
ul.language-switcher-locale-url li{
display: inline;
}
 
ul.language-switcher-locale-url li:after{
   content: "/";
}
 
ul.language-switcher-locale-url li:last-child:after{
   content: "";
}

For more advanced styling options, check this link.

You can list all the views defined at your Oracle database by having a look at all_views table which stores the following information of each view:

SQL> DESC all_views;
 Name					   NULL?    TYPE
 ----------------------------------------- -------- ----------------------------
 OWNER					   NOT NULL VARCHAR2(30)
 VIEW_NAME				   NOT NULL VARCHAR2(30)
 TEXT_LENGTH					    NUMBER
 TEXT						    LONG
 TYPE_TEXT_LENGTH				    NUMBER
 TYPE_TEXT					    VARCHAR2(4000)
 OID_TEXT_LENGTH				    NUMBER
 OID_TEXT					    VARCHAR2(4000)
 VIEW_TYPE_OWNER				    VARCHAR2(30)
 VIEW_TYPE					    VARCHAR2(30)
 SUPERVIEW_NAME 				    VARCHAR2(30)

The query information is stored in “text” row. So, let’s retrieve the query that our AUTORESUZ has defined:

SQL> SELECT text FROM all_views WHERE view_name = 'AUTORESUZ';
 
TEXT
----------
SELECT a1.

OMFG! The query seems to be there, but it is truncated…

In order to view the full query, you must set long with a value greater that text’s length. Like this:

SQL> SELECT text_length FROM all_views WHERE view_name = 'AUTORESUZ';
 
TEXT_LENGTH
-----------
	369
 
SQL> SELECT text FROM all_views WHERE view_name = 'AUTORESUZ';
 
TEXT
----------
SELECT a1.
 
SQL> SET long 369
SQL> SELECT text FROM all_views WHERE view_name = 'AUTORESUZ';         
 
TEXT
--------------------------------------------------------------------------------
SELECT a1.rec_key AS arecord,
  REGEXP_REPLACE(a2.rec_data,'^\|a(.*)','\1') AS nipuz,
  REGEXP_REPLACE(REGEXP_REPLACE(REGEXP_REPLACE(a1.rec_data,'^\|a(.*)\|6\(UZ.*','
\1'), '(.*)\|c(.*)','\1'), '(.*),\|d(.*)','\1') AS autoruz
 
 FROM var_fields2 a1,  var_fields2 a2
 WHERE a1.rec_key LIKE 'a%' AND a1.MARC_TAG='100' AND
  (a1.rec_key=a2.rec_key AND a2.MARC_TAG='090')

And there is a videotutorial as well.

The above show how to configure breadcrumbs in nodes, but… how to display breadcrumbs in Views pages?

This struggled me for a while, because I was taking the (limited) instructions too literally.

To create a breadcrumb to a views page display that has a path like “/path/to/my-view” just use that as the path (as it isn’t an alias). To know the path, go to your view and edit it (admin/structure/views/view/VIEWNAME/edit) and refer to the Page Settings – Path value.

Also, leave the “Arguments” and “Selection rules” empty, then setup your breadcrumbs as you did with nodes.

Let’s see an example. First, the path to the view:

Path breadcrumbs in views

And the path breadcrumbs configuration:

drupal 7 Path breadcrumbs in views

And here is the resulting breadcrumb. Remember that your theme’s page.tpl.php must print $breadcrumb or you will not see breadcrumbs at all…

# Follow symbolic links in this directory.
Options +FollowSymLinks

Some web hosts tighten up security settings and now forbid +FollowSymLinks option in .htaccess. This causes an 500 error when accesing the site.

The fix is quite simple. Just replace +FollowSymLinks with +SymLinksIfOwnerMatch. So edit the lines above to this:

# Follow symbolic links in this directory.
# comment this one...
# Options +FollowSymLinks
# add this new line...
Options +SymLinksIfOwnerMatch

The issue should be fixed.

Please note that there is not just one .htacess file in your Drupal 7 site. There is one in / and usually there are other .htaccess files that must be modified too, for instance in sites/default/files. You must change that one too or every image that you upload to your Drupal 7 site won’t be rendered…

Discussion about this topic available here: http://drupal.org/node/1269780

def truncate_string(mystring, numberofwords):
    return ' '.join(mystring.split()[:numberofwords])

An example of use:

>>> sample_string = "hello world this is a string"
>>> print truncate_string(sample_string,2)
hello world

2013-04-17 08:31:30 --> 2013-04-17 08:31:30 --> Updating task status to ERROR.
2013-04-17 08:31:30 --> Task #21731 finished. [ERROR]

Calling inveniogc with verbose level = 9 I got some more information (var/log/bibsched_task_XXXX.log and .err files):

2013-04-17 08:29:51 --> - deleting queries not attached to any user
 
2013-04-17 08:29:51 -->   SELECT DISTINCT q.id
  FROM query AS q LEFT JOIN user_query AS uq
  ON uq.id_query = q.id
  WHERE uq.id_query IS NULL AND
  q.type <> 'p' 
 
2013-04-17 08:31:30 --> 2013-04-17 08:31:30 --> Updating task status to ERROR.
2013-04-17 08:31:30 --> Task #21731 finished. [ERROR]

The issue arised when inveniogc tried to delete user queries not attached to any user. I edited lib/python/invenioinveniogc.py and noticed the error was being produced by the output of a query result being printed. Just commented that out and inveniogc works again:

write_message("""  SELECT DISTINCT q.id\n  FROM query AS q LEFT JOIN user_query AS uq\n  ON uq.id_query = q.id\n  WHERE uq.id_query IS NULL AND\n  q.type <> 'p' """, verbose=9)
result = run_sql("""SELECT DISTINCT q.id
                    FROM query AS q LEFT JOIN user_query AS uq
                    ON uq.id_query = q.id
                    WHERE uq.id_query IS NULL AND
                          q.type <> 'p'""")
 
# write_message(result, verbose=9)

Why is this? It seems that the output buffer that write_message is using is too small to store the result of the previous query, so it fails…

Thirty-second intro to Drupal theming

If you are new to Drupal, let me explain how the themes work.

Each theme is a directory (under sites/all/themes/yourthemename) with at least three files:

* The first one, the .info file, called yourthemename.info, describes the theme (regions, path to stylesheet, javascript files, blablabla).

* The second one, which contains the logic (php code) is called template.php, and

* the third one is the html markup file (ideally, with just some php print’s) called page.tpl.php.

The concept is quite simple: you generate some variables in template.php and print them in page.tpl.php.

Now that we understand the basics, you will find this examples quite self-explaining:

The dirty way: display Drupal form in page.tpl.php

First way to show a search box in your Drupal theme works as expected, but it is not the way you are supposed to implement it.

This adds the logic to show a search form directly in your View file (page.tpl.php).

This practice should be avoided, as there must not be any logic inside .tpl.php files… Anyway, Drupal allows it, so:

Edit page.tpl.php (in your theme folder, in /sites/default/MYTHEME) and add these two lines, which will render a block containing a search form:

<?php
// this is page.tpl.php
 
// insert a search_form here...
$block = module_invoke('search','block_view','form');
//  'search' is the module invoking the block. 
//  'block_view' is the operation we want to call, that is, we want to view the block, and 
//  'form' is the machine name of the block you want to print.
 
// You can get this information by hovering over the edit link on the block overview page at admin/structure/block
// Edit links will be in the form
//       /admin/structure/block/manage/MODULENAME/BLOCK_MACHINENAME/configure
 
 
// now we print the block...
print render($block);
?>

You can read more about module_invoke and render function in drupal documentation.

The right way: show a search block in your Drupal 7 theme

We can set a variable containing a search block in template.php:

<?php
// this is template.php, where the logic goes...
// replace MYTHEME with your theme name (like the theme folder containing the theme)
function MYTHEME_preprocess_page(&$variables)
{
    $block = module_invoke('search','block_view','search');
    $rendered_block = render($block);
    $variables['mysearchblock'] = $rendered_block;
}
?>

And then print that variable in your page.tpl.php file:

<?php
// this is page.tpl.php, where the presentation (view) is generated:
   // ... custom html stuff ...
 
   // print our rendered search block...
   print $mysearchblock;
?>

The right way: display Drupal 7 search form in theme

Instead of rendering the block, we will be rendering the form (not a block, but the full search form instead):

Let’s put the logic where it should be, in template.php:

<?php
// this is template.php, where the logic goes...
// replace MYTHEME with your theme name 
function MYTHEME_preprocess_page(&$variables)
{
    $search_box = drupal_render(drupal_get_form('search_form'));
    $variables['my_search_box'] = $search_box; 
}
?>

And then, in our page.tpl.php, just print that $my_search_box variable we just set earlier…

<php
// this is page.tpl.php
print $my_search_box
?>

If done like so, it will work and render the search form, but it will spit out something like
Strict warning: Only variables should be passed by reference in

This has to be with variables being passed as reference, and not creating an instance for those first. Read this for further information.

So, let’s fix it.

In template.php:

<?php
// this is template.php
 
function MYTHEME_preprocess_page(&$variables){
  // para poder usar una caja de búsqueda en los templates .tpl.php de Drupal 7...	
  $form = drupal_get_form('search_form');
  $cajabusqueda = drupal_render($form);
  $variables['cajabusqueda'] = $cajabusqueda;   
}?>

This was driving me nuts but I finally found how to make it work.

Scenario:
Drupal 7.21
Token 7.x-1.5
Pathauto 7.x-1.2
Admin theme: Seven

The fix
It seems that Seven theme is responsible for this. This theme has some issues with js/jQuery and won’t show (out of the box) the Pathauto pattern’s.

To fix it, just go to Appearance, scroll down to the bottom of the page and select “Bartik” or “Garland” instead of “Seven“.

Now save, and reload ?q=admin/config/search/path/patterns. The pattern tab info should be nicely displayed now.

If it works, you can try to activate Seven theme for admin again. In my case, it worked.

*** UPDATE 20130427***
If the steps above won’t fix the issue, then edit your php.ini field and try to increase memory_limit to a higher value. For instance, in my case I changed from:

memory_limit = 32M

To:

memory_limit = 64M

After updating php.ini do not forget to restart your web server!

Further information: http://drupal.org/node/1267966

When I looked at the code, I saw he was connecting to MySQL using MySQLdb connect function as in:

import MySQLdb as mdb
con = mdb.connect(host='localhost',user='myuser',passwd='mypassword',db='mydatabase')

And he was astonished because I was able to solve his problems just by changing that to:

import MySQLdb as mdb
con = mdb.connect(host='localhost',user='myuser',passwd='mypassword',db='mydatabase', charset='utf8', use_unicode=False)

So don’t underestimate the power of official documentation and please, RTFM!