Hide the users icon in administration menu

I'm a huge fan of Administration menu, even more than projects like admin, toolbar or possibly others out there. If you want to delete some items from the menu, you need to implement hook_menu_link_alter() and reset the $item. Following snippets removes the users icon which shows the number of anonymous and authenticated users. Simple and powerfull.

* Implementation of hook_menu_link_alter().
function swentel_menu_link_alter(&$item, $menu) {
  if (
$item['title'] == 'icon_users') {
$item = NULL;

Drupalcon San Francisco and Display Suite

Due to Volcano activity on Iceland, I wasn't able to get to San Francisco for the biannual DrupalCon fest. But the Drupal community is that enthousiastic that we are setting up our own DrupalVolCon parties in Europe, already going on in London, Paris and in Antwerp. I'm supposed to give a session about Display Suite on wednesday, and that still might happen: we're busy testing and setting up streaming servers so we are able to stream our presentation on the internet at the time our sessions should take place in SF. All looks fine for now, so take that Eyjafjallajökull!

If you want to attend the session in Belgium, more info is available on http://belgium.drupalvolcon.com/

Update: we recorded the session and it's now available also on vimeo. Slides are at the bottom.

Display Suite profile

Related to our presentation, we just created a Display Suite profile containing all modules which are supported by Display Suite. We don't enable all modules by default in the installation profile, we just wanted to package them all, so you know what's possible.

We also packaged the Nodeform Columns module which enables you to organise your node forms in an easy way. If you don't really care about fieldgroups on the node form page, but need them on the front-end, you don't need to enable fieldgroups from CCK. The same applies to the tabs and cck fieldgroup tabs module, which are also included in the profile. Display Suite has this functionality by default.

You can see the full list of modules at http://drupal.org/node/775524, together with downloads of the profile and the packaged version of all modules with or without Drupal core included.

Important: some modules (like gmap and location) require the dev version to work properly, but for obvious reasons, the packed profile only contains official releases.

Anyway, sad I'm not there, but we're having fun here also!

Display Suite 1.1 'Fieldgroups baby'

After 2 months of hard work, we're proud to present you a new stable release of Display Suite and two new modules implementing the API, User displays and Views displays. A list of new features and bugfixes is available on the release notes of DS 6.x-1.1, make sure to read them as we had to introduce 2 small API changes. If you choose to upgrade, make sure you upgrade all other implementations too. A summary of cool new features:

  • Support for fieldgroups: the number one feature request by many users. You don't necessarily have to enable the fieldgroups module which comes with CCK, you can create as many as you like with the DS API via the interface. As a bonus, when the tabs module is enabled, you can change the output of your fieldgroups to tabs.
  • User Displays: first release which has support for the core profile module. Theming of the user profile finally got nice, especially in combination with fieldgroups support.
  • Views Displays: drag and drop your views, also with support for the Views attach module.
  • Region to block plugin: exposes regions per content type and build mode to a block.
  • Various other small new features like adding styles, simple panels support, location/gmap and syncing and copying display settings from one build mode to another.

New screencasts are available showing the new features and our demo site is also still available.

The roadmap has been updated, next focus is creating a full working version for Drupal 7. In the meantime, enjoy and see you hopefully at Drupalcon for our session about Display Suite!

New Display Suite toys: Views displays and ND Location

We've been quite busy with Display Suite since the first release. A lot of issues have been fixed and fieldgroups integration, the number one feature request by anyone out there, is almost done. We also created two new, rather small - but cool - modules which integrate perfectly with DS.

  • ND location: integrates with the location and Gmap modules. All location properties will be exposed as separate fields and you get an extra field which opens the marker info window on google maps, ideal for an overview page. We'll add a few other cool goodies to make this module rock even harder than it already does.
  • Views displays: all variables in the views.tpl.php are now 'fields' which you can put in the default set of regions. Extra fields/data are now very ease to add to your views displays.

You can see the power when combining these 2 modules in this short screencast. You can also click around on our demo site, still on the same URL, at http://demo.customsource.be/location.

Contextual links backport - more or less

Drupal 7 now comes with the contextual module which makes it very easy to edit your site as there are inline action links available on your content, blocks and so on. There are a few modules out there available for D6 - block edit and admin:hover come to mind - which offer the same functionality but are different when it comes to interface and/or extendability.

We decided to write a new module from scratch with the UI in mind of the D7 version, also taking care of performance and the need for easy extendability including hooks (duh) and static actions which allows us to have a static variable during the page request which can collect stuff from all over the place. You can test it out at http://demo.customsource.be/content/home with demo/demo. Surf to the 'articles' page which has contextual links for views, nodes & blocks.

What happens next ?

  • I could contrib this back and ignore all other efforts out there.
  • Merge this with block edit (or another) but with another branch (and also another name).
  • Commit this as a complete new project but with a good comparison to other modules.
  • Simply do nothing, saves me another project I need to maintain .. :)

So, let me know what you think, add comments, mail or ping me on IRC if you want to have a talk about this.

Update 17/03: code is available at http://github.com/swentel/contextual


Subscribe to RSS - drupal

You are here