Drupal Feeds

Drupal Association News: About Today's Board Resignation

Feeds from Drupal.org - Fri, 2014-06-13 17:44

Today Morten Hyde-Birch Jørgensen stepped down from his role on the Drupal Association's Board of Directors. The Drupal Association's Board of Directors supports Morten’s decision. The Drupal Association and the Drupal community value inclusivity and diversity, and our leadership must demonstrate those values as well.

We want to thank Morten for his service; he came to the board with a mission to foster improved transparency and communication. He helped both the board and staff embrace those principles in a way that will carry into the future.

Today’s development underscores the need for a broader discussion that we need to have about inclusivity and diversity. Creating and maintaining the right culture and environment is vital to Drupal's success. Therefore, we have asked the Community Working Group to define a process to help our community address these issues and identify positive, proactive, and concrete steps we can take to ensure that everyone feels welcome in Drupal. In any community, people will make mistakes. The real test of our community is how we respond to these issues.

Morten is vacating a community elected seat. The Board of Directors will discuss how and when to fill this vacancy at the next board meeting.

Respectfully,

The Drupal Association Board of Directors

Categories: Straight From Drupal

Getting Started as an Acquia Partner

Upcoming Webinars - Fri, 2014-06-13 17:37

Welcome to the Acquia Partner Program!

We know your time is valuable, so we’ve put together everything you need to know about Acquia into a 30 minute webinar.  During this webinar, we’ll give you an overview of Acquia, our partner program and the recommended next steps to get you started as an Acquia partner.

After this 30 minute session, you will understand:

Language Undefined

Drupal Watchdog: Caffeinated Drupal

Planet Drupal - Fri, 2014-06-13 17:28

Over our last cup of coffee we discussed content delivery networks (CDNs) and how they can dramatically speed up websites. This issue, we’ll take a look at how to swap out the backend storage used by Drupal’s Cache API. So, let’s grab a nice iced latte to toast the end of summer, and we’ll dive right in!

Pretty espresso machine

First of all, we should discuss the reasons why one might want to move Drupal’s cache storage out of MySQL. As Drupal sites grow, the amount of cache data will greatly increase. When this happens, the frequent querying of cache items, along with database updates to invalidate caches, can cause a heavy load on your database server. By moving cache data out of the database and into a key-value store such as Memcached or Redis, not only can we reduce load on the database, but we gain the ability to easily scale out the caching layer horizontally (adding more servers) as the need arises. This type of scaling is not something that’s easily accomplished with MySQL.

Memcached is by far the most popular alternate cache storage for Drupal, although Redis – a newer technology with some features not found in Memcached – has been growing in popularity. Both are what are referred to as “key value stores”, meaning when you store a piece of data (the value), you assign it a key so that you can easily retrieve it later. The design of these key value stores is such that they maintain a constant performance no matter how large the dataset grows. Imagine a coffee shop that always had a hot cup of coffee waiting for you in less than five seconds, no matter how much other coffee they were serving at the time.

It is a common misconception that retrieving a single cache item from Memcached or Redis should be faster than retrieving the same cache item from MySQL. This is typically not the case. However, both Memcached and Redis scale much better with large data sets, and moving caches out of MySQL speeds up the database for other queries. For these reasons, swapping the cache backend can still be a great performance win even though the speed for serving a single page to a single client may not improve at all.

Drupal Watchdog: Caffeinated Drupal

Feeds from Drupal.org - Fri, 2014-06-13 17:28

Over our last cup of coffee we discussed content delivery networks (CDNs) and how they can dramatically speed up websites. This issue, we’ll take a look at how to swap out the backend storage used by Drupal’s Cache API. So, let’s grab a nice iced latte to toast the end of summer, and we’ll dive right in!

Pretty espresso machine

First of all, we should discuss the reasons why one might want to move Drupal’s cache storage out of MySQL. As Drupal sites grow, the amount of cache data will greatly increase. When this happens, the frequent querying of cache items, along with database updates to invalidate caches, can cause a heavy load on your database server. By moving cache data out of the database and into a key-value store such as Memcached or Redis, not only can we reduce load on the database, but we gain the ability to easily scale out the caching layer horizontally (adding more servers) as the need arises. This type of scaling is not something that’s easily accomplished with MySQL.

Memcached is by far the most popular alternate cache storage for Drupal, although Redis – a newer technology with some features not found in Memcached – has been growing in popularity. Both are what are referred to as “key value stores”, meaning when you store a piece of data (the value), you assign it a key so that you can easily retrieve it later. The design of these key value stores is such that they maintain a constant performance no matter how large the dataset grows. Imagine a coffee shop that always had a hot cup of coffee waiting for you in less than five seconds, no matter how much other coffee they were serving at the time.

It is a common misconception that retrieving a single cache item from Memcached or Redis should be faster than retrieving the same cache item from MySQL. This is typically not the case. However, both Memcached and Redis scale much better with large data sets, and moving caches out of MySQL speeds up the database for other queries. For these reasons, swapping the cache backend can still be a great performance win even though the speed for serving a single page to a single client may not improve at all.

Categories: Straight From Drupal

Lullabot: Receive Desktop Notifications in Chrome for Drupal.org Tests

Planet Drupal - Fri, 2014-06-13 17:00

During the extended weekend sprints at DrupalCon Austin, I discovered what an enthusiastic test refresher I am. When you submit a patch to the Drupal core issue queue, and even some contributed modules, a handy testbot will come along and ensure that your proposed code changes don't break any existing tests. Like most people, I found myself with lots of tabs open, compulsively refreshing each one to see if my test had completed or not.

Lullabot: Receive Desktop Notifications in Chrome for Drupal.org Tests

Feeds from Drupal.org - Fri, 2014-06-13 17:00

During the extended weekend sprints at DrupalCon Austin, I discovered what an enthusiastic test refresher I am. When you submit a patch to the Drupal core issue queue, and even some contributed modules, a handy testbot will come along and ensure that your proposed code changes don't break any existing tests. Like most people, I found myself with lots of tabs open, compulsively refreshing each one to see if my test had completed or not.

Categories: Straight From Drupal

Receive Desktop Notifications in Chrome for Drupal.org Tests

Lullabot (via DrupalFire)

During the extended weekend sprints at DrupalCon Austin, I discovered what an enthusiastic test refresher I am. When you submit a patch to the Drupal core issue queue, and even some contributed modules, a handy testbot will come along and ensure that your proposed code changes don't break any existing tests. Like most people, I found myself with lots of tabs open, compulsively refreshing each one to see if my test had completed or not.

Categories: Drupal Universe

Drupal.org Featured Case Studies: The Official Beatles Website

Planet Drupal - Fri, 2014-06-13 13:45
The Official Beatles Website - built with DrupalCompleted Drupal site or project URL: http://www.thebeatles.com

Everybody has heard of The Beatles - their music has no doubt become part of the soundtrack of everybody's life and so much of it still sounds as good now as it did then. It's no surprise then that The Beatles have a huge fan base with millions of followers around the world and they expect engagement from the official website and social media channels.

Apple Records and Motherlode Media approached Drupology with a brief to create a new website for the band. The aim is to provide an experience and presentation similar to The Beatles Anthology book, i.e. snippets of text, quotes, never-before-seen imagery and video (ok, so video isn't in books, but you get the idea), and a very personal insight into the band, their music, and ideas at the time. The website also needs to promote new albums, merchandise, and events in a way that engages fans, although revenue conversion isn't a key requirement - it's more about creativity and experience.

Drupology, the technical lead, are a specialist Drupal digital marketing agency based in the UK and service many enterprise-level organisations with high-profile websites at home and around the world. We were delighted to be given the opportunity to work on such an iconic project.

Key modules/theme/distribution used: ViewsEntity APIEntity referenceEntity Reference View WidgetMediaFacebook APIComment blockChaos tool suite (ctools)FeedsCookie ControlCDNOrganizations involved: DrupologyTeam members: Dubs

Drupal.org Featured Case Studies: The Official Beatles Website

Feeds from Drupal.org - Fri, 2014-06-13 13:45
The Official Beatles Website - built with DrupalCompleted Drupal site or project URL: http://www.thebeatles.com

Everybody has heard of The Beatles - their music has no doubt become part of the soundtrack of everybody's life and so much of it still sounds as good now as it did then. It's no surprise then that The Beatles have a huge fan base with millions of followers around the world and they expect engagement from the official website and social media channels.

Apple Records and Motherlode Media approached Drupology with a brief to create a new website for the band. The aim is to provide an experience and presentation similar to The Beatles Anthology book, i.e. snippets of text, quotes, never-before-seen imagery and video (ok, so video isn't in books, but you get the idea), and a very personal insight into the band, their music, and ideas at the time. The website also needs to promote new albums, merchandise, and events in a way that engages fans, although revenue conversion isn't a key requirement - it's more about creativity and experience.

Drupology, the technical lead, are a specialist Drupal digital marketing agency based in the UK and service many enterprise-level organisations with high-profile websites at home and around the world. We were delighted to be given the opportunity to work on such an iconic project.

Key modules/theme/distribution used: ViewsEntity APIEntity referenceEntity Reference View WidgetMediaFacebook APIComment blockChaos tool suite (ctools)FeedsCookie ControlCDNOrganizations involved: DrupologyTeam members: Dubs
Categories: Straight From Drupal

Localize.drupal.org: 1000 new translatable strings for Drupal 8 and the future of localize.drupal.org

Planet Drupal - Fri, 2014-06-13 13:24

As we kept following the changes made to Drupal 8 and the dozens of new ways of adding translatable strings to code in the new version, we worked on support for TWIG translation constructs and all kinds of YAML file sources (routing titles, menu items, action links, local tasks, configuration schemas, etc) recently as well as some misc new APIs like TranslationWrapper objects. Huge thanks to the amazing work of @ksenzee, @herom and @hron84 building string extraction support for these in our not very well loved issue queue.

Support for these APIs is now rolled out live on localize.drupal.org and I sent Drupal 8 alpha12 to be parsed again with the new code. The result is the number of strings made available for translation jumped from 6820 to 7769, making available almost a thousand previously hidden strings. (Also almost 800 new files are considered now for source strings, jumping from 3972 to 4722). For comparison, Drupal 7's latest release only contains 4645 strings to translate. Our advice from last June that this may not be the time to jump on translating it all yet still stands though.

The quest is not over. API changes that affect translatability are still made. The latest one is the logger API that replaces watchdog(). We still need to igure out how to support that in string extraction. Help needed there! I'm not sure how the string extraction based method can sustain itself for Drupal 9, we'll need to take a hard look at this definitely. We are doing out best now in Drupal 8 to cover what is possible.

The largest outstanding item keeps being support for shipped configuration translatables. All the default user roles, filters, views, content types, menus and so on that Drupal 8 itself supports to be translated with sources from localize.drupal.org, so only the server side part on our side is missing still. There are probably hundreds of translatable strings hidden there still.

That said, it is not only the Drupal 8 API support that is a bit lacking, we need more volunteers to help with the site itself. The site's biggest contributor Sebastien Corbin posted about the state of the site in January and that is still pretty accurate. I submitted a Core conversation proposal for DrupalCon Amsterdam to at least start assembling a working group around the site with people who can devote time in a sustainable fashion. We all rely on this site for so much and it gets so little love!

read more

Localize.drupal.org: 1000 new translatable strings for Drupal 8 and the future of localize.drupal.org

Feeds from Drupal.org - Fri, 2014-06-13 13:24

As we kept following the changes made to Drupal 8 and the dozens of new ways of adding translatable strings to code in the new version, we worked on support for TWIG translation constructs and all kinds of YAML file sources (routing titles, menu items, action links, local tasks, configuration schemas, etc) recently as well as some misc new APIs like TranslationWrapper objects. Huge thanks to the amazing work of @ksenzee, @herom and @hron84 building string extraction support for these in our not very well loved issue queue.

Support for these APIs is now rolled out live on localize.drupal.org and I sent Drupal 8 alpha12 to be parsed again with the new code. The result is the number of strings made available for translation jumped from 6820 to 7769, making available almost a thousand previously hidden strings. (Also almost 800 new files are considered now for source strings, jumping from 3972 to 4722). For comparison, Drupal 7's latest release only contains 4645 strings to translate. Our advice from last June that this may not be the time to jump on translating it all yet still stands though.

The quest is not over. API changes that affect translatability are still made. The latest one is the logger API that replaces watchdog(). We still need to igure out how to support that in string extraction. Help needed there! I'm not sure how the string extraction based method can sustain itself for Drupal 9, we'll need to take a hard look at this definitely. We are doing out best now in Drupal 8 to cover what is possible.

The largest outstanding item keeps being support for shipped configuration translatables. All the default user roles, filters, views, content types, menus and so on that Drupal 8 itself supports to be translated with sources from localize.drupal.org, so only the server side part on our side is missing still. There are probably hundreds of translatable strings hidden there still.

That said, it is not only the Drupal 8 API support that is a bit lacking, we need more volunteers to help with the site itself. The site's biggest contributor Sebastien Corbin posted about the state of the site in January and that is still pretty accurate. I submitted a Core conversation proposal for DrupalCon Amsterdam to at least start assembling a working group around the site with people who can devote time in a sustainable fashion. We all rely on this site for so much and it gets so little love!

read more

Categories: Straight From Drupal

groups.drupal.org frontpage posts: All the sprints at and around DrupalCon Amsterdam

Planet Drupal - Fri, 2014-06-13 12:19
Start:  2014-09-27 09:00 - 2014-10-05 19:00 Europe/Amsterdam Sprint

We have a great tradition of extended sprints around big Drupal events including DrupalCons and Drupal Dev Days. While there is a sprint day included in DrupalCons (usually) on Friday, given that a lot of the Drupal core and contrib developers fly in for these events, it makes a lot of sense to use this opportunity to start sooner and/or extend our stay and work together in one space on the harder problems.

DrupalCon Amsterdam is next up! DrupalCon and the Drupal Association continue to recognize the need for extended sprints as part of the schedule and are providing space on Monday, and helping organize space for the weekends before and after also! We are still looking for additional sponsors for the weekend sprints before/after to help with space, internet, coffee, tea and maybe food. There are already various sprints signed up including Multilingual, Drupal.org and Frontend. We are really friendly and need all kinds of expertise!

Now is the time to consider if you can be available and book your travel and hotel accordingly!

Join the sprinters, signup now! Practical details
Dates
Sept 27 to Oct 5 (all week at DrupalCon and weekends both before and after).
Times
We start each day at 9am and plan to have space booked until midnight.
Locations
To be booked.
Sponsors Lead sponsor:

Drupal Association @DrupalAssoc

Looking for sponsors

We are looking for more sponsors to be able to pay for extra expenses. If you are interested sponsoring or if you need sponsors to cover expenses, please contact me at https://drupal.org/user/4166/contact

#node-427578 .picture, #node-427578 h3 { display: none; } #node-427578 .field-type-datestamp { margin: 0 0 2em 0; } #node-427578 dl { margin-bottom: 1em; } #node-427578 dd { margin-top: 0.5em; } #node-427578 h3.content { display: block; }

groups.drupal.org frontpage posts: All the sprints at and around DrupalCon Amsterdam

Feeds from Drupal.org - Fri, 2014-06-13 12:19
Start:  2014-09-27 09:00 - 2014-10-05 19:00 Europe/Amsterdam Sprint

We have a great tradition of extended sprints around big Drupal events including DrupalCons and Drupal Dev Days. While there is a sprint day included in DrupalCons (usually) on Friday, given that a lot of the Drupal core and contrib developers fly in for these events, it makes a lot of sense to use this opportunity to start sooner and/or extend our stay and work together in one space on the harder problems.

DrupalCon Amsterdam is next up! DrupalCon and the Drupal Association continue to recognize the need for extended sprints as part of the schedule and are providing space on Monday, and helping organize space for the weekends before and after also! We are still looking for additional sponsors for the weekend sprints before/after to help with space, internet, coffee, tea and maybe food. There are already various sprints signed up including Multilingual, Drupal.org and Frontend. We are really friendly and need all kinds of expertise!

Now is the time to consider if you can be available and book your travel and hotel accordingly!

Join the sprinters, signup now! Practical details
Dates
Sept 27 to Oct 5 (all week at DrupalCon and weekends both before and after).
Times
We start each day at 9am and plan to have space booked until midnight.
Locations
To be booked.
Sponsors Lead sponsor:

Drupal Association @DrupalAssoc

Looking for sponsors

We are looking for more sponsors to be able to pay for extra expenses. If you are interested sponsoring or if you need sponsors to cover expenses, please contact me at https://drupal.org/user/4166/contact

#node-427578 .picture, #node-427578 h3 { display: none; } #node-427578 .field-type-datestamp { margin: 0 0 2em 0; } #node-427578 dl { margin-bottom: 1em; } #node-427578 dd { margin-top: 0.5em; } #node-427578 h3.content { display: block; }
Categories: Straight From Drupal

FacetAPI URL Validator

Latest Drupal Modules - Fri, 2014-06-13 11:53

This is a cheeky little module that attempts to insert some validation of URL parameters into Facet API, so that if someone pops something random into the URL it doesn't get sent to the search backend for it to choke there.

For example, it's possible to send strings to filter integer fields.

This probably isn't the best implementation of this stuff, but it works!

Categories: Straight From Drupal

Code Karate: Drupal 7 Calendar Module

Planet Drupal - Fri, 2014-06-13 11:25
Drupal 7 Calendar Module - Daily Dose of Drupal Episode 155

The Drupal 7 Calendar Module makes it easy to build event calendars in Drupal. It makes use of the Views module to make it all happen.

In this episode you will learn:

Code Karate: Drupal 7 Calendar Module

Feeds from Drupal.org - Fri, 2014-06-13 11:25
Drupal 7 Calendar Module - Daily Dose of Drupal Episode 155

The Drupal 7 Calendar Module makes it easy to build event calendars in Drupal. It makes use of the Views module to make it all happen.

In this episode you will learn:

Categories: Straight From Drupal

CTI Digital: DrupalCon Austin

Planet Drupal - Fri, 2014-06-13 11:07

CTI Digital’s Head of Drupal, Paul Johnson has just returned from an intense week at DrupalCon Austin, USA.

Drone Group Photo DrupalCon Austin 2014

It's fair to say DrupalCon Austin was always going to be special for CTI Digital from the outset. Appointed DrupalCon 2014 design partners our team have enjoyed contributing to the overall success of the conference. CTI’s Creative Director, Rik Hopkinson designed the complete conference concept and branding encomassing signage, brochures, guides, stickers, web design, right the way through to the stage design below.

The pre-keynote "Calling all Drupal Super Heros" saw Dries wrapped in a million critical tissues and all 3300 attendees performing the ridiculous Gity Pokey. It was no surprise to see Robert Douglass seizing the opportunity to don a nurses outfit complete with plaits and beard!

On a more serious note the DriesNote was a refreshing departure from the typicial state of Drupal presentation. During his keynote Dries Buytaert illustrated in how photography in the early days was a complex time consuming process with many steps. With innovation came 35mm film, then Polaroid and lately digital cameras. With each generation photography became more streamlined.

Looking at the way the web is evolving he sees a digital convergence and the development of what he coined the "Experience Web". He challenged the audience to consider what Drupal's future role would be and provided some predictions. Watch the Keynote here

Erynn Petersen's keynote approached the issues of diversity and inclusivity in open source and business. Saying "An Open Source Project is as Healthy and Vibrant as its community"  she celebrated the Drupal community as trailblazing the campaign to ensure a well rounded community. Indeed DrupalCon Austin had 20% female attendees which represents a substaintial and consistent uplift. 

As a highly active member of the global community Paul contributed to the global Drupal Community Summit. A rare opportunity to meet many of the leaders we communicate with on a regular basis, the day event allowed thought leaders to share their epic wins and fails so others could learn and improve their local Drupal community, DrupalCamps, solve issues with Drupal.org and general sprint on the human side of Drupal.

CTI Digital commisioned Tom Oakley from Ten Integrated Marketing to design a cartoon/superhero style mask of Drupal creator Dries Buytaert. We encouraged people to tweet themselves wearing the mask to #WheresDries with a chance of winning a Makey Makey.

Before Paul left for DrupalCon he contacted Drupalist around the globe and invited them to join in, in a small way bringing the spirit of DrupalCon to where they lived. We should never lose sight that some people are not able to attend. It was amazing to see what contrasting lives people using Drupal lead. 

Hendrik Martens travelled to Johanesburg to find a special location for his #WheresDries photo.

Timo Teller was the first lucky winner of a Makey Makey which we knew his kids would enjoy!

As DrupalCon social media lead Paul met with the Drupal Latino team who are planning DrupalCon Bogotá. It looks like we are in for quite a party! Follow @DrupalConLatino for news.

During the conference Cathy Theys made Paul aware that the crowdfunding initiative to develop Rules for Drupal 8 was not likely to reach it's funding deadline in just 7 days. As one of the first corporate sponsors of #D8Rules we are pleased to announce after a sustained social media campaign the $15,000 funding goal was smashed. Further phases of funding will follow. You can find out about Drupal8Rules here.

So after the DrupalCon volunteers dinner Paul's work was over and our thoughts are already onto DrupalCon Amsterdam where we again are developing the entrire branding, design and build of the conference marketing collateral and website. We thoroughly enjoyed contributing to helping DrupalCon "Keep Austin Weird" and we hope to meet you in Amsterdam where CTI Digital will be present in much larger numbers! 

Austin Group Photo: Michael Schmidt

 

 

CTI Digital: DrupalCon Austin

Feeds from Drupal.org - Fri, 2014-06-13 11:07

CTI Digital’s Head of Drupal, Paul Johnson has just returned from an intense week at DrupalCon Austin, USA.

Drone Group Photo DrupalCon Austin 2014

It's fair to say DrupalCon Austin was always going to be special for CTI Digital from the outset. Appointed DrupalCon 2014 design partners our team have enjoyed contributing to the overall success of the conference. CTI’s Creative Director, Rik Hopkinson designed the complete conference concept and branding encomassing signage, brochures, guides, stickers, web design, right the way through to the stage design below.

The pre-keynote "Calling all Drupal Super Heros" saw Dries wrapped in a million critical tissues and all 3300 attendees performing the ridiculous Gity Pokey. It was no surprise to see Robert Douglass seizing the opportunity to don a nurses outfit complete with plaits and beard!

On a more serious note the DriesNote was a refreshing departure from the typicial state of Drupal presentation. During his keynote Dries Buytaert illustrated in how photography in the early days was a complex time consuming process with many steps. With innovation came 35mm film, then Polaroid and lately digital cameras. With each generation photography became more streamlined.

Looking at the way the web is evolving he sees a digital convergence and the development of what he coined the "Experience Web". He challenged the audience to consider what Drupal's future role would be and provided some predictions. Watch the Keynote here

Erynn Petersen's keynote approached the issues of diversity and inclusivity in open source and business. Saying "An Open Source Project is as Healthy and Vibrant as its community"  she celebrated the Drupal community as trailblazing the campaign to ensure a well rounded community. Indeed DrupalCon Austin had 20% female attendees which represents a substaintial and consistent uplift. 

As a highly active member of the global community Paul contributed to the global Drupal Community Summit. A rare opportunity to meet many of the leaders we communicate with on a regular basis, the day event allowed thought leaders to share their epic wins and fails so others could learn and improve their local Drupal community, DrupalCamps, solve issues with Drupal.org and general sprint on the human side of Drupal.

CTI Digital commisioned Tom Oakley from Ten Integrated Marketing to design a cartoon/superhero style mask of Drupal creator Dries Buytaert. We encouraged people to tweet themselves wearing the mask to #WheresDries with a chance of winning a Makey Makey.

Before Paul left for DrupalCon he contacted Drupalist around the globe and invited them to join in, in a small way bringing the spirit of DrupalCon to where they lived. We should never lose sight that some people are not able to attend. It was amazing to see what contrasting lives people using Drupal lead. 

Hendrik Martens travelled to Johanesburg to find a special location for his #WheresDries photo.

Timo Teller was the first lucky winner of a Makey Makey which we knew his kids would enjoy!

As DrupalCon social media lead Paul met with the Drupal Latino team who are planning DrupalCon Bogotá. It looks like we are in for quite a party! Follow @DrupalConLatino for news.

During the conference Cathy Theys made Paul aware that the crowdfunding initiative to develop Rules for Drupal 8 was not likely to reach it's funding deadline in just 7 days. As one of the first corporate sponsors of #D8Rules we are pleased to announce after a sustained social media campaign the $15,000 funding goal was smashed. Further phases of funding will follow. You can find out about Drupal8Rules here.

So after the DrupalCon volunteers dinner Paul's work was over and our thoughts are already onto DrupalCon Amsterdam where we again are developing the entrire branding, design and build of the conference marketing collateral and website. We thoroughly enjoyed contributing to helping DrupalCon "Keep Austin Weird" and we hope to meet you in Amsterdam where CTI Digital will be present in much larger numbers! 

Austin Group Photo: Michael Schmidt

 

 

Categories: Straight From Drupal

IP Language Negotiation

Latest Drupal Modules - Fri, 2014-06-13 10:13

This modules uses the ip2country module for country detection. It's add a Language Detection option at admin/config/regional/language/configure which can be used to redirect the user to the language of his country.

It's usage is quite basic now. It works only for countries where the language code is the same as the country code (eg: NL, FR, PL, etc).

Categories: Straight From Drupal

Morten.dk: Language, Twitter, Misunderstanding & Drupal Community

Planet Drupal - Fri, 2014-06-13 09:30

At Drupalcon in Austin I took on the mechanical bull. I ended up losing miserably. Not surprisingly, it was recorded and sent out to the world. Because of my epic fail on the bull, one of my friends in Sweden (I’m Danish) afterwards called me out on Twitter with the #drupalcon hashtag and called me a “pussy".

read more

Pages

Subscribe to My Drupal aggregator