Drupal

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:

Shortly after publishing CTOG on drupal.org, Drupal Radar came up with a short review of it. Let me describe the main differences between CTOG and Open Atrium (referred to as OA from now on), after I had a thoughtful conversation with the OA guys at the #open_atrium IRC channel.

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>.

We have two roles: documentation-builders and customers. The documentation-builders want to hide some content from the customers, but they want some contents to be editable by the customers. The hiding part can be done with the nodeaccess.module - but how should we do the latter?