Drupal API

Views Bulk Operations come handy when doing bulk operations over a selected list. This is great because it combines the power of views to filter the selection and specific actions to do on each selected entity. For Ex: Updating some field in the record, deleting selected entity and so on.

Views also provide an easier way to define your own set of custom functions to perform on each selected row of entities.

First, we need to define an action :

This post would reflect on few essential APIs in Drupal 7 and how they were changed in Drupal 8:

drupal_get_title(): Gets the title of the current page. Link to changelog here .
Drupal 7:

Drupal provides nice theming options for table display. However, various options available using tabular display are not documented well. This article will try to list various options to use when creating tables using drupal theme functions.

Creating a table display:

Displaying data for any entity fields with formatting can be achieved with 2 simple drupal api.

field_get_items: Returns the field items in the language they currently would be displayed.
field_view_value: Returns a renderable array for a single field value.

Example:

Both l and url methods are handy to create urls for various entities. However, the variety of options available makes the usage exciting and complex.

l(): Formats an internal or external URL link as an HTML anchor tag.
Syntax: l($text, $path, array $options = array())

Creating an absolute URL using l(). The example below creates a node link.

This can be achieved using hook_node_view

We may want to get the options available for a field in content type. This can be achieved using Field API.

This post will illustrate various handy file operations available in Drupal

Get Absolute Path of a file from URI : drupal_realpath()
A URI in drupal looks like: private://donor_registration/somefile.csv for a private file
Absolute Path: /srv/www/example.com/public_html/sites/default/private/files/donor_registration/somefile.csv

There are times when we would want to create similar data structures across multiple drupal sites for common functionalities. Although this can be done using features but when the effort involves one time exercise and involves just few fields to be exported, using custom code for creating export definitions for importing in the other site can be a simpler alternative.

If you want export a field definition, you can use the handy field_info_field and field_info_instance functions. Taking our example above, here's how you would call these two functions: