August 2012

Multilingual challenge: Node vs. Field

Katrin Fartaček's picture
Katrin Fartaček

So there was a DrupalCon in Munich and we were there! Many people, much information and a lot of excitement for Drupal 8! One of the best sessions I attended was by Suzanne Kennedy (aka pixelite) about "Multilingual Content in Drupal 7 & 8".

I always had trouble which translation type to choose, because I didn't get the difference between all those field translation, entity translation, i18something,... modules. Well, pixelite cleared it up for me!

Here is how to decide between Node level and Field level Translation.

Ready for the basket?

Florian Engel's picture
Florian Engel

One of the most complicated user interfaces in CRM systems is frequently the profiling interface. You want to sort your contacts, filter them and literally create formulas of filters that you can save.
In this blogpost I'll introduce a rough concept we've been working on. Hopefully we'll be able to implement it as part of Redhen CRM some time soon.

Rethinking Drupal's block placement interface

Florian Engel's picture
Florian Engel

Drupal's user experience and interfaces have gotten a lot better with Drupal 7. Still, there are a few areas that need more work.
One of those areas is the process of adding blocks, configuring them and placing them on the desired pages. In this blogpost I want to outline a few ideas on how it could be improved and maybe we can actually turn some of those interfaces into a module.

Removing a default field from the default palette of form_builder

Matthias Weiss's picture
Matthias Weiss

When you're using form_builder you possible want to remove some of the form elements from the palette of fields to show the users only those elements they need. I can show you a simple although not really elegant way to achieve this.

Adding your own fields to the field palette of form_builder

Matthias Weiss's picture
Matthias Weiss

The form_builder module is a handy thing when you want to create webforms in drupal. Its drag & drop UI is really user friendly and for our project "advocacy engine" we want just that. But what if you want to add your own webform fields to the palette where you can drag from? Then you need to use the form_builder API which is not that easy to program against.