Submitted by WITTMANN Balázs Ádám on 2014-09-26, Friday, 12:46
Submitted by CSÉCSY László on 2014-08-06, Wednesday, 11:32
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.
Submitted by CZÖVEK András on 2014-06-12, Thursday, 08:33
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:
Submitted by CSÉCSY László on 2014-01-10, Friday, 13:29
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:
Submitted by CZÖVEK András on 2014-01-09, Thursday, 11:23
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.
Submitted by CZÖVEK András on 2013-11-26, Tuesday, 17:29
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.
Submitted by CSÉCSY László on 2011-09-09, Friday, 14:50
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:
Submitted by CSÉCSY László on 2010-02-01, Monday, 10:03
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 drupal.org'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>.