Planet Drupal

Subscribe to flux Planet Drupal - aggregated feeds in category Planet Drupal
Mis à jour : il y a 36 min 32 sec Use of Drupal in Product Companies

lun, 30/05/2016 - 02:00
Catégories: Elsewhere How To Force Search API To Reindex a Node / an Entity

sam, 28/05/2016 - 10:46

By default Search API (Drupal 7) reindexes a node when the node gets updated. But what if you want to reindex a node / an entity on demand or via some other hook i.e. outside of update cycle? Turned out it is a quite simple exercise. You just need to ...

Read now

Catégories: Elsewhere Adding a custom extra field to entity / node display

sam, 28/05/2016 - 10:46

I had a case recently, where I needed to add custom data to the node display and wanted this data to behave like a field, however the data itself didn't belong to a field. By "behaving like a field" I mean you can that field at node display settings and ...

Read now

Catégories: Elsewhere

Dries Buytaert: Changes with the Drupal Association

sam, 28/05/2016 - 02:17

The Drupal community is very special because of its culture of adapting to change, determination and passion, but also its fun and friendship. It is a combination that is hard to come by, even in the Open Source world. Our culture enabled us to work through really long, but ground-breaking release cycles, which also prompted us to celebrate the release of Drupal 8 with 240 parties around the world.

Throughout Drupal's 15 years history, that culture has served us really well. As the larger industry around us continues to change -- see my DrupalCon New Orleans keynote for recent examples -- we have been able to evolve Drupal accordingly. Drupal has not only survived massive changes in our industry; it has also helped drive them. Very few open source projects are 15 years old and continue to gain momentum.

Drupal 8 is creating new kinds of opportunities for Drupal. For example, who could have imagined that Lufthansa would be using Drupal 8 to build its next-generation in-flight entertainment system? Drupal 8 changes the kind of end-user experiences people can build, how we think about Drupal, and what kind of people we'll attract to our community. I firmly believe that these changes are positive for Drupal, increase Drupal's impact on the world, and grow the opportunity for our commercial ecosystem.

To seize the big opportunity ahead of us and to adjust to the changing environment, it was the Drupal Association's turn to adapt and carefully realign the Drupal Association's strategic focus.

The last couple of years the Drupal Association invested heavily in to support the development and the release of Drupal 8. Now Drupal 8 is released, the Drupal Association's Board of Directors made the strategic decision to shift some focus from the "contribution journey" to the "evaluator's adoption journey" -- without compromising our ability to build and maintain the Drupal software. The Drupal Association will reduce its efforts on's collaboration tools and expand its efforts to grow Drupal's adoption and to build a larger ecosystem of technology partners.

We believe this is not only the right strategic focus at this point in Drupal 8's lifecycle, but also a necessary decision. While the Drupal Association's revenues continued to grow at a healthy pace, we invested heavily, and exhausted our available reserves supporting the Drupal 8 release. As a result, we have to right-size the organization, balance our income with our expenses, and focus on rebuilding our reserves.

In a blog post today, we provide more details on why we made these decisions and how we will continue to build a healthy long-term organization. The changes we made today help ensure that Drupal will gain momentum for decades to come. We could not make this community what it is without the participation of each and every one of you. Thanks for your support!

Catégories: Elsewhere

Drupal Association News: Reorganizing for a changing Drupal

sam, 28/05/2016 - 00:00
Serving Drupal’s opportunity

The release of Drupal 8 creates many opportunities for organizations worldwide to build something amazing for complex web solutions, mobile, SaaS, the Internet of Things, and so much more. The Drupal Association is excited to work with the community to create these opportunities.

In our mission to support the Drupal Project, the Association unites our global open source community to build and promote Drupal. We do this primarily by using our two main resources:, the center of our community’s interactions, with 2 million unique visitors a month; and DrupalCon, which hosts over 6,000 attendees a year and provides the critical in-person acceleration of ideas.

Both foster the contribution journey that makes amazing software, and the evaluator’s adoption journey that encourages people to use Drupal across industries to create amazing things. As I mentioned in my recent blog post, achieving our mission helps the community thrive into the future and realize their Drupal dream.

With the release of Drupal 8, we have an opportunity to reflect on how the Association leverages these assets to work for Drupal’s current and future opportunities. Working with our board of directors, we determined that the Association needs to:

  • Re-assess the Project’s needs, and find new ways to support and meet those needs
  • Address a structural issue, to be a more sustainable organization

To do this, the Drupal Association board and I made hard choices. Having invested heavily in supporting the Drupal 8 release and exhausting available reserves, we recognize that the Association now must right-size the organization and balance our income with our expenses. The biggest impact is the elimination of seven positions, reducing our staff size from 25 to 17 employees. Also as part of this reduction, we have reorganized staff to better address the Project’s needs now that Drupal 8 is released.

While we do have our eye on a bright future for the Project through these changes, we’re also painfully aware that we’re not just eliminating positions. We’re saying goodbye to seven people who are important to us—whose contributions we value more than we can describe. We’re impacting the lives of people we care about—people who’ve given a lot to the Project and to others in our community.

Making the Drupal Association sustainable

In early 2014, the Association began investing reserves in building an engineering team for two main reasons: to address critical issues that were slowing down the production of Drupal 8, and to modernize In doing so, we purposefully created a structural deficit, with the hopes that we could grow revenue to meet the cost of this investment before we drew down our reserves.

Because of this investment, we were able to accelerate the release of Drupal 8 through a roadmap of features like semantic versioning, DrupalCI (continuous integration testing for the projects we host), better search and discovery capabilities, numerous issue queue improvements, and issue credits, all of which positively impacted the release of Drupal 8. In addition, the engineering team has addressed years of technical debt and incorporated more modern services in the site that have made it more reliable and faster around the world.

While revenue grew from 2014 to 2015 by 14%, it didn't grow enough. Last year, we acknowledged that we did not meet the revenue goals that would sustain this investment. We addressed it with a retrenchment designed to extend our runway and see if we could increase revenue sufficiently. All told, while we have accomplished both revenue diversification and growth, it wasn’t enough to fully replace the investment. Then in spring 2016, several things happened on the revenue front that created a significant budget gap:

  • Sponsored work: The Association funded Engineering resources by accepting sponsored work to build Composer endpoints for Drupal projects. After that project was completed, we were unable to line up an additional sponsored project to continue underwriting the Engineering team.
  • The Connect Program: This new experimental program designed to connect software companies with service providers for partnership and integration opportunities did not meet its revenue goals.
  • DrupalCon: DrupalCon New Orleans ticket sales did not reflect the increase we were expecting this year, and we have revised our DrupalCon Dublin ticket sales projections accordingly.

"CAGR" means compound annual growth rate.
2016 data is projected revenue and expenses.

Addressing this structural deficit required a reduction of both labor and non-labor expense. Labor is our biggest cost, and we can’t create alignment without cutting roles at the Association. Holly Ross, our Executive Director, Josh Mitchell, CTO, and Matthew Tsugawa, CFO, offered to step down and contribute their salaries to the reduction, as they saw that a smaller organization doesn’t require a full leadership team. Additionally, we are losing three staff members from the Engineering team, one from the Events team, and one from the MarComm team. We are working with these staff members to help them through their transition.

Our second biggest expense is rent. We are working to eliminate the physical office in Portland, Oregon—moving staff to a virtual, distributed team—but those efforts will likely not introduce savings until 2017. We already work with distributed staff and community members around the world, so we have the know-how and tools like Slack and Zoom in place to support this change when it happens.

While these staff reductions are painful today, they correct the structural problem, bringing expenses in line with income. We have conservatively reforecasted revenue to reflect any impact this staffing reduction may have. We can see with our forecasts that the layoffs result in the Association being on healthy financial ground in 2017.

What happens next?

Leading up to now, we invested in tooling to help the community release Drupal 8. Now that Drupal 8 has shipped, the Project has new needs, which are:

  • Promote Drupal 8 to grow adoption
  • Sustain so the community can continue to build and release software is our strongest channel for promoting Drupal, given that it’s the heart of the community and organically attracts hundreds of thousands of technical decision makers. It provides the biggest opportunity to guide evaluators through an adoption journey and amplify Drupal’s strength in creating new business opportunities through solutions like “DevOps and Drupal” or “Drupal for Higher Education.” These new services on will help evaluators, create value for our partners, and increase revenue for the Drupal Association.

We can also use to better promote DrupalCon. It’ll help grow ticket sales and attract more community members to that special week of in-person interaction, accelerating their adoption and contribution journeys.

Additionally, we’ll expand our efforts to attract more evaluators to DrupalCon. We can accelerate their adoption journey through peer networking and programming that helps them understand how Drupal is the right solution for their organization. We do this today with our vertical-specific Summits (like the Higher Education Summit) and we can do more through relevant sessions and other special programming. And while the Drupal evaluators are there, we’ll connect them with Drupal agencies who can help them realize their Drupal vision.

One thing about our work won’t change: our commitment to the tools you use to build Drupal every day. Though the Engineering team is smaller after today, they will make sure the tools and services you need to build and release the software are supported. That includes things like the issue queues, testing, security updates, and packaging.

Right now, we’re focused on the team as we go through this transition. Once the transition is complete, we’ll be looking at the Project needs and making sure we align our work accordingly. When we make changes, we’ll be sure to keep the community updated so you know what our primary focus is and how we are working towards our vision of Drupal 8 adoption across many sectors.

In the meantime, I invite you to tell me your thoughts on this new focus and how the Drupal Association can best help you.

Catégories: Elsewhere

DrupalEasy: We're getting workshoppy

ven, 27/05/2016 - 23:48

We’ve really been busy here at DrupalEasy updating our curriculum and adding some training programs that we think will help get people leveraging the new awesomeness of Drupal 8. After a few times out at Drupal events, and our upcoming gig at Drupal North in Montreal with Introduction to Drupal 8 Module Development on June 15, we’ve decided to go broader. We’re going new school, with online sessions of these D8 workshops in June to extend the reach beyond camps and 'cons.  

If you are looking to get up to speed with Drupal 8 module development and/or theme development, two online afternoon sessions live, at your desktop are coming up:

Introduction to Drupal 8 Module Development

  • 2 Afternoons, Live, Online
  • Monday & Tuesday June 13 & 14;
  • 3:00 pm - 7:00 pm EDT each day
  • Early Bird: $199. After June 6; $249
  • Register now

The Introduction to Drupal 8 Module Development workshop is designed for anyone with either knowledge of PHP or knowledge of Drupal 7 module development. The workshop takes users through the development of three custom modules demonstrating the basic principles and concepts of Drupal 8 module development. Students will be hands-on for the majority of the day, and will leave with confidence to start writing their own custom Drupal 8 modules.

Introduction to Drupal 8 Theme Development

  • 3 Afternoons, Live, Online
  • Monday, Tuesday & Wednesday June 20 - 23
  • 3:00 pm - 7:00 pm EDT each day
  • Early Bird: $199. After June 13; $249
  • Register now

The Introduction to Drupal 8 Theme Development workshop is our newest curriculum and it's super-sized! Through three half-days of training, you will learn about Drupal 8 core's new built-in base themes, Twig templates, theme anatomy, and a full-on front-end development toolchain that utilizes Node.js and Gulp. The workshop uses the Bootstrap base theme for two of its three main units, giving students plenty of hands-on time developing custom themes. Anyone with knowledge of Drupal 7 theming or a working knowledge of HTML and CSS will leave the workshop with skills to allow them to start theming Drupal 8 sites.

Catégories: Elsewhere

Jeff Geerling's Blog: Ensuring Drush commands run properly using Drush 8.x via Acquia Cloud Hooks

ven, 27/05/2016 - 22:56

Any time there are major new versions of software, some of the tooling surrounding the software requires tweaks before everything works like it used to, or as it's documented. Since Drupal 8 and Drush 8 are both relatively young, I expect some growing pains here and there.

One problem I ran into lately was quite a head-scratcher: On Acquia Cloud, I had a cloud hook set up that was supposed to do the following after code deployments:

# Build a Drush alias (e.g. [subscription].[environment]).

# Run database updates.
drush @${drush_alias} updb -y

# Import configuration from code.
drush @${drush_alias} cim vcs

This code (well, with fra -y instead of cim) works fine for some Drupal 7 sites I work on in Acquia Cloud, but it seems that database updates were detected but never run, and configuration changes were detected but never made... it took a little time to see what was happening, but I eventually figured it out.

The tl;dr fix?

Catégories: Elsewhere

NEWMEDIA: Build robust forms in Drupal 8

ven, 27/05/2016 - 20:00
Build robust forms in Drupal 8 Over the last few Drupal releases, the Webform module has been the standard for creating robust forms and surveys. While this venerable module has served the community’s needs quite well, major releases of Drupal often afford the opportunity to take a fresh look at how common problems are solved, leveraging new technologies and concepts introduced in the release. Tanner J. Ferguson Fri, 05/27/2016 - 18:00 Baked into Core

Since Drupal 4.6, Drupal Core has shipped with a basic contact form module that had limited functionality. Finally, the contact module got some much-needed attention in Drupal 8. Contact forms are now fieldable entities, allowing us to build forms with the same fields we build content types, taxonomies, and other entities with.

Building Out the Form

Forms are created and managed by navigating to Structure->Contact Forms in the Admin menu. From here, choose “Add contact form.”


This takes us to a form for setting the name of the form, email addresses for submissions to be sent to, and optionally an auto-reply message to the submitter. Once saved, we are taken back to the Contact Forms admin page. 

This gives us a basic form with Sender Name and Email, a Subject field, and a basic text area for a Message. To add fields to our new form, we need to select the “Manage Fields” option in the Operations dropdown. From here, we can add any of the field types available on the site.

Form Display

To customize how the form is displayed, we want to select the “Manage Form Display” option in the Operations dropdown. This will allow us to change the order of the fields for the form, change configurations for each field, and allow us to disable any fields that are provided by default that we don’t want to use.

Manage Display

Similar to Form Display, if we want to change the order and display of fields in the submission emails, using the “Manage Display” option will allow us reorder or hide fields from showing in the submission email.

Submission Storage and Export

Everything we’ve covered so far is great if we want to build out a form and start getting submissions by email. However, if we want to save and view submissions in the site or want to export the submissions in bulk, we need to look to some contributed modules to fill in the gaps.

Contact Storage Module

As its name implies, the Contact Storage module addresses the need for a central location from which content editors can review and manage form submissions on the site. The module also provides Views integration as well as some additional customization options for our forms. The default configuration provides these features for us, so we can install the module and start benefitting from it immediately.

Submission Exports

We now have robust forms and a place to centrally store their submissions, with Views giving us the ability to build out lists of submissions. What we’re still missing at this point is a way to download the submissions in bulk, and it’s fairly common to want such an export in a format like CSV that can be loaded into a spreadsheet application. To achieve that, we can put our Views integration to use, along with Drupal 8’s REST Module, and the CSV Serialization module. 

Once these modules are installed, create a new view of Contact Messages and check the “Create a REST Export” option, providing the path we will navigate to trigger the export. Then hit Save and Edit to continue configuring the view.

In the format section of the view configuration page, we see the format is set to “Serializer”. Here, we want to configure the settings for Serializer, and select the “csv” format.

At this point we have a working view that will export all submissions as a CSV. We can leave the view set to show content as “Entity,” which will export all fields for the submission, or we can switch the display to “Fields,” which will allow us to specify the fields we want in the export, and how they are formatted.

With exports now provided by Views, we can create custom exports for specific forms, or we can utilize Exposed Filters and Contextual Filters to provide an export that works for all forms, allowing users to choose how they want the export filtered.

More Form Solutions in Contrib

If we need to provide robust survey forms now, the approach covered here is currently the most stable and ready to implement. If this solution doesn’t meet your use case, it might be worth taking a look at eForm, the Drupal 8 version of the Entityform module introduced in Drupal 7. There is also still some discussion of a Drupal 8 port of the Webform module, so it’s possible with enough interest we could have a few different solutions for providing front-facing forms to end users.

While building forms will be a bit different in Drupal 8 compared to previous versions, the experience is more in line with what we’ve come to expect from building Content Types and other fieldable entities. This provides the opportunity for more flexibility and functionality when building front-facing forms, and the Views integration provides the opportunity to present and export the submitted form data just the way we need.

Catégories: Elsewhere Pune Drupal Meetup, May 2016

ven, 27/05/2016 - 17:42
Pune Drupal Meetup, May 2016 Body

The flavour of this month has been the Drupalcon New Orleans and we decided to keep the momentum going for this PDG meet-up held at the QED42 office.

The first session was given by Rakhi Mandhania on her experience at DrupalCon both as an attendee as well as a Keynote speaker for the Higher Ed Summit. She explained how everyone is concerned with the migration of a large number of websites to Drupal 8 and the lack of rich Drupal talent. DrupalCAP initiative was hailed as a solution to the jarring lack of Drupal literate work force and appreciated all around. 

The second session was by Piyuesh Kumar on service workers, the same session both he and Saket kumar presented at New Orleans. He explained that functionalities such as, rich offline experiences, periodic background syncs, push notifications that traditionally require a native application are coming to the web and service workers provides the technical foundation all these features will rely on.

He ended the session with a demo of a working website for DrupalCamp.


The evening was concluded with us deciding the dates for DrupalCamp Pune 2016, which will tentatively take place sometime in late August.

Watch this space for details, coming shortly!
Good day and see you all soon.


aurelia.bhoy Fri, 05/27/2016 - 21:12
Catégories: Elsewhere

Third & Grove: The One and Only entity_metadata_wrapper!

ven, 27/05/2016 - 16:00
The One and Only entity_metadata_wrapper! miro Fri, 05/27/2016 - 10:00
Catégories: Elsewhere

Mediacurrent: Friday 5: 5 Tips for Improving Your Site's SEO

ven, 27/05/2016 - 15:22

We made it to the finish line of another busy work week!

Thanks for joining us for Episode 9 of The Mediacurrent Friday 5. This week, Community Lead Damien McKenna discusses 5 Tips for Improving Your Site's SEO with the one and only Mark Casias.

Catégories: Elsewhere

Valuebound: Drupal 8 Commerce is on the Way! DrupalCon New Orleans 2016.

ven, 27/05/2016 - 13:13

A lot of thanks to the commerce guys for contributing the Drupal commerce module to Drupal community, which took drupal to a different level in the CMS world. Its very exciting, Commerce 2.x which is the Drupal 8 version of drupal commerce. As like any other drupal developer / architect, I am also excited about Commerce 2.x

Thank God, I was one of the fortunate ones to attend the Commerce Guys session on DrupalCon New Orleans 2016, the very first session after the release of ‘8.x-2.0-alpha4’  version of drupal commerce. It was an amazing session, which made a lot of things clearer,a lot of unanswered questions were answered…

Catégories: Elsewhere

Pronovix: Brightcove Video Connect for Drupal 8 - Part 3: Video & Playlist Management

ven, 27/05/2016 - 11:23

Part 3 of this 4-part blog series illustrates the management of Videos & Playlists and discuss some of the changes compared to the Drupal 7 version of the module - especially the new video listing interface (with a similar layout to Brightcove’s own Studio interface) and autocompleting tags feature.

Catégories: Elsewhere

OpenLucius: 12 Cool Drupal modules for site builders | May 2016

ven, 27/05/2016 - 11:22

Without further ado, here is what struck me about Drupal modules in the past month:

1. Hide submit button
Catégories: Elsewhere

Chapter Three: Scripting Drupal Development With Drush

ven, 27/05/2016 - 06:50

Whether you work on one Drupal site or multiple, it is often necessary for your local dev environment to be slightly different from your site's server.  Perhaps you need to disable Secure Pages because you don't want to set up SSL on your local environment, or there are modules specific to your website's server config.  If you work on multiple sites in a sporadic fashion its possible you need to synchronize your local database with the dev server between tasks, that way you aren't missing any updated configurations.

Sure, you can pull this off manually by grabbing the database, reloading your local, and updating your Drupal site's config; but why not add a little automation to help out?

Catégories: Elsewhere

Four Kitchens: What’s on the Horizon for Drupal?

jeu, 26/05/2016 - 18:00

The Drupal community is self-reflective enough to see the flaws in the project and brave enough to reinvent itself. …

Catégories: Elsewhere

Acquia Developer Center Blog: Acquia U, before and after - meet Ally Gonthier

jeu, 26/05/2016 - 17:56

I sat down with Ally Gonthier the first time I visited Acquia's then-new downtown Boston headquarters in mid-2015. At the time, she was preparing to leave her job as Support Coordinator at Acquia to enter Acquia's Drupal/tech bootcamp, known as Acquia U. When I returned to Boston in the spring of 2016, I took the chance to talk with her again about her experiences at Acquia U and what had become of her in the meantime. Below is a transcript of our before and after conversations.

Before and after on video

More with Ally
Before Acquia U: Mid 2015

jam: Hey. We are at Acquia’s brand-spanking-new headquarters. It’s been barely any time. This is only my third day here ever and we’re in downtown Boston, and it’s kind of exciting. I am with a current and future colleague, right? Why don’t you introduce yourself and tell us something about you.

Ally Gonthier: Something?

jam: Yes, whatever you like. Maybe something non-Drupaly.

Ally Gonthier: Okay. My name is Ally. My last name is pronounced differently depending on where you are in the world. In America, it’s Gonthier [read in American accent]. In France, it’s Gonthier [read in beautiful French accent], which is way better.

jam: Way better, okay. So I’m with Ally Gonthier. What’s your job at Acquia right now?

Ally Gonthier: I am a senior customer support coordinator, which is sort of a complicated-ish but not really.

jam: Interestingly, you’re about to be a "Ubie". So you’re changing from this job and going into Acquia’s Drupal training program.

Ally Gonthier: Yes.

jam: Why are you doing that?

Ally Gonthier: So I’m in support right now and it’s a very entry level position. There’s a lot to do, a lot of tasks to be done. To get me to the next level, I need to learn a lot more about Drupal and as intensely as I can, so ...

jam: And you’re excited about Drupal and you want ... ?

Ally Gonthier: Yes.

jam: You’re all about the Drupal now?

Ally Gonthier: That’s why I’m here.

jam: Okay. So this sounds kind of silly in context, but how did you hear about the Acquia U program?

Ally Gonthier: I literally met Amy who’s running the program at a Drupal camp last September and I bumped into her. We worked together but I didn’t even know who she was and we – she introduced herself to me and I was like fly paper. I didn’t leave her alone.

jam: Wow! Okay, okay. And had you heard of Drupal before you came to Acquia?

Ally Gonthier: Yes, yes. So I have been ... a “Supportian” for a while now. I had other jobs in life but when I went into sort of a technical land I found support really fit my personality well because not only do I enjoy learning and doing technical things, but I’m also really empathetic for customers. I really want to help people, and help them understand and ... I’m not necessarily a people person but I care if that makes sense, you know?

jam: No, it does. I think support, it’s actually such a great fit for people steeped in the open source mentality because you really do help people succeed and it’s all about transparency and sharing, right? And then I’ve also been told by other people from Acquia support that the difference between working in a support role and working in some company building website ...

Ally Gonthier: Like a help desk, right?

jam: Right. Well, you get to look at a different code base every day.

Ally Gonthier: Yes, absolutely.

jam: You’re not just working on the one thing for ...

Ally Gonthier: It’s every day is different. Every customer is different. It’s a different challenge every day. It’s great for somebody who doesn’t want to do the same thing all day every day.

jam: What’s your first Drupal memory?

Ally Gonthier: My first Drupal memory? Interesting. Well, honestly, I mean I learned about Acquia, obviously, because of Drupal but I was just looking into web design maybe five/six years ago. I just was comparing all the big CMSs or whatever was available at that time and I was like, “What is the best? And what is the hardest? And, okay, Drupal it is.” Then, I just started – I literally bought a book and I went front to back.

jam: What made you stick with it then?

Ally Gonthier: Honestly, I learned about – I figured I – I saw Acquia and they had some really neat tools that we still have this time like we had Dev Desktop which just made it really easy to spin up a site and play with it. Then, we had Drupal Gardens as well which you could just customize and then export that and then throw it wherever. So I did that for a couple of friends’ websites, and then I was like, “Where are these people located?” I saw they’re hiring so I just looked at their hiring page and applied to every job I could.

jam: Are you from the Boston area?

Ally Gonthier: Yes.

jam: Oh, that helped too, right?

Ally Gonthier: Yes.

jam: Okay, cool. So, how did you feel when you were accepted into the new Acquia U class?

Ally Gonthier: I’m ecstatic. I could not be more excited.

jam: Awesome. What were your expectations going in?

Ally Gonthier: I’m a little anxious, you know? I’m not super confident myself. I don’t know. It’s just something I had to work on. I mean, I’m going to just dive in and learn as much as I can and absorb it all.

jam: High five to that. So is it okay if we check-in again over the course of the program and see how you’re doing?

Ally Gonthier: Sure, absolutely.

jam: All right. I will see you some time soon.

Ally Gonthier: Okay.

jam: And good luck on Acquia U.

Ally Gonthier: All right, thanks.

jam: Thanks for talking to me.

Ally Gonthier: All right, great.

After Acquia U: Early 2016

jam: Ally Gonthier, it is now early-ish 2016. How are you?

Ally Gonthier: I’m well.

jam: Last time we were talking was the middle of 2015, right? And you were just going into Acquia U.

Ally Gonthier: Right.

jam: To recap, you’ve been at Acquia a while.

Ally Gonthier: Yes.

jam: And until you did Acquia U, your job title was?

Ally Gonthier: I was a Customer Support Coordinator.

jam: And what was your Drupal level, Drupal experience to be in that job?

Ally Gonthier: Zero basically. I didn’t need any Drupal experience for that position.

jam: Support coordinator?

Ally Gonthier: Yes.

jam: Then, you had the chance to do the Acquia U Drupal Bootcamp, tech boot camp thing.

Ally Gonthier: Yes, yes.

jam: How was that?

Ally Gonthier: That was eye-opening. It was crazy. It was fun. It was overwhelming. Every single emotion that I could ever – I was pushed to my limit and beyond. I cried more than once. I laughed more than once.

jam: I mean, it sounds funny that you say that but I’ve talked with a bunch of people ... It was a really powerful experience for a lot of people who have gone through the program.

Ally Gonthier: Yes, yes. I did things that I would have never normally have done and it gave me the Drupal picture, which I did not have before. It empowered me with my confidence. I knew what I wanted. I was just – it was a great experience.

jam: So I want to roll it back for a second. How did you end up at Acquia in the first place?

Ally Gonthier: I had always been in tech support for quite a while, different roles, different companies. I was sort of getting interested in web design, web development, and I was like, “Well, what’s the best?” So I was drawn to Drupal and I just literally downloaded Acquia Dev Desktop. I was like, “I wonder where these guys live.” I was like, “Oh, that’s 20 minutes away.” So I applied to three different positions. I interviewed for all of them and then they hired me.

jam: Cool, okay. So what was your thought process in going into Acquia U? What were you hoping for?

Ally Gonthier: I wasn’t sure. Ultimately, I wanted to grow and I wanted to try something different. Sad to say, but I wanted to make more money in the long run so ...

jam: There is nothing sad about that and, frankly, that’s a completely legitimate goal.

jam: What are some of the skills, some of the things that you learned in the – during the course?

Ally Gonthier: We built a bunch of different Drupal sites and, like I mentioned, it gave me the – it helped me for the big picture anyway. Like now I feel like I might not be a Drupal expert but I can join in the conversation and I can understand what my peers are talking about, you know? That’s like sort of the big part of it. I might not be an expert, but I know where the experts are. Now, I can have conversations with them, and grab that feedback, and learn from it so ...

jam: Even knowing how to figure out what the right question is and how to answer the question opens the door to enormous career, well, and enormous possibilities whether those are in career or whether doing something for yourself or your community with technology, right?

Ally Gonthier: Yes, absolutely. Yes.

jam: So what’s your title now? Did you get a new job coming out of Acquia U?

Ally Gonthier: I did. I am a Support Engineer now so yes.

jam: So you do actual Drupal on the job?

Ally Gonthier: Yes, I do. Yes, exactly. That’s right. So just like you described, I take questions. I might not know the answer, but I can find the answer and I have resources to help me with that. I’ve learned so much and every day just flies by. Of course, I’ve always loved the people I work with here. So I wouldn’t want to go anywhere else really.

jam: One of the things that I’ve always really admired about the approach that our global support team takes is that we’re not about – you have a problem with your website, you tell us what it is. We’ll fix it and then we’ll tell you it’s fixed and then go away. I’ve seen a lot of people share. They say, “Hey, so this got misconfigured. There was a problem on the server. The file system is corrupt in this way and these are the things that we did.” And whether subtle or not, we’re giving people the tools to help themselves or maybe not create the same problem for the second time. I imagine that you’ve got a situation where you now know enough about Drupal. You see all of these different everyday problems that people are having and every one of those is a chance for you to learn as well, right?

Ally Gonthier: Exactly, exactly. Definitely, yes.

jam: So you become more of an expert every day, more ready for – readier for new challenges, for new possibilities?

Ally Gonthier: Yes, that describes it. It’s fun. I like it.

jam: So you’re a problem solving sort of person?

Ally Gonthier: I am. I can’t do the same thing every day type of person if that makes sense.

jam: Oh, yes. So I remember talking with someone about their job in support saying that the best thing about working in support compared to working on a client project or an in-house project was, “Actually, I don’t have to touch the same code base every day. I get a completely different work day every day.”

Ally Gonthier: Every single day is something different. Different and you might touch something and not touch it again for three months. For me personally, it helps because I get bored honestly and in that kind of atmosphere, it’s really difficult to be bored, you know? So ...

jam: That’s really cool. So do you – let me think how to ask this. Do you have new and different career ambitions now?

Ally Gonthier: No, I don’t. I think I’m in a different point now where I’m just trying to do well at what I’m doing right now. Then, I’ve always thought of that like, “What’s next? What’s next? What’s next?” Right now, I’m just focusing on now and I’ll re-evaluate that eventually but for the time being, I’m pretty happy where I am right now so ...

jam: Cool, and Acquia U was part of putting you in this space right now. You’re pretty happy to sit and learn, and do this stuff?

Ally Gonthier: Yes, 100%. Yes, definitely.

jam: Cool. Well, congratulations.

Ally Gonthier: Thank you.

jam: We should probably make a pitch for Acquia Support being a really fun place to work.

Ally Gonthier: Yes, it is a lot of fun.

jam: Ally is a lot of fun to work with. I know that. So cool. So Acquia U, worth doing?

Ally Gonthier: Yes, yes. It was challenging. It was great. It was a good experience. It got me to where I wanted to be, so very happy for that.

jam: Excellent. Hey, so thanks for taking the time to come back and talk with me again.

Ally Gonthier: No problem.

jam: And you people watching this out on the internet have seen before Ally and this is after Ally.

Ally Gonthier: I’m sure I looked the same I hope.

jam: Well, you look enriched with Drupal knowledge now.

Ally Gonthier: Yes, I have the tattoo. No, I’m just kidding.

jam: Oh, you didn’t? Yes, you have to get that once you’ve taken the course.

Ally Gonthier: I know the secret handshake. No, I’m just kidding.

jam: It’s true. It’s real. Thanks, Ally.

Ally Gonthier: Thanks, jam.

Skill Level: BeginnerIntermediateAdvanced
Catégories: Elsewhere

Drupalize.Me: What's New in Drupal 8.1.0

jeu, 26/05/2016 - 17:10

Drupal 8.1.0 was released on April 20th. There are a few things that are exciting about this release; in particular the 2 new experimental modules BigPipe and Drupal Migrate UI.

Catégories: Elsewhere

Chapter Three: How to Register an Event Subscriber in Drupal 8

jeu, 26/05/2016 - 16:30

Events in Drupal 8 allow for different components of the system to interact and communicate with each other. One system component dispatches the event at an appropriate time; many events are dispatched by Drupal core and the Symfony framework in every request. Other system components can register as event subscribers; when an event is dispatched, a method is called on each registered subscriber, allowing each one to react.

Most of the hooks from previous versions of Drupal were removed in Drupal 8 in favor of Events. Example: hook_boot() which now can be done by registering an event subscriber.

I will use the following structure for the example module:

Catégories: Elsewhere