You are here

Drupal Planet

WITTMANN Balázs Ádám's picture

Using PHP_CodeSniffer in PhpStorm

PHP_CodeSniffer is a PHP5 script, which can validate PHP, JavaScript and CSS type source codes according to the different coding standards. In other words, you can easily check your source code’s standardization with a script, instead of knowing every detail about the coding standards by heart. You can use PHP_CodeSniffer in different ways, for example you can run it simply from terminal but thanks for the PhpStorm’s built-in support it becomes a much more effective tool.

CZÖVEK András's picture

Applying node access on a non-node based view

The Views module automatically joins the node_access table only for node based views. In any other case we need to take care of the proper access handling ourselves.

CSÉCSY László's picture

Exporting image field defaults in D7

We all love image fields' defaults: it's so easy to have a hero image for a product or a colleague's profile even when the editor does not provide one, with all the niceties such as displaying it with various image styles in a list, in the teaser or on the actual page. We all love Features module as it allows us to export Drupal 7 content types with all its settings.

CZÖVEK András's picture

Ctools export API

In one of our recent projects we used the Commerce Custom Order Status module to create custom commerce order statuses from the UI. The problem with this module was however that the created statuses (living in the module's own database table) were not exportable.

To make a module's custom database table exportable with features you have 3 options:

CSÉCSY László's picture

Building a web service with Drupal 7

1. The task

We built a site over a year ago which allows placing orders after the visitor has selected an offer. Our customer asked to implement a web service that allows submitting orders from a 3rd-party service (eg. from a mobile app).

2. What to do?

Such a web service should consist of at least four calls:

CZÖVEK András's picture

New module: Field collection tabs widget

Data belonging to a drupal entity often can be added only by combining several fields. An example for such data can be a person with a name, a birth date and a place of birth. The most popular solution to make this kind of data multivalue is the Field Collection module. We love this module a lot but viewing and editing big field collections can be daunting.

CZÖVEK András's picture

Entity reference - customizability at its best

The Entity reference module is one of the most used Drupal modules. At the moment of writing it is 51st on the usage list of Drupal projects. Those who have already made a Drupal site probably have knows it. At the same time, not many know what a powerful tool it can be even in special cases.

CSÉCSY László's picture

The fairy tale of the multi-person, multi-environment Drupal development

The slides of my session are available for download here as PDF, the code base is available at Github:

CSÉCSY László's picture

Installation profile: default features instead of overriden ones, by default

Most likely I am not the only one who has run into the problem: if an own Drupal 7 installation profile enables a feature (a module created with the help of Features), then it gets overridden even for the first visit to the site. How can we avoid this situation?

First of all, prepare our feature modules properly, so they will not have problems! Practically this means Kit compatibility, especially:

CSÉCSY László's picture

Show result list of a view with exposed filters only when filters set

There is a (Views2) view listing any type of elements and with at least one exposed filter. The task is to show the empty text instead of the list if the filter is not set. One part of the solution can be found at's forum, but is not perfect. It works fine while every part of the exposed filters are textfields - but there are views with optional filters shown as dropdowns/selects with the first, "empty" element being <All>.