Whether you are a Drupal newcomer or a seasoned Drupal developer, you're bound to run into one, some, or all of the issues outlined below. Some are obvious, some not so obvious, but we'll show you how to troubleshoot them all regardless.
Firewise USA™'s paper application process existed for 15 years but, in 2016, the Firewise team decided to bring the process online. They chose to build this process on top of Drupal 8.
Since moving to Drupal, the Wildfire Division of the National Fire Protection Association has streamlined their processes - enabling them to more efficiently deliver on their program’s goal: teaching individuals how to adapt to living with wildfires and take community action to prevent loss of property.
Join us, Acquia, and our client Aron to discuss the challenges and rewards of bringing a paper process online as a Drupal 8 web app. Topics we’ll discuss:
- Leveraging an agile philosophy to respond quickly to change, collaborate across disciplines and stakeholder groups and get to a working product in as little time as possible.
- Balancing effective deliverables with shared understanding to produce working software that meets the organization’s needs.
- Organizational hurdles to overcome when adding structure and bringing an established paper application process online.
A point of sales system is already in production in Drupal 7; people are using it and seem to like it. And now, we've ported it to Commerce 2 for Drupal 8. Check out this week's High5 to learn more!What does this mean?
In Drupal 8, the POS is much more built in, and you can easily do things like change out widgets. So if you update your orders and you add a new field, the field will show up there. If you add a specific widget that controls how that field displays, you can pick from a list of available options and it will work in the POS.How is this different?
In Drupal 7, the POS was very stand alone—it was all custom-built forms and custom-built options. You actually configured it outside of Commerce itself. It used some of the underlying parts of Commerce, but from a user perspective it was almost as if it was a separate module.
For Drupal 8, that's not the case. It has the same level of functionality, but it's integrated much more so you can use a lot of the Commerce infrastructure. For instance: Drupal 7 had the concept of locations (as in store locations), but Drupal 8 has the concept of stores built right in, so we just use that. There's lots of stuff that goes along with stores: you can attach addresses and extra billing information and so on, and the POS can take full advantage of that in Drupal 8.Are there any new features?
We have quite a bit more reporting (such as KPI reports for tacking metrics for sales people, for instance.) We also have a new "quick add" section that lets you easily add common products without having to look them up by SKU—it's quite robust and fits nicely into the user interface.When will all this be ready?
We're only at Alpha 1 right now. Alpha 2 should be coming soon. The module should be fully ready to go in the near future. You can download it's current state and follow progress here.The bottom line
POS is finally ready for Drupal 8. You can start using it, and we're going to continue releasing new features at least once a month for the foreseeable future.
Hello Drupalers! Here is another #Tips&Trick to make your placeholder translatable. Recently, I have an opportunity to fix one of the issues in Drupal 8 instance where the website was not multilingual hence unable to handle internationalization. After fixing the issue, the contact form now supports more than 25 languages. Let me explain you, what exactly was the issue over here? And how did we overcome this issue?
Issue: Here, Drupal Contact Form Placeholder was not translatable from User Interface Translation.
As we all know anything passes…
This time we want to draw your attention to one of the serious questions - Drupal adoption, and two easy things everyone can do to facilitate it. I guess the Drupal Community helped you a lot when you were a newbie. Now it’s time to pay back and help the Community and its developers to grow and mature faster.
Appnovation Technologies: Website Accessibility Series, Part 2: Accessibility, Audits and Alterations
We recently Open Sourced our temporary environment builder, M8s. In this blog post we will be demoing everything you need to get started!by Nick Schuch / 21 November 2017 Introduction
In this video we will introduce you to M8s and the problem which it is solving.Provisioning a M8s cluster
Now that you are acquainted with the M8s project, it's time to get a cluster provisioned!
In this video we will setup a Google Kubernetes Engine cluster and deploy the M8s API components.Setting up CircleCI
Now that our M8s cluster is up and running, it's time to setup our pipeline to run a build.
In this video we will be configuring CircleCI to run the M8s CLI.Pushing a topic branch
It's time to put it all together!
In this video we will be pushing a topic branch to demonstrate how M8s interacts with a Pipeline.Finale
You made it to the finale! In this video we will be checking out the build environment and how a developer can access the Mailhog and Solr containers.Conclusion
To learn more about the M8s project you can go and checkout:
We welcome any and all feedback via Twitter and our Github Project issues page.Tagged m8s, Kubernetes, Drupal Development
Sys Ops Lead
Dated 21 November 2017Add new comment
This month, our membership campaign celebrates the ways we, together, build community on the home of the Drupal project. Hear from the Drupal Association team how and why Drupal.org offers you tools to make more connections, to increase your potential for a fulfilling professional career, and to enable your contributor journey in Drupal.
You can do a lot on Drupal.org and its sub sites. Check out the campaign page. We hope you are inspired to learn more about what Drupal.org offers and if you aren't yet a Drupal Association member, join today!Want to help our campaign?
We need your help so we meet our two goals: sign up 50 new members and raise $1500. We've made a page of resources for you to share.
Thank you for building community with us!
Notes from the November 20 meeting:
@drpal's update on the past week's work
- Ongoing work on the React dblog prototype: https://github.com/mattgrill/drupal-react-dblog & https://www.drupal.org/project/react_admin
- Core JS cleanup: https://www.drupal.org/project/drupal/issues/2915784 and https://www.drupal.org/project/drupal/issues/2917234 need review and are blocking subsequent work. Split https://www.drupal.org/project/drupal/issues/2925064 into issues with smaller scope.
- Shared questions to explore with the framework experiment:
Using https://github.com/mozilla-services/react-jsonschema-form as a way to generate React forms without requiring developers to learn React. Possible replacement for Form API. Is this something that seems viable / a good idea?
- The way they use JSON schema is valuable; not necessarily the implementation.
Related core issue: https://www.drupal.org/node/2913372
- Explore separate react-ui and react-json-schema. tim.plunkett has code locally for the schema piece and will post a patch.
- The way they use JSON schema is valuable; not necessarily the implementation.
- Initiative communication
- What's the next UI after dblog?
- https://www.drupal.org/project/drupal/issues/2830584 could be a candidate for exploration once the dblog is done
- Don't take on a new UI yet since there's more work we can do with the dblog (forms, components)
- On rewriting modals: Can you partially opt in to a new UI? https://reactjs.org/docs/portals.html might help
- What are the next steps around the React DBLog prototype + component ui library, json schema forms?
- Take Tim’s work and try to generate form components from Drupal data
- Do we want to actually add a new dblog to core or is it solely for an experiment?
This past weekend, I was honored to be able to present a session at 2017's New England Drupal Camp (NEDCamp) about Drupal 8's Migrate API. Redfin has implemented many Drupal 8 migrations to date both from CSV data sources and legacy Drupal sites (Drupal 6 and 7). As a result, we want to share with you what we've learned in hopes of saving you the time often spent in the trials and errors of data migration.Chris November 20, 2017
DrupalCamp Atlanta was such a great experience -- I can't decide if it was a great end to a good year or the beginning of even a better year. My last blog post was about organizing and presenting the Webform training materials, which was in preparation for my three-hour Webform training at DrupalCamp Atlanta. Suffice it to say, it was an enlightening experience. Not to mention I learned a few things...
First off, I am in awe of all the people in the Drupal community that are 'professional trainers'. The ability to understand and explain something as complex as Drupal is no easy task. The 14 attendees at my Webform training had various skill levels. Because my leg did not nervously shake at all during my three hours at the podium, I can finally say my comfort level with public speaking is increasing. I also came away with some invaluable, practical information. Prior to attending DrupalCampAtlanta, I had completely underestimated how hard it is to coordinate people to do hands-on exercises, like installing and building a webform. After the first hour of the training, I took a break and decided that the hands-on exercises were going to be impossible to accomplish in the remaining two hours, and that the training should instead focus on walking through all the material while answering any questions. I haven’t given up hope on being able to do hands-on exercises, however, I do need to rethink my approach. Fortunately, I was able to attend other sessions, watch some 'profession trainers' in action, and learn a few things.
The Drupal Association is excited to expand its team with two new staff members who are filing the roles Conference Director and Community Liaison. Please join me in welcoming Brooke Candelaria and Rachel Lawson. Both are going to add great value to the Drupal Association team as well as to the Drupal community.Conference Director
We are excited for Brooke Candelaria, our new Conference Director, to join the team. She will infuse DrupalCon with ideas that draw on her extensive technology event experience in open source - Python specifically. In addition to taking over DrupalCon North America planning, Brooke will be a great partner in finding the best way to deliver DrupalCon globally. In addition to Brooke’s expertise, she brings enthusiastic energy to everything she does whether that is planning events or volunteering for the Houston Livestock Show and Rodeo. Brooke resides in Houston, Texas, USA.Community Liaison
The team is equally excited that Rachel Lawson has agreed to join the team as our new Community Liaison where she will engage with the Drupal community to build a better relationship and understanding between the Drupal Association and the community. Rachel is well suited for this position given her background as a Drupal developer as well as her communications experience in the pharmaceutical industry. Even more impressive is that Rachel has been in the Drupal community for over 11 years and played many important roles such as Community Working Group member, Sprint Lead and mentor, DrupalCon and camp presenter, and more. Rachel has demonstrated time and again that she is a great communicator and has a natural talent to rally people behind a common goal. While you will see Rachel mostly online, she will still be touring Drupal events on her motorbike. Rachel resides in Norfolk, UK.
It’s always hard to be a newcomer. Let’s help Drupal beginners to take a step forward this CMS, and show them what changes Drupal brought into our lives. In this blog post, we will tell you about the #DrupalChanges initiative, and how you can help to enhance the Drupal adoption.
In my recent talk at DrupalSouth Auckland 2017 I took a hard look at the hyperbole of Drupal supposedly powering over a million websites. Where does Drupal really sit in relation to other CMS platforms, both open source and proprietary? What trends are emerging that will impact Drupal's market share? The talk looked outside the Drupal bubble and took a high level view of its market potential and approaches independent firms can take to capitalise on Drupal's strengths and buffer against its potential weaknesses.by Owen Lansbury / 20 November 2017 But, Drupal powers over a million websites!
One of the key statistics that Drupalers hold onto is that it's powered over a million websites since mid 2014 when Drupal 7 was in ascendance. However, since Drupal 8 was released in late 2015, Drupal's overall use has stalled at around 1.2m websites, as seen circled in red on the Drupal Core usage statistics graph below.
The main reason for this stall in growth was that Drupal 8 was a major architectural re-write that wasn't essential or even affordable for many Drupal 7 sites to migrate to. For clients considering major new projects, many held off on committing to Drupal 8 until there were more successful case studies in the wild and didn't commission new Drupal 7 sites given that version was nearing a decade old. Anecdotally, 2016 was a tough year for many Drupal firms as they grappled with this pause in adoption.
Of course, Drupal 8 is now a well-proven platform and is experiencing steady uptake as circled in green on the usage graph above. This uptake corresponds with a down tick in Drupal 7 usage, but also indicates a softening of total Drupal usage. If we extrapolate these trend lines in a linear fashion, then we can see that Drupal 8 might surpass Drupal 7 usage around 2023.
Of course, technology adoption doesn't move in a straight line! Disruptive technologies emerge that rapidly change the playing field in a way that often can't be envisaged. The example that springs to mind is Nokia's market share was still growing when the iPhone 4 was released in 2010. By the time the iPhone 4s was released in 2011, Nokia's sales volumes had almost halved, leading to Microsoft's catastrophic purchase of the handset division in 2013 and subsequent re-sale for 5% of the purchase value in 2016. Oops!
Despite this downward trend in overall Drupal usage, we can take comfort that its use on larger scale sites is growing, powering 5.7% of the Top 10,000 websites according to Builtwith.com. However, its market share of the Top 100,000 (4.3%) and Top Million (3%) websites is waning, indicating that other CMS are gaining ground with smaller sites. It's also worth noting that Builtwith only counts ~680,000 Drupal websites, indicating that the other ~500,000 Drupal.org is detecting are likely to be development and staging sites.
So, where are these other sites moving to when they're choosing a new CMS?
Looking at the stats from W3Techs, it's clear to see that Wordpress accounts for almost all of the CMS growth, now sitting at around 30% of total market share.
Wordpress has been able to achieve this dominance by being a fantastic CMS for novice developers and smaller web agencies to build clients' websites with. This is reinforced by Wordpress having an exceptional editor experience and a hugely popular SAAS platform at Wordpress.com.Drupal's place in the CMS market
The challenge Wordpress poses to other open-source CMS platforms, like Joomla, Typo3 and Plone, all with under 1% market share and falling, is their development communities are likely to look direct their efforts to other platforms. Drupal is able to hedge against this threat by having a large and highly engaged community around Drupal 8, but it's now abundantly clear that Drupal can't compete as a platform for building smaller brochure-ware style sites that Wordpress and SAAS CMS like Squarespace are dominating. We're also seeing SAAS platforms like Nationbuilder eat significantly into Drupal's previously strong share of the non-profit sector.
We often talk of Drupal as a CMS Framework, where it competes against frameworks like Ruby on Rails, .NET and Django to build rich web based applications. Drupal 8 is still well placed to serve this sector if the web applications are also relying on large scale content and user management features.
Which brings us to the Enterprise CMS sector, where Drupal competes head to head with proprietary platforms like Adobe Experience Manager, Sitecore and legacy products from Opentext, IBM and Oracle. The good news is that Drupal holds its own in this sector and has gained very strong market share with Government, Higher Education, Media and "Challenger" Enterprise clients.
This "Comfort zone" for Drupal usage is characterised by clients building large scale platforms with huge volumes of content and users, high scalability and integration with myriad third party products. Operationally, these clients often have well established internal web teams and varying degrees of self reliance. They're often using Agile delivery methods and place high value on speed to market and the cost savings associated with open-source software.
Where Drupal is gaining a competitive edge since the release of Drupal 8 is against the large proprietary platforms like Adobe Experience Manager and Sitecore. These companies market a platform of complementary products in a unified stack to their clients through long standing partnerships with major global digital agencies and system integrators. It's no surprise then that Acquia markets their own platform in a similar way to this sector where Drupal serves as the CMS component, complemented by subscription-based tools for content personalisation, customer segmentation and cloud based managed hosting. Acquia have actively courted global digital media agencies with this offering through global partnerships to give Drupal a toe hold in this sector.
This has meant Acquia has made significant headway into larger Enterprise clients through efforts like being recognised as a "Leader" in the Gartner Magic Quadrant for CMS, lending Drupal itself some profile and legitimacy as a result. This has driven Enterprise CIOs, CTOs and CMOs to push their vendors to offer Drupal services, who have looked to smaller Drupal firms to provide expertise where required. This is beneficial to independent Drupal services firms in the short term, but the large digital agencies will quickly internalise these skills if they see a long term market for Drupal with their global clients.
As one of those independent Drupal firms, PreviousNext have staked a bet that not all Enterprise customers will want to move to a monolithic platform where all components are provided by a single vendor's products. We're seeing sophisticated customers wanting to use Drupal 8 as the unifying hub for a range of best-of-breed SAAS platforms and cloud services.
This approach means that Enterprise customers can take advantage of the latest, greatest SAAS platforms whilst retaining control and consistency of their core CMS. It also allows for a high degree of flexibility to rapidly adapt to market changes.What does this all mean for Drupal 8?
The outcome of our research and analysis has led to a few key conclusions about what the future looks like for Drupal 8:
- Drupal's overall market share will steadily fall as smaller sites move to SAAS CMS and self-managed Wordpress installs.
- The "comfort zone" of Government, Media, Higher Education and "Challenger" Enterprise clients will grow as many of these clients upgrade or switch to Drupal 8 from Drupal 7 or proprietary platforms.
- Drupal will gain traction in the larger Enterprise as the global digital agencies and system integrators adopt Drupal 8 as a direct alternative to proprietary CMS products.
- Independent Drupal services firms have a good opportunity to capitalise on these trends through partnerships with larger global agencies and specialisation in technologies that complement Drupal 8 as a CMS.
- A culture of code contribution needs to grow within the larger clients and agencies moving to Drupal to ensure the burden of maintaining Drupal's development isn't shouldered by smaller independent firms and individual developers.
Despite the fact that we've probably already passed "Peak Drupal", we're firm believers that Drupal 8 is the right tool for large scale clients and that community has the cohesion to adapt to these existential challenges!Tagged DrupalSouth
Dated 20 November 2017Add new comment
Read our Roadmap to understand how this work falls into priorities set by the Drupal Association with direction and collaboration from the Board and community.Announcement New issue shortcuts and friendly url structure
Drupal contributors have been managing bug fixes, feature requests, and code reviews on Drupal.org for around 15 years now. Passing an issue node id around a sprint table is a stable of DrupalCon and camps around the world. In October we announced that we would be implementing some changes to the issue url structure, as well as some shortcuts to help users navigate to issues more easily.URL Pattern for issues:
When an issue is moved between projects the alias will be updated.
The search bar will now automatically redirect you to a node if you enter its id directly:
A new menu callback will help you get to issues with a shorter url string:
And of course you can still use the old https://drupal.org/node/<nid> urls if you still have them bookmarked.
Spoiler alert: These shortcuts and new url patterns were deployed in November and you can use them right now!Drupal.org updates Composer instructions on release pages
To make it easier for site builders to figure out how to use a release with composer we've added the composer command line instructions to release pages.
This command installs the package with the current release number specified as a minimum version parameter. We also provide a link to the documentation on using Composer to manage Drupal site dependencies, to help users who may be unfamiliar with Composer learn how to use it.The Community Section
The community is the heart of the Drupal project, but until now community news has not had it's own place to live. We've now made the community page a proper section with its own blog, so that community posts and CWG information has a dedicated place to live.
When the first posts in this new section go live, we'll add this blog feed to Drupal Planet as well. Over time, we hope to further refine the community section and improve the tools we provide for the community to connect with each other.WYSIWYG for Forums (CKEditor)
We're always looking for ways to make improvements to the site that have a high impact to effort ratio. One such change was enabling the CKEditor for editing in the forums. CKEditor has been in the wild as a WYSIWYG editor on Drupal.org for other content types for quite a while now, and we felt confident it was ready for use on forums as well.Bug-fix: Dev releases on project pages
In the runup to DrupalCon Vienna we made a number of improvements to project pages - however a bug or two crept in as well. A race condition was causing dev releases not to display in some cases, and we resolved this issue in October. If you're a project maintainer on Drupal.org and see anything else go missing, please let us know!Infrastructure DrupalCI: Faster, more affordable testing
DrupalCI uses spot requests on Amazon Web Services to spin up testbots on-demand for the Drupal project. In the past, instances were provisioned in minimum increments of one hour, meaning to make the most of testing we had to queue up tests to reuse the remainder of any paid-for instance-hours.
Because AWS has enabled per-second billing, we no longer have to try to fill instance-hours, and so we have reconfigured our spot instance requests to provision testbots faster, while still saving money overall compared to the previous configuration.DrupalCI: More efficient RTBC testing
We also discovered that a bug in our automated RTBC retesting system was triggering more tests than necessary. We've fixed the bug, and now only the most appropriate recent test/environment will be retested for RTBC issues.Server Maintenance Windows
Finally, we scheduled several maintenance windows in cooperation with our infrastructure services partner to schedule updates/restarts of our servers.
https://t.co/57fE1VZHTn db maintenance window is complete. We may schedule a follow up maint window, and will notify here if needed.
— Drupal infra (@drupal_infra) October 31, 2017
As always, we’d like to say thanks to all the volunteers who work with us, and to the Drupal Association Supporters, who made it possible for us to work on these projects. In particular we want to thank:
- Elevated Third - *NEW* Premium Supporting Partner
- Thunder - Renewing Premium Supporting Partner
- EPAM - Renewing Premium Supporting Partner
- CI&T - Renewing Premium Supporting Partner
- Inviqa - Renewing Classic Supporting Partner
- Bellcom - Renewing Classic Supporting Partner
- Osforce - Renewing Classic Supporting Partner
- Faichi Solutions - Renewing Classic Supporting Partner
- Vardot - Renewing Classic Supporting Partner
- SymSoft Solutions - Renewing Classic Supporting Partner
- Forum One - Renewing Classic Supporting Partner
- Catalyst IT - Renewing Classic Supporting Partner
- Duo Consulting - Renewing Classic Supporting Partner
- Mobomo - Renewing Classic Supporting Partner
- CHROMATIC - Renewing Classic Supporting Partner
- New Target - Renewing Classic Supporting Partner
- weKnow - Renewing Classic Supporting Partner
- Davyin Internet Solutions - Renewing Classic Supporting Partner
- Kellton Tech - Renewing Classic Supporting Partner
If you would like to support our work as an individual or an organization, consider becoming a member of the Drupal Association.
Even when salt, shells or stones were used instead of money, the most successful sellers were those relying on marketing and analytics! After, it was always important to find ways to persuade people to buy goods, as well as to figure out which goods were most in demand.Read more