Drupal Planet

Syndicate content
Drupal.org - aggregated feeds in category Planet Drupal
Updated: 7 hours 13 min ago

Mediacurrent: Blockchain: Long Thoughts

Fri, 2017-09-08 08:00
First thoughts...

It has always been said that “the book is better than the movie.” This blog post gives a behind-the-scenes look at the writing that inspired the Friday 5 video.

Why?

Due to the Mediacurrent Friday 5 being a series that lasts 5 minutes, and the unfortunate absence of a suitable ”Friday half hour to 45 minutes” show, the content would be again, reimagined.

Categories: Drupal

Blair Wadman: Accessible Drupal 8 modals when Javascript is disabled

Fri, 2017-09-08 05:01

In the previous tutorial, you learnt how to create a modal in a custom module. If you missed it, you can check it out here.

Categories: Drupal

InternetDevels: Why Drupal should power your content-heavy website

Fri, 2017-09-08 02:29

More and more often, developers and users see that Drupal is arguably the most powerful CMS today. We have also repeatedly written about the benefits of Drupal for your business.

Read more
Categories: Drupal

hussainweb.me: Vagrant 2.0 and DrupalVM

Fri, 2017-09-08 00:01
Vagrant 2.0 has just been released. Being who I am, I jumped at trying this out and testing if it worked well with my vagrant setup. I have entirely moved to DrupalVM since some time and wanted to see if it worked properly.
Categories: Drupal

Nextide Blog: Maestro D8 Concepts Part 2: The Workflow Engine's Internals

Thu, 2017-09-07 17:34

The Maestro Engine is the mechanism responsible for executing a workflow template by assigning tasks to actors, executing tasks for the engine and providing all of the other logic and glue functionality to run a workflow.  The maestro module is the core module in the Maestro ecosystem and is the module that houses the template, variable, assignment, queue and process schema.  The maestro module also provides the Maestro API for which developers can interact with the engine to do things such as setting/getting process variables, start processes, move the queue along among many other things.

As noted in the preamble for our Maestro D8 Concepts Part 1: Templates and Tasks post, there is jargon used within Maestro to define certain aspects of the engine and data.  The major terms are as follows:

Categories: Drupal

Nextide Blog: Decoupled Drupal and Ember - Authentication

Thu, 2017-09-07 17:34

This is part 2 of our series on developing a Decoupled Drupal Client Application with Ember. If you haven't yet read Part 1, it would be best to review Part1 first, as this article continues on with adding authentication and login form to our application. Shortly, we will explore how to create a new article but for that we will need to have authentication working so that we can pass in our credentials when posting our new article.

Categories: Drupal

Nextide Blog: Maestro D8 Concepts Part 1: Templates and Tasks

Thu, 2017-09-07 17:34

Templates and tasks make up the basic building blocks of a Maestro workflow.  Maestro requires a workflow template to be created by an administrator.  When called upon to do so, Maestro will put the template into "production" and will follow the logic in the template until completion.  The definitions of in-production and template are important as they are the defining points for important jargon in Maestro.  Simply put, templates are the workflow patterns that define logic, flow and variables.  Processes are templates that are being executed which then have process variables and assigned tasks in a queue.

Once created, a workflow template allows the Maestro engine to follow a predefined set of steps in order to automate your business process.  When put into production, the template's tasks are executed by the Maestro engine or end users in your system.  This blog post defines what templates and tasks are, and some of the terms associated with them.

 

Categories: Drupal

Nextide Blog: Decoupled Drupal and Ember

Thu, 2017-09-07 17:34

This is the first in a series of articles that will document lessons learned while exploring using Ember as a decoupled client with Drupal.

You will need to have Ember CLI installed and a local Drupal 8 (local development assumed). This initial series of articles is based on Ember 2.14 and Drupal 8.3.5 but my initial development was over 6 months ago with earlier versions of both Ember so this should work if you have an earlier ember 2.11 or so installed.

You should read this excellent series of articles written by Preston So of Acquia on using Ember with Drupal that provides a great background and introduction to Ember and Drupal.

Categories: Drupal

Nextide Blog: Maestro Overview Video

Thu, 2017-09-07 17:34

We've put together a Maestro overview video introducing you to Maestro for Drupal 8.  Maestro is a workflow engine that allows you to create and automate a sequence of tasks representing any business process. Our business workflow engine has existed in various forms since 2003 and through many years of refinements, it was released for Drupal 7 in 2010. 

If it can be flow-charted, then it can be automated

Now, with the significant updates for Drupal 8, maestro was has been rewritten to take advantage of the Drupal 8 core improvements and module development best practices. Maestro now provides a tighter integration with native views and entity support.

Maestro is a solution to automate business workflow which typically include the movement of documents or forms for editing and review/approval. A business process that would require conditional tests - ie: IF this Then that.

Categories: Drupal

Nextide Blog: Maestro Workflow Engine for Drupal 8 - An Introduction

Thu, 2017-09-07 17:34

The Maestro Workflow Engine for Drupal 8 is now available as a Beta download!  It has been many months of development to move Maestro out of the D7 environment to a more D8 integrated structure and we think the changes made will benefit both the end user and developer.  This post is the first of many on Maestro for D8, which will give an overview of the module and provide a starting point for those regardless of previous Maestro experience.

Categories: Drupal

Drupal Association blog: DrupalCon Europe: Where do we go from here?

Thu, 2017-09-07 15:23

DrupalCon Europe plays an important role in moving Drupal forward. However, with waning attendance and financial losses, it’s time to find a new path forward so it is sustainable and continues to provide unique value. This blog proposes a better path forward for hosting a sustainable and valuable DrupalCon Europe . This blog is part of a series that includes:  

  1. The problems we need to solve for financial sustainability

  2. The problem we need to solve to create unique value

  3. Results from a proposal based on community input

  4. A new path forward for DrupalCon Europe

We are now at the end of our blog series. Thank you for digesting so much content. Determining the strategic direction for a region’s event is rather complex and there are many facets to understand. It was important to us to share all of the details with you.

The Drupal Association is a mission-based organization and not a business that makes purely financial decisions. Rather, we employ staff who are personally invested in achieving our mission. We feel it is imperative to find the best way to serve the European community and we took great care over the last several months to find a path forward that would achieve this.

We don’t see this exercise as just determining an event’s strategy, but how can we further the special and profound human experience that takes place when Drupalers come together in person.

In the end, we see that Europe needs a clear goal for DrupalCon so that the energy put into creating it truly strikes at the community needs, strategically moves the project forward in a sustainable way, and creates the human experience that Europeans want. Currently, the community is expressing competing goals. We believe that the European community is best suited to determine what the region needs DrupalCon to achieve, and especially because of the feedback from the community discussions, we want to give the region more agency to drive DrupalCon’s programming.

A Little History

The Drupal Association became an official 501(c)3 U.S. non-profit in 2011, and our first focus was hosting DrupalCon London (ok, Croydon). Since that time, Drupal events have grown and matured, like DrupalCamp London, Dev Days, and Frontend United. We are thrilled to see Drupal events in Europe doing so well and we are thankful for the volunteers who are making that happen.

What this maturity likely means is that Europe has the ability to drive DrupalCon Europe forward, tailoring it more closely to the region’s needs. We just need an operational model that allows us to give the event to the community without negatively impacting the community.

When DrupalCon was produced by the community before DrupalCon London, the event became too big for volunteers alone to manage. It put a lot of strain on the community. That’s why the Drupal Association took over event production. In the process, we managed to professionalize the event, but we also applied a US model and we know that doesn’t feel authentic to attendees. The waning attendance and sponsorship reinforces that the event is not meeting needs, and the financial losses and staff working at over-capacity highlights that we are applying the wrong operational model.

It is time to break the mold and approach DrupalCon Europe completely differently. I believe the best approach to explore is a licensing model. That’s a contractual term for giving an entity the right to run a DrupalCon.

Licensing DrupalCon

There may be several operational models to explore and I want to hear about them from you. Until then, I’d like to share why we should consider the licensing approach.

Licensing gives the European community the agency they have asked for so they can create an event that is more European and has more desirable content. Once we get this model to work in Europe, we can leverage this creativity so other regions and countries can have DrupalCon too, like China, India, Australia, Brazil, or Costa Rica. This change expands DrupalCon’s reach and impact, moving the project forward in a strategic and global way.

While I have the rough concept in mind, I don’t have all the answers on how to license DrupalCon, but here are some broad brush strokes:

  • We want to give DrupalCon to a community-based entity that has proven event experience and demonstrated ability to serve the community. The entity needs to be grounded in the community so they can decide how to best serve the region’s needs and move the project forward in the right ways.

  • The Drupal Association would have some requirements that protect the brand experience such a Driesnote to kick off the event, the venue needs to meet certain needs like accessibility, the Code of Conduct must be applied so the event remains welcoming, there is diversity in speakers and attendance, and the official DrupalCon branding is used.

  • The Drupal Association would also have financial and reporting requirements, but we need to feel our way through what this looks like. We encourage the event organizer to make the event profitable and we would apply a license fee schedule as they become more sustainable.

  • The Drupal Association wants the event organizers to have freedom to tailor the event to the region’s unique needs. What Europe needs may be completely different from what Brazil needs, should they want their own DrupalCon as some point. The event organizer would pick who the target audience is, the programming structure, etc.

Clearly there are many details to work out if we go down this path. However, we can look to other Open Source Software projects who use this model to gain insights and best practices.

It will take time to set up this structure. The Drupal Association needs to work on this internally and as we mentioned before, we have a serious capacity issue that prevents us from working on this initiative while also producing DrupalCon.

The only way to free up staff capacity to work out a long-term solution is for Drupal Association to not host DrupalCon Europe in 2018.

DrupalCon Europe 2018

“What? Did she really just say what I think she said?” Yes, it’s true. I did say that the Drupal Association will not be hosting DrupalCon Europe in 2018. It doesn’t feel good saying this and I labored over this decision with others on the board and in the community for a long time. But, sometimes you have to take a step back to take a big step forward. Europe deserves a better DrupalCon that feels authentic and meets their needs. And countries around the world deserve access to this very special event.

We know that these changes could feel like Europe is being abandoned or not supported as much as the U.S. We empathize with those who may feel this way and that is certainly not what we want to convey. I want to be clear that the Drupal Association will definitely support Europe in 2018.

Supporting European Drupal Events in 2018

European Drupal events are strong and make a big impact. They are important Drupal contribution and adoption engines and we want to give those engines more fuel in 2018. In order to do that, the Drupal Association commits to the following:

  • Dries will keynote some European Drupal events

  • Drupal Association will aggregate and market European Drupal events to our lists and through our channels

  • Drupal Association will email our sponsors, encouraging them to sponsor camps

  • Drupal Association wil host 2-3 community organizer virtual round tables to foster knowledge sharing and problem solving.

What are other ways we can support Europe in 2018?

Here are some other ways we can support Europe in 2018. Let us know if these ideas could better serve the European community:

  • Camps bid to host DrupalCon Europe 2018. Camps have very similar programming to a DrupalCon and Dries could provide a Driesnote, While this is a viable option to keep DrupalCon alive in 2018, event organizers pointed out that this has some downsides to consider.
  • The camp will need to cap the attendance to the size for their venue.

  • Even though the expectation would be to run the camp as usual with the additional DrupalCon elements like a Driesnote, organizers and volunteers could get burnt out, and that helps no one.

  • Camps bid to be the “Official Camp of the Region in 2018”. I’m sure we can come up with a better name, but the idea is that camps bid for why community members should come to their camp. Then they get the “Official Camp To Go To in 2018” status and the Drupal Association will help promote that camp. Community organizers felt this idea has some merit because:

    • It doesn’t put pressure on camps to be something more. They can produce the program they are used to providing. Of course, more people may attend that camp and the organizers have to be prepared for this - or know when and how to cut off registration so they are not overwhelmed.

    • We create a new concept that can be leveraged in other regions

What do you feel is the best way to serve Europe in 2018? We want to hear. Tell us in the comments section and or meet us in the meetings listed below.

What About DrupalCon North America?

Community members asked me why we are only making a change to DrupalCon Europe and not to DrupalCon North America. It’s a good question. The simple answer is that DrupalCon North America is financially stable and growing. It provides 45% of our total revenue and that funds Drupal.org. The Drupal Association needs to be very mindful that changes don’t impact this important funding source.

Learn More at DrupalCon Vienna

Again, thank you for taking this journey with us to understand the challenges we have been facing with DrupalCon Europe and how we can solve them, together. I am encouraged by the many community members who have helped us and I look forward to moving this discussion forward in person at DrupalCon Vienna.

Please join me at the following sessions to discuss 2018 and beyond:

Community Summit

BoF 1

BoF 2

Drupal Association Board Meeting

Post DrupalCon Virtual Meeting

  • Thursday 16:00 CEST
  • For those that can not attend DrupalCon Vienna, we will host a webinar to share themes from the DrupalCon meetings, here your additions to the discussion, and talk about next steps.
  • https://zoom.us/j/241666153
Categories: Drupal

Lullabot: Talking Performance with Pantheon's David Strauss and Josh Koenig

Thu, 2017-09-07 13:00
Matt & Mike are joined by Pantheon co-founder and CTO David Strauss, Pantheon co-founder and Head of Product Josh Koenig, as well as Lullabot's own performance expert Nate Lampton to talk everything performance. Topics include front-end performance, server-side PHP, CDNs, caching, and more.
Categories: Drupal

Drupalize.Me: Drupal 8.4 is Coming Soon

Thu, 2017-09-07 10:03
Categories: Drupal

Phase2: How Digital Government Is Evolving with Drupal

Thu, 2017-09-07 09:39

In 2012 we wrote a blog post about why many of the biggest government websites were turning to Drupal. The fact is, an overwhelming number of government organizations from state and local branches to federal agencies have chosen to build their digital presence with Drupal, and government continues to adopt Drupal as the content management system of choice.

Categories: Drupal

Acquia Developer Center Blog: Boston Drupal Meetup Considers Distributions

Thu, 2017-09-07 08:46

The topic was “Distributions” at the September Boston Drupal Meetup, which was held at Acquia HQ in downtown Boston, and attendees were treated to an unusually comprehensive session.

That’s because Drupal Project Lead Dries Buytaert kicked off the meeting by going waaay back, to the very first Drupal “distro.”

To back up a bit, a distribution is a combination of Drupal core + modules + configuration + documentation -- all bundled up and optimized for a particular purpose or group of users.

Tags: acquia drupal planet
Categories: Drupal

Mediacurrent: Autocomplete Deluxe Released for D8

Thu, 2017-09-07 08:11

I am excited to announce that the D8 port of the Autocomplete Deluxe module has been released in “beta”!
 

What does it do?

The Autocomplete Deluxe module provides a widget that enhances the default autocomplete field in Drupal. It uses jQuery UI autocomplete and provides a slick visual element for content editors to reference terms - displaying them inline, drag-n-drop reordering, and creation of new terms from the field itself. It works out-of-the-box and no 3rd party libraries are needed.
 

Categories: Drupal

Drupal blog: Drupal 8.4.0-rc1 is available for testing

Thu, 2017-09-07 05:47

The first release candidate for the upcoming Drupal 8.4.0 release is now available for testing. Drupal 8.4.0 is expected to be released October 4.

Download Drupal-8.4.0-rc1

8.4.x includes new stable modules for storing date and time ranges, display form errors inline and manage workflows. New stable API modules for discovering layout definitions and media management are also included. The media API module is new in core, all other new stable modules were formerly experimental. The release also includes several important fixes for content revision data integrity, orphan file management and configuration data ordering among other things. You can read a detailed list of improvements in the announcements of alpha1 and beta1.

What does this mean to me? For Drupal 8 site owners

The final bugfix release of 8.3.x has been released. A final security release window for 8.3.x is scheduled for September 20, but 8.3.x will receive no further releases following 8.4.0, and sites should prepare to update from 8.3.x to 8.4.x in order to continue getting bug and security fixes. Use update.php to update your 8.3.x sites to the 8.4.x series, just as you would to update from (e.g.) 8.3.4 to 8.3.5. You can use this release candidate to test the update. (Always back up your data before updating sites, and do not test updates in production.)

For module and theme authors

Drupal 8.4.x is backwards-compatible with 8.3.x. However, it does include internal API changes and API changes to experimental modules, so some minor updates may be required. Review the change records for 8.4.x, and test modules and themes with the release candidate now.

For translators

Some text changes were made since Drupal 8.3.0. Localize.drupal.org automatically offers these new and modified strings for translation. Strings are frozen with the release candidate, so translators can now update translations.

For core developers

All outstanding issues filed against 8.3.x were automatically migrated to 8.4.x. Future bug reports should be targeted against the 8.4.x branch. 8.5.x will remain open for new development during the 8.4.x release candidate phase. For more information, see the release candidate phase announcement.

Your bug reports help make Drupal better!

Release candidates are a chance to identify bugs for the upcoming release, so help us by searching the issue queue for any bugs you find, and filing a new issue if your bug has not been reported yet.

Categories: Drupal

Appnovation Technologies: Project Spotlight – J.D. Power Advanced Search

Thu, 2017-09-07 04:52
Project Spotlight – J.D. Power Advanced Search Appnovation was recently tasked to redesign J.D. Power’s car and article search functionality. The current car search implementation was based on Drupal views searching against the database, while the article search was a basic Apachesolr (Drupal contrib module) search page. The car and article search functionality was to be based on A...
Categories: Drupal

Agiledrop.com Blog: AGILEDROP: The drought is over, Antwerp is here

Thu, 2017-09-07 02:04
The drought is finally over. After a long time with no events in which we participated, it is once again time to go around the world and share the knowledge. The two summer months (July and August) are practically always »spleepy«, so we are thrilled to announce that we will be seeing you tomorrow at DrupalCamp Antwerp. We promised that you will be informed as much as possible about where to find us besides in our office. We are keeping our promise once again. So, if you have a particular subject in mind and you like discussing things about Drupal, or anything really, say hello to us at the… READ MORE
Categories: Drupal

Chapter Three: How to Alter Node URL Alias Based on Taxonomy Term in Drupal 8

Thu, 2017-09-07 01:00

Recently I had to generate term-specific aliases (aliases that are different from the default alias pattern set for Article entities). This is how to do it:

1. Enable the Pathauto module
2. Set the default URL alias pattern for your content type in order to fire the hook
3. Implement hook_pathauto_alias_alter() in your .module file.

Example module structure:

mymodule/ - mymodule.info.yml - mymodule.module - src/ - ArticlePathAlias.php

I like to keep .module clean and simple and because of that I store the main logic in src/ArticlePathAlias.php file.

The mymodule.info.yml this is just a regular .info file.

4. Add the following to your mymodule.module file:

Categories: Drupal

Powered By