Tips and Tricks

There is a lot of terminology specific to Drupal and it is easier when your clients get used to the odd language you are using. This is made overly complicated by the Drupal community sometimes messing up these terms by making them ambiguous or contradictory.

This came up today and did a little bit of digging and testing to find a solution.

One of the things most startling about Drupal 8 is the lack of documentation or false documentation on many simple everyday tasks. I went looking for how to set a (date) field on an entity form when another entity was selected from an entity reference autocomplete field on that form.

It took me a while to track this down so I wanted to post it somewhere. In the past I would have posted to api.drupal.org but it seems as though that has been rendered useless in D8 as each new release of D8 (8.3, 8.4, etc) hides the previous comments.

Thanks to jedihe for posting this great tip: https://www.drupal.org/node/2313791#comment-11469881

$view = views_get_view('machine_name_of_my_view');
$source_display = 'machine_name_of_the_overridden_display';

DrupalCamp Ottawa 2015 was held at the University of Ottawa on July 24. It is a 1 day Drupal camp for Drupal users, developers, site builders and those just wanting to check out Drupal for the first time.

Just stumbled upon this core bug today and thought i would post for a couple reasons:

We are currently involved in multiple bilingual Drupal 7 projects. As we proceed with development we are coming across numerous i18n related issues. I thought it might be useful to list the various issues/fixes/patches/solutions we are providing all in one spot.

For many bilingual websites, the standard Language Switcher block that comes with the locale module (shows both language links in one block)  will suffice.