Updating modules in Drupal 8 is similar to updating modules in Drupal 7 - the drush pm-update (drush up) command still works, but there's a new "gotcha" that you need to look out for when updating modules that work with entities.
Sometimes, after updating modules that interact with entities, you'll see a "Entity/field definitions: Mismatched entity and/or field definitions" error on your site's status report (admin/reports/status).
In the screenshot above, this error was generated by updating the Inline Entity Form module from its alpha4 version to the most recent -dev version (the site also uses the Scheduled Updates module). As long as a mismatch is present, the fields listed in the error will lead to unpredictable results.
Neither rebuilding caches nor running cron will fix this issue ("drush up" doesn't automatically run this command either) - for these types of errors, the drush entity-updates command is what you're looking for.
Once this command is run, your status report will look something like this:
This is just one more reason why checking your site's status report page after updating modules is always a good idea.
Using Vagrant to manage virtual machines in a development workflow has become a life-saver and standard practice in many cases. Running a project server inside a virtual machine sidesteps the majority of the custom configuration that used to be required on a developer’s machine, but at the same time it introduces a new machine to connect to and manage.
This episode Bob is out on assignment so we have Matt Davis in his stead to talk about our upcoming invasion of Sandcamp on February 24th and then Florida Drupal Camp on March 5th. Mario has the latest blog posts from Mediacurrent.com, there will be actual content in the Maildrop, Ryan brings us home as always with The Final Bell.
A fundamental part of ThinkShout’s philosophy and business is to not only use great open source tools, but to actively give back to the open source community. The most recognizable part of that contribution is in the form of Drupal modules: over 60,000 Drupal sites run on ThinkShout technology! This strategy has been a huge win for our clients, who get features, bugfixes, and security updates from the community because they are sharing code. We benefit from this work as well, as it enhances our profile in the community and helps us generate leads for new projects. Of course, the vast majority of these sites are built on Drupal 7, which released in the same month that ThinkShout was founded.
The exciting and much-anticipated release of Drupal 8 has given us a lot to think about. Internally, we’ve been running a Drupal 8 "book club" to give our development team a chance to dive in and figure out what’s going on with D8. While we’ve bathed in the glories of Composer, Twig, and YAML files galore, we’ve also had a chance to start upgrading a few of our favorite modules to Drupal 8!
With support from the incredible folks over at MailChimp, we’ve already got a working release of the MailChimp integration module for Drupal 8, and are hard at work on the integration with Mandrill, MailChimp’s awesome transactional email service, which may have a Drupal 8 release before this blog post goes live.
This is a great start, but it’s really only the tip of the iceberg: ThinkShout has about 50 modules released for Drupal 7! As much as we’d love to dive in and update all of them for Drupal 8 today, that’s not particularly practical. To better focus our work, I analyzed some of these modules so we can prioritize them and look for opportunities to work with our partners and clients to get the most useful, popular, and important modules upgraded to Drupal 8 first.
Of our 50 modules, we started by de-prioritizing anything that was:
Extremely narrow in purpose (Entity Reference Plus Data)
Blocked by another module’s Drupal 8 development (Apache Solr Geo, lots of others)
Offers modest functionality replaceable by custom code (Footer Message) or
Just not seeing much usage (Instagram Realtime)
That left us with around 10 projects, among them MailChimp and Mandrill, which we were already working on. We wanted to pick a manageable number of these remaining modules to get started on.
Based on community usage, the priorities of our clients, and perceived usefulness, it was clear that the Registration module belonged on this list. The story of Registration’s development is connected to the story of ThinkShout’s fledgling years and open source philosophy, so it’s an added bonus that Registration will be part of our early push into Drupal 8.
ThinkShout has also carved out a reputation as experts in the CRM world, with RedHen, our leading Drupal-integrated CRM, and the Salesforce Suite, a fabulous tool for integrating Drupal sites with Salesforce. Though these modules don’t have the 5-digit usage numbers that Registration or MailChimp have, they still have lots of users who are very engaged, and are central to the needs of our clients. We added them to the top of the list for Drupal 8 consideration.
In thinking about the rest of our modules and the nature of our work, it became clear that these three projects really stand out from the rest: they are our "Big 3", and we set about creating a roadmap for developing them on Drupal 8.
You can already see the beginnings of this work! At our team sprint on February 11, we put together an outline for bringing RedHen to Drupal 8, and pushed the first commits to Drupal.org.
These are our sprint faces!
As of February 11, all of the Big 3 have nominal Drupal 8 branches.
As we kick off four Drupal 8 sites in the first part of this year, we will be working with our clients to bring Registration, RedHen CRM, and Salesforce Suite to Drupal 8. All three should update beautifully, as they are built on top of Entity API, which is part of Core in D8.
We will also be focusing our internal open source contribution hours on these three projects to kickstart their jump into the Drupal 8 sea. If you’re looking for awesome CRM or registration systems for your Drupal 8 site, fear not! They are on their way.
We have two Drupal 8 sites utilizing ThinkShout core technologies scheduled for launch this summer, so look for a release of RedHen in the spring!
Our next round of prioritization will depend significantly on the progress of Commerce solutions in Drupal 8: once that landscape settles, we have some projects that will jump up that priority list, including:
Registration Commerce, our favorite paid registration solution
RedHen Donation, our CRM-integrated, single-page donation tool
So if you’re a fan of our Commerce integrations, or Add to Cal, or even little Bean Entity View (I know I am): stay tuned! We love these tools, we love that you’re using them, and we look forward to bringing you even more awesome stuff for Drupal 8 than we have for Drupal 7!
Our Drupal developers will continue sharing Drupal 8 tips with you. We have published articles so far about configuration in Drupal 8, general tips on Drupal 8 development, and on using Twig in Drupal 8.Read more
The monthly security release window for Drupal 6, 7, and 8 core will take place on Wednesday, February 24.
This does not mean that a Drupal core security release will necessarily take place on that date for any of the Drupal 6, 7, or 8 branches, only that you should watch for one (and be ready to update your Drupal sites in the event that the Drupal security team decides to make a release).
February 24 is also the end-of-life date for Drupal 6, so this will be the last security release window for Drupal 6.
There will be no bug fix or feature release on this date. The next window for a Drupal core patch (bug fix) release for all branches is Wednesday, March 2, 2016. The next scheduled minor (feature) release for Drupal 8 will be on April 20, 2016.
Thank you! Drupal Association and Drupal Indian Community Members for putting together the most fabulous experience for the Drupal enthusiasts of the community. The Venue sponsor IIT Mumbai needs a special mention.
Our Journey @DrupalConAsia, A short message from each of our Drupal Development team and their learning and contributions at DrupalConAsia
DrupalCon Asia 2016 has just finished, and it was like no other DrupalCon ever. This is the third time DrupalCon has ventured outside it's normal North American or European location.
When creating various pages developers often have to generate links, URLs and occasionally redirect users to where they came from, or any other arbitrary page. In Drupal 7 we used l(), drupal_get_destination() and drupal_goto(). As you may suspect, things have changed drastically with Drupal 8. Although drupal_get_destination() is still there, it is marked deprecated, so we should not be using it any longer.Tags: acquia drupal planet
I'm excited to announce the release of Drupal VM 2.3.0 "Miracle and Magician"—with over 21 new features and bugs fixed!
One of the most amazing improvements is the new Drupal VM dashboard; after you build Drupal VM, visit the VM's IP address to see all the sites, tools, and connection details in your local development environment:
This feature was singlehandedly implemented by Oskar Schöldström—who also happens to have practically matched my commit activity for the past month or so. I'm pretty sure I owe him something like 100 beers at this point!
Here are some of the other great new features of Drupal VM in 2.3.0:
DrupalCon New Orleans may still seem far, far away in the distant future — but it’s not! — and the deadline for session submissions is quickly approaching! February 29th will be here in one short week. Can you believe it?Kathryn McClintock Mon, 02/22/2016 - 15:42
This is a friendly reminder to get those submissions in soon so the Drupal community can have its best DrupalCon yet in the Big Easy!
This year, Eric Sembrat is heading up the Frontend track and I’m supporting him as the global chair. We’re excited for the broad range of topics this track includes: everything from atomic design to client-side applications.
We’re looking to fill the track with fresh perspectives on some of the more usual suspects: Twig, sustainable development patterns, best practices, plus new tools and techniques!
So this is a challenge to you, Drupal Frontenders — to fill our plate with a plethora of inspiring submissions so we can help you have a great DrupalCon. The call for papers closes at midnight on Monday, February 29th. Mark your calendars so you don't miss out!
In case you missed it, here's that link again: click to submit your session
See you all in New Orleans!
Drupal association plays a key role in supporting Drupal Project, Drupal.org and the Drupal community. I am contesting for the Director At Large post on Association Board to help support the organization.
I would like to work with the Drupal Association and be a representative of the Asian community and contribute towards building community strategy. I would like to make a positive contribution towards community participation not only in terms of numbers but also in terms of quality of participation.
Having worked in multiple initiatives in the Drupal project, I understand and can align myself with the key goles of the association. Additionally my expeience in building Drupal teams and having been involved in strategic decisions in my organization will be of value in this role.
Want to know more about me, Shyamala Rajaram, checkout the candidate profile at: https://assoc.drupal.org/election/2016-director-large-election/candidate...
Did you have a great time at DrupalCon Asia but want something to show for it?
We are happy to issue a certificate of attendance in PDF format for anyone who picked up their conference badge or signed in at a training.
Simply submit your request via our contact page with the subject "Request a Certificate of Attendance".
In the first part of this series, we showed you how to perform a very basic migration without any customisation. In this part, we will show you how to modify some fields during migration.
Once the dust settles we will begin to realise DrupalCon Asia was indeed a seminal moment in the history of Drupal. In this short time, as I've managed the social media for the conference, I've watched the Asian Drupal Community come of age.
Huge respect has grown for the region has been born out of the event through high calibre presentations, floorless executing of the event, sheer energy, cultural diversity and harmony. I have no doubt this event was exactly the impetus the region deserved. There's a lot to celebrate.
— Larry Garfield (@Crell) February 19, 2016
One of the reasons for the heightened sense of importance everyone placed on the event undoubtedly stems from the fact for 840 of the 1025 attendees (82%) this was their first DrupalCon. It's been a long time coming, a huge anticipation surrounded the event. More than ever before this con mattered to everyone who passed through the doors.
for 840 of the 1025 attendees (82%) this was their first DrupalCon
So many have taken their first brave step onto the stage of the international speaker circuit, volunteered as sprint mentors, helped organisers with logistics, organised BoFs, met with their peers from across the region and the world.
Many overseas Drupalists recognised the gravity of this event DrupalCon Asia and they came in force. We saw a very strong international presence with attendees from 32 countries including USA (40), UK (15), Australia (10) and Japan (9). Dries Buytaert, Angie Byron, Alex Pott, Gábor Hojtsy, Josef Daernig, Dave Hall, Donna Benjamin to name just a few. Josue Valencia travelled the furthest from Guayaquil, Ecuador (16,499 km).
For years the significance of Drupal's Asian powerhouse has been gathering steam, this event provided the perfect showcase to the world. The event was a triumph for inclusivity and diversity not only that ladies represented 16.5% attendees but also that through Drupal people are able to transcended cultural, political and physical boundaries.
— Rachit Gupta (@tweet_rachit) February 21, 2016Drupal community celebrated
— Innoppl India (@InnopplIndia) February 20, 2016Record breaking sprint participation
What really impressed was that over 350 (34% attendees) came to the contribution sprints. This is the greatest proportion witnessed at any DrupalCon to date.
— xjm (@xjmdrupal) February 21, 2016
— Josef Dabernig (@dasjo) February 21, 2016
— Josef Dabernig (@dasjo) February 21, 2016A whole lot of fun!
Between all the sessions, BoF's, hallway track, summits and trainings there was a huge amount of fun going on too. Sand drawings, kite flying, Octocat competitions, . What occurs to me is how do Europe and USA follow this up? The baton passes to New Orleans.
— Paul Johnson (@pdjohnson) February 19, 2016A touch of Bollywood hits DrupalCon
— Holly Ross (@drupalhross) February 20, 2016Best #Prenote ever?
— Gaurav Mishra (@gmishra) February 20, 2016
— Prateek Sharma (@meprateeksharma) February 19, 2016
— Josef Dabernig (@dasjo) February 20, 2016Building bridges between communities
— GitHub Education (@GitHubEducation) February 21, 2016Kite flying outside on the green
— Gaurav Khambhala (@gkhambhala) February 20, 2016The most selfies ever at one DrupalCon
— Josef Dabernig (@dasjo) February 20, 2016
— Kavitha Sriram (@kavithad7) February 19, 2016
— DrupalCon Asia (@DrupalConAsia) February 19, 2016
— Dave Hall (@skwashd) February 19, 2016and dries in a turban
— pvishnuvijayan (@pvishnuvijayan) February 19, 2016Here's a non alcoholic drink to DrupalCon Asia! Where next?
— Josef Dabernig (@dasjo) February 19, 2016
Header photo by Michael CannonFurther information: Map of DrupalCon Asia attendees by Josef DabernigDrupalCon Asia Flickr Group
I'll be hosting a Reddit AMA on the Drupal subreddit tomorrow morning, Monday February 22, starting at 10 a.m. Eastern / 9 a.m. Central.
During the AMA, I would love to hear any questions you have about Drupal VM, Honeypot, Ansible, writing, open source communities, or really anything else you can think of! I just wrapped up a big project last week, so I'll have a couple hours tomorrow to talk about anything and everything with the Drupal community on Reddit. Even horse-sized ducks and Legos, if you're so inclined.
I'll also be formally announcing the next major release of Drupal VM, with some amazing new features for local Drupal development, so please check in tomorrow morning!