Drupal Planet

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

Hook 42: Node.js version control in Drupal themes

Mon, 2016-07-18 12:44

It is important that for any given project, each developer uses the same version of Node.js and related Javascript (JS) packages. In this article, we’ll discuss how to use “Node Version Manager” (NVM) to install multiple versions of Node.js, how to use “Automatic Version Switching for Node.js” (AVN) to automatically switch Node.js versions when changing to a project directory, and how to use “Node Package Manager” (NPM) to keep track of JS packages.

Categories: Drupal

FFW Agency: The ABC's of Drupal: Component, Composer, Console

Mon, 2016-07-18 11:15
The ABC's of Drupal: Component, Composer, Console Ray Saltini Mon, 07/18/2016 - 18:15

When we said we'd introduce you to the ABC's of Drupal we didn't just mean the easy stuff. Here are three C's that will help you understand the power behind Drupal 8.

Component: In Drupal 8 the word component is often used to identify one of the libraries managed by the Symfony project used by Drupal. Visit this link for a full list. https://ffwagency.com/blog/what-symfony-components-are-going-into-drupal-8 While Twig is often cited as a Symfony component, strictly speaking it is a PHP theming engine created by the same individuals who founded and maintain the Symfony project.

Composer: Composer is a dependency manager tool for PHP, Drupal’s core scripting language. If you are familiar with a package manager it is similar but not the same. Practically speaking Composer will help you download, install and manage specific code libraries and any additional code libraries they in turn may be dependent on for a given project. It’s important to understand that Composer is project centric - it defaults to managing code and dependencies within projects (like websites) rather than globally across projects. Composer’s use in the Drupal space is growing with the adoption of Drupal 8 and has begun to be used as an alternative to .make files which have been used to help manage Drupal installs and distributions.

Console: Console is a component of the Symfony project. Most often when a Drupal developer refers to using Console they are talking about using Drupal Console, a suite of tools run from a command line interface (CLI) to generate boilerplate code and interact with a Drupal 8 installation. In 2014 FFW hired Drupal Console’s lead project developer Jesus Olivas to develop the project and contribute the tool back to the Drupal community to strengthen Drupal 8 adoption. Drupal Console is used as a learning tool, module and theming scaffolding, debugger and configuration tool for Drupal 8. For more information on Drupal console visit https://ffwagency.com/blog/drupal-console-an-overview-of-new-drupal-cli

Tagged with Comments
Categories: Drupal

Appnovation Technologies: Giving Back with Drupal: Isa Mundo Foundation

Mon, 2016-07-18 10:44
Drupal is used by nonprofits around the world because it provides a low-cost, flexible and scalable platform for any kind of organization.
Categories: Drupal

Jeff Geerling's Blog: Migrating Link fields with multiple properties with Drupal 8

Mon, 2016-07-18 10:11

Today I needed to migrate a URL/Link into a Drupal 8 site, and I was scratching my head over how to migrate it so there were distinct values for the URL (the actual link) and the Label (the 'title' that displays to end users and is clickable). Drupal 8's Link field type allows you to set a URL in addition to an optional (or required) label, but by default, if you just migrate the URL, the label will be blank.

I first set up the migration config like so:

  field_url: source_url

And source_url was defined in the migration's source.fields configuration.

In my case, the source data didn't have a label, but I wanted to set a default label so the Drupal 8 site could display that as the clickable link (instead of an ugly long URL). To do that, it's similar to migrating a formatted text field, where you can migrate individual components of the field using the syntax [field_name]/[component]. In a Link field's case, it looks like:

Categories: Drupal

Ben's SEO Blog: 8 Ways Drupal 8 Can Improve Your Website and Generate More Leads

Mon, 2016-07-18 09:00

Drupal 8 is a marketer’s dream. With the new core enhancements, you can execute more effective marketing campaigns because you can deliver personalized content segmented by audience, language, and device type. You can develop relevant content that improves SEO, drives users to your website, creates leads, and results in more sales.

Drupal draws on the innovation of thousands of developers, designers, and marketers who contribute to the open-source platform. The result is that cutting-edge, marketing functionality is now included in the core of Drupal 8.

1.  Mobile For Your Customers; Mobile for You

Most platforms today offer some form of mobile responsiveness. While this was an add-on for Drupal 7, it’s now built into Drupal 8’s core functionality. Mobile-responsiveness is critical for Google rankings and it’s key to marketing success. We’ve seen it coming. As more and more people began to use smartphones for everything in their personal lives, it was inevitable that it would drive mobile usage in the business world as well. While consumer marketing was at the forefront of mobile marketing, B2B mobile marketing has expanded as well. Google reports 300% growth in B2B queries in just two years. Mobile isn’t a trend anymore; it’s a necessity.

The newest version of Drupal takes mobility seriously. All of Drupal 8’s built-in themes are mobile-responsive. Web services are built into the core of Drupal 8, allowing content to be accessed from any device such as Amazon’s Alexa. Now that Apple has opened Siri to third party developers, it is only a matter of time before Drupal will be powering Siri’s voice-based interactions.

And mobile is not just for your website visitors. Drupal has taken the next step and optimized website administration for mobile. You can administrate, create and publish content, approve editorial changes, clear caches, or any other admin task all on your mobile device.

2. The Path From Everyone to Each One--Personalized Content is Now in Drupal 8

Personalized content is needed to be competitive and Drupal 8 provides tools to help you achieve it. Customers are coming to expect streamlined, end-to-end, digital experiences and the companies who fail to provide this are increasingly at a competitive disadvantage. While nearly all marketers see the need for personalization, getting there is another story. Only 4% of marketers consider their web site to be very personalized and most of them don’t know how to achieve it. Often, technology can be a roadblock to achieving higher levels of engagement at every customer touch point.

Drupal 8 can help you quickly deploy various types of digital content and campaigns that span multiple segments and channels. It allows you to define customer segments, create custom content and deliver it in real-time on any device.

3. Speed Matters. Stay in Front of the Race

According to the Aberdeen Group, customers are won or lost in one second. Nearly half of web users expect a site to load in 2 seconds or less and they tend to abandon a site that isn’t loaded within 3 seconds. This means if your website is slow, you’re losing conversions from visitors on your site. A second delay in page response can result in a 7% reduction in conversions. The fact is, faster pages make more money.

The speed of your page loading matters to the user and that means it matters for SEO as well. Google uses page load time as one factor to determine rankings, so optimizing your page load time is important. This will give your website an extra edge on the competition and a boost in rankings.

Drupal 8 has features that make your websites faster without the need for a lot of technical expertise. Drupal 8 uses “cache tags” that makes caching more efficient and includes Cache Context API which provides context-based caching. This means pages load faster while ensuring that visitors always see the latest version of your site.

Also built into Drupal core is the BigPipe module. This new feature in Drupal 8 helps you deliver personalized content with the fastest page load time possible. BigPipe determines what parts of your web page are static and sends that instantaneously. The dynamic portion of your page--the parts that are personalized--are sent next. The net result is a much faster experience for your website visitors.

4. Need Multiple Languages? No Problema

Global business has become a strong driver in many companies’ revenue growth. Much of the economic growth is happening in countries like China and India, who have growing middle classes, meaning that if you want to take advantage of the global economy, you need to market to these countries as well. And it’s not just mega companies going overseas; 97% of U.S. exporters of goods are small businesses. The Internet has been the driver in opening up these global markets for goods and services. Through the Internet, even small businesses can target individual consumers in countries around the world. Companies that deliver web-based products and services tend to experience turbocharged global growth.

But all of this increases the complexity of your business: now you must deal with different languages, different customs and different distribution channels. In order to grow successfully, marketing teams must learn to tackle the global marketplace. They need to put the customer first no matter where that customer is located. Serving them well enables you to attract customers in other markets and turn them into referrals.

Drupal 8 has stepped up to the challenge of supporting a global presence. While many users face difficulty with languages and translations in Drupal 7, multilingual support is a part of the Drupal 8 core. With this version of Drupal, you are able to integrate a language much more easily and create territory-specific content. Not only can you change the back-end administration into another language, you can use Drupal’s language translator to translate links, pages and titles. When users visit your website they can select a language from those that you chose to provide. !Qué bueno!

5. Simplified Content Creation and Management

As digital content has gained massive importance in most businesses, the ability to easily create and manage content has become more important as well. IT resources are limited in any company and they need to be used wisely. The sooner you can put new content into place, the sooner you can react to changes or problems and the faster you can put new leads into your system.

One of the most exciting improvements in Drupal 8 is the addition of a WYSIWYG editor. With its drag-and-drop interface, you can edit content directly on the page rather than navigating to another. There are many options for image size, shape and alignment. You can also see how those images will look on a mobile device.

Many of the popular Drupal add-on modules have been included in the Drupal 8 core, meaning that less work and customization is needed to get the website you desire. Some of the modules new to Drupal core are Views, Block, and Context. One of the most exciting additions to Drupal 8 core is the Views module which provides great flexibility by enabling you to display any content in whatever format you require.

In addition to simplified content creation, Drupal 8 offers simplified management. You are able to monitor your website and your campaigns on your smartphone. When you are able to track your campaigns and see what is trending from content, social, and email efforts, anywhere and anytime, you can react quickly to market trends and customer requests.

6. Integrate, Don’t Re-create Data

Have you ever lost leads in the cracks between your various software systems? Drupal 8 integrates with email, analytics, marketing automation, CRM and other business software to create a seamless transition from content to lead generation to sale.

Drupal 8 offers a big upgrade in usability and often requires less technical understanding to complete integrations with third party systems. Marketers can frequently achieve integrations using community-built modules without coding knowledge.

7. Drupal 8: Proven and Tested  by Thousands

As with any software update, you want to know that the software has been well-tested and proven to work. In fact, tens of thousands of organizations are using Drupal 8 after less than a year on the market. Drupal 8 has more than 75,000 installations since its release in November. At this rate, it is being adopted twice as fast as the popular Drupal 7.

Memorial Sloan Kettering Cancer Center (MSK) used Drupal 8 beta version to launch its new website, mskcc.org in May, 2015, even when the software was still in its beta phase. Learn about other companies who use Drupal 8 at https://www.drupal.com/showcases.

8. SEO that is Sophisticated and Powerful

Drupal has always been one of the best content management systems for effective SEO results.  Drupal’s Taxonomy system automatically creates a page for tags that are optimized for search engines by adding the page to the XML Sitemap and updating it when changes are made. The updated XML sitemap can help search engines find the new content.

With its mobile-responsiveness and speed, Drupal 8 should provide even more assistance in achieving top Google rankings. There have always been a wide range of Drupal SEO modules that can further enhance your SEO efforts.. For Drupal 8, many of these SEO modules are still in testing.

Upgrading to Drupal 8 could create issues for your Google rankings if you don’t plan carefully. Taking SEO into account before the migration can save money. In a migration plan, all the web site’s current content and digital assets should be inventoried and a matrix of old to new should be created. Naming conventions for categories, link URLs, and anchor text should be considered and 301 redirects put in place if needed.

If you don’t have in-house staff to manage the process, you may want to consider hiring an experienced Drupal SEO expert. There is no avoiding an effect in search visibility 100%, however, if the SEO expert is involved from the start, key insights can be incorporated into the overall process, mitigating ill effects such as short term costs for redeveloping CMS and long term effects from uncrawlable content, lost links and lost traffic.

Ready to Make the Switch to Drupal 8?

If you are ready to migrate to Drupal 8, Volacci can provide a Drupal SEO migration audit so that you can make the switch with confidence. Give us a call at (512) 989-2945.

drupal marketing, drupal seo, Planet Drupal, drupal 8
Categories: Drupal

Acquia Developer Center Blog: Drupal 8 Module of the Week: Permissions by Term

Mon, 2016-07-18 08:20

Each day, between migrations and new projects, more and more features are becoming available for Drupal 8, the Drupal community’s latest major release. In this series, the Acquia Developer Center is profiling some prominent, useful, and interesting projects available for Drupal 8--modules, themes, distros, and more! This week: Permissions by Term.

Tags: acquia drupal planetaccess controlgroupogorganic groups
Categories: Drupal

OSTraining: How to Install Drupal 7 Using Bitnami for Windows

Mon, 2016-07-18 07:05

Bitnami is a software that allows you to install website applications such as Joomla, WordPress and of course Drupal 7.

In this tutorial we will show you how to install Bitnami on Windows to create a Drupal 7 site.

Categories: Drupal

Drupal Blog: Drupal 8.1.7 released

Mon, 2016-07-18 07:00

Drupal 8.1.7, a maintenance release which contains fixes for security vulnerabilities, is now available for download.

See the Drupal 8.1.7 release notes for further information.

Download Drupal 8.1.7

Upgrading your existing Drupal 8 sites is strongly recommended. There are no new features nor non-security-related bug fixes in this release. For more information about the Drupal 8.1.x release series, consult the Drupal 8 overview.

Security information

We have a security announcement mailing list and a history of all security advisories, as well as an RSS feed with the most recent security advisories. We strongly advise Drupal administrators to sign up for the list.

Drupal 8 includes the built-in Update Manager module, which informs you about important updates to your modules and themes.

Bug reports

Drupal 8.1.x is actively maintained, so more maintenance releases will be made available, according to our monthly release cycle.

Change log

Drupal 8.1.7 is a security release only. For more details, see the 8.1.7 release notes. A complete list of all changes in the stable 8.1.x branch can be found in the git commit log.

Security vulnerabilities

Drupal 8.1.7 was released in response to the discovery of security vulnerabilities. Details can be found in the official security advisories:

To fix the security problem, please upgrade to Drupal 8.1.7.

Update notes

See the 8.1.7 release notes for details on important changes in this release.

Known issues

See the 8.1.7 release notes for known issues.

Categories: Drupal

Drupal.org frontpage posts for the Drupal planet: Drupal Core - Highly Critical - Injection - SA-CORE-2016-003

Mon, 2016-07-18 06:53

Drupal 8 uses the third-party PHP library Guzzle for making server-side HTTP requests. An attacker can provide a proxy server that Guzzle will use. The details of this are explained at https://httpoxy.org/.

CVE identifier(s) issued
  • CVE-2016-5385
Versions affected
  • Drupal core 8.x versions prior to 8.1.7

Install the latest version:

  • If you use Drupal 8.x, upgrade to Drupal core 8.1.7
  • If you use Drupal 7.x, Drupal core is not affected. However you should consider using the mitigation steps at https://httpoxy.org/ since you might have modules or other software on your server affected by this issue. For example, sites using Apache can add the following code to .htaccess:
    <IfModule mod_headers.c> RequestHeader unset Proxy </IfModule>

We also suggest mitigating it as described here: https://httpoxy.org/

Also see the Drupal core project page.

What if I am running Drupal core 8.0.x?

Drupal core 8.0.x is no longer supported. Update to 8.1.7 to get the latest security and bug fixes.

Why is this being released Monday rather than Wednesday?

The Drupal Security Team usually releases Security Advisories on Wednesdays. However, this vulnerability affects more than Drupal, and the authors of Guzzle and reporters of the issue coordinated to make it public Monday. Therefore, we are issuing a core release to update to the secure version of Guzzle today.

Contact and More Information

The Drupal security team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact.

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

Front page news: Planet DrupalDrupal version: Drupal 8.x
Categories: Drupal

Drupal core announcements: Drupal 8.x core release on Monday, July 18 (update to previously scheduled window)

Sun, 2016-07-17 10:28

The Drupal core security release window has been moved to Monday, July 18. See the PSA announcement for the release for details.

Categories: Drupal

David Lohmeyer's Blog: Scaling block output as Twig variables in Drupal 8

Sat, 2016-07-16 14:30

With Drupal 8's Object Oriented focus, it's just a matter of time before cooler approaches to the theme's giant template.php (now yourtheme.theme) file are found. I've written a nicer way to get block output into the $variables array in page and node preprocess functions. What this allows you to do is use simple variables like {{ my_cool_block_stuff }} in yor Drupal Twig templates.

Categories: Drupal

Wuinfo: Have hundreds of items in one multivalued field?

Fri, 2016-07-15 18:29

Sounds like a bad design? When the first time I found out this, I thought that should have avoided it in design. But, that is not what we are talking today. After we I figured out a way to fix the performance, it seems quite a powerful way to deal with the business logic.

How to accommodate the request that a node holds thousands of multiple value items in one field? When it comes to editor experience, we have something to share. Multiple values field for a field-collection-item is a usual setup for a content type. When there are only couple dozens of values, everything is good. The default field-collection embed widget with a multivalue field is working well.

As the number of items goes up, the editing page become heavier. In our case, we have a field collection contains five subfields. There is one entity reference field pointing to nodes, two text fields, one taxonomy entity reference field and a number field. Some nodes have over 300 such field collection items. The editing pages for those nodes are like taking forever to load. Updating the node getting more and more difficult.

for such a node, the edit form has thousands of form elements. It is like loading an adult elephant with a small pickup truck. Anything can slow down the page. That can be from web server performance to the network bandwidth and our local computer browser capability. So, we need to find a valid way to handle it. We want the multiple value field to be truly unlimited. Make it capable of holding thousands of field-collection-items value in a single node.

After doing some research, we come with a pretty good solution. Here is what we had done to deal with it.

We use Embeded Views Field to build a block for the field collection items. We paginate it and break down 300 items into 12 pages. Then, we insert the views block into the node editing page. Not loading all the elements into the node editing form, it speeds up the page loading immediately. Display the field collection items in views block is not enough, we need to edit them. I had tried to use the VBO to handle editing and deleting. It did not work. Then we built some custom ajax functions for editing and deleting. We use the ctools modal window as front end interface to edit, delete and add new items. That works well. With modal window and Ajax, we can keep the main node edit page untouched. There is no need to refresh the page every time they change the field-collection-items. Thanks to the pagination of the views block. We now can add as many items as we want into the field collection multivalue field. We added views sorting function to the embedded views field.

Sounds pretty robust, but wait, there is something missing. We quickly running into problem soon we implement it. What about the form to create a new node? On the new node page, the embedded views field block is not working. A new node does not have its node id. We fixed it by using the default widget. It is just for the new node page. We used the following function to switch the field widget.

function MODULENAME_field_widget_properties_alter(&$widget, $context) {
  if ($context['entity_type'] == 'node') {
    if (!isset($context['entity']->nid)) {
      if ($context['field']['field_name'] == 'FIELD_MACHINE_NAME') {
        if ($widget['type'] == 'field_collection_hidden') {
          $widget['type'] = 'field_collection_embed';
Categories: Drupal

Sooper Drupal Themes: Glazed 2.5.0 – Massive Release, Powerful New Design Tools

Fri, 2016-07-15 11:51

New Typography Controls, New Layout Capabilities, Drupal Block Design, and much more!

Today after about a month of coffee-infused delays I'm happy to announce Glazed 2.5.0. and Carbide Builder 1.0.11. Our framework theme has just become massively more powerful, with design tools that help you create any design imagineable the hassle of writing and testing code. While on the surface...

Categories: Drupal

The Sego Blog: Drupal 8, Pantheon & GitKraken: Part 3 of 3

Fri, 2016-07-15 11:51
07/15/2016Drupal 8, Pantheon & GitKraken: Part 3 of 3

Welcome to the third and final installment of our three part Drupal 8, Pantheon & GitKraken series.

Categories: Drupal

Drupal core announcements: Drupal core security release window on Wednesday, July 20, 2016

Fri, 2016-07-15 09:52
Start:  2016-07-20 11:00 - 12:00 America/Chicago Organizers:  xjm catch David_Rothstein stefan.r mlhess Event type:  Online meeting (eg. IRC meeting)

The monthly security release window for Drupal 8 and 7 core will take place on Wednesday, July 20.

This does not mean that a Drupal core security release will necessarily take place on that date for any of the Drupal 8 or 7 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).

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, August 03. The next scheduled minor (feature) release for Drupal 8 will be on Wednesday, October 5.

Drupal 6 is end-of-life and will not receive further security releases.

For more information on Drupal core release windows, see the documentation on release timing and security releases, and the discussion that led to this policy being implemented

Categories: Drupal

Drupal @ Penn State: Special Menu Items and Breadcrumbs

Fri, 2016-07-15 09:16

If you are using the Special Menu Items module to add things like HRs and unlinked titles to your menus, you might run into the Breadcrumb issue.

If you have a non-linked menu item it may show up on your breadcrumbs as a plain text title which you may not want to see. There are a number of issues for this in the modules queue, but as far as I can tell it has not been fixed.

My quick fix is a function in template.php

Categories: Drupal

Janez Urevc: Sam Morenson is thinking about media in Drupal core

Fri, 2016-07-15 08:34
Sam Morenson is thinking about media in Drupal core slashrsm Fri, 15.07.2016 - 17:34

My friend and a long time member of the Drupal media team has published a blog post where he thinks about media in Drupal core and possible ways forward.

I am very happy to see mature debate evolving in this area. We need more of that!

Categories: Drupal

Drupal.org blog: What’s new on Drupal.org? - June 2016

Fri, 2016-07-15 08:20

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.

In June the Drupal Association had our annual staff retreat, where the remote team members joined the Portland, OR team for a three day retreat. This year's retreat was particularly important as we found our feet as a smaller, leaner team, and focused on our organizational roadmap for the next twelve months.

For the engineering team in particular, our focus will be on maintaining the critical systems that make project successful: issue queues, updates, testing, packaging, etc, while at the same time finding new ways to support and enable Drupal's evolution.

These were some heady days, but even as we worked through the best ways to continue serving the Drupal community on a strategic level in June, we also found the time to keep making Drupal.org a better home.

Drupal.org updates Documentation Migration

A long running initiative this year has been the creation of a new Documentation system for Drupal.org, a topic we've touched on in many prior updates as it has begun to come online. We are very happy to say that we are moving to the next stage of the documentation project: moving from development to migration.

In June tvn recruited several volunteers to join our documentation migration team, and to become some of the first maintainers for the new Documentation Guides. General documentation, such as Understanding Drupal, Structure Guide, etc. will be migrated first. Documentation for contributed projects will follow in the coming weeks.

Maintainers of contributed projects, who currently have their documentation on Drupal.org, will be added as maintainers to respective documentation guides and are encouraged to clean/tidy up their documentation post-migration.

if you are interested in helping, or sign up as a maintainer for some of the new documentation guides.

Composer Repositories are now in Beta

Drupal.org's Composer repositories allow developers building sites with Drupal to use the Composer command line tool for dependency management. In June we collected feedback from a variety of users, as well as the community volunteers who assisted us with the Composer Community Initiative.

We spent the month iterating quickly on the alpha implementation: fixing bugs and rebuilding the meta data to ensure that users get consistent and expected results. Because of those fixes, and after gathering yet more feedback from the community, we were able to move the Drupal.org Composer repositories to beta.

We encourage you to begin transitioning your composer based workflows to use Drupal.org's composer facade. Package names are stable, and downtimes will be planned and announced. For more information on how to use Drupal.org's Composer repositories, read our documentation.

Better issue credit tools for maintainers

The Drupal.org issue credit system is a unique innovation of our community. By allowing users to attribute their contributions as volunteers, to their employers, or to client customers, we have an insight into the contribution ecosystem for Drupal that is unparalleled among open source projects. We've also already seen the impact of incentivizing organizations to give back to Drupal, by using the credit system as the basis for organization rankings in the marketplace.

In June we added two new tools for maintainers to improve how they grant credit to users. Firstly, maintainers can now deselect the automatic credit attribution for users who have submitted patches. This change was important to prevent gaming the credit system. Secondly, we've given the maintainers the ability to credit users who have not commented in the issue. Whether that help was provided in IRC, Slack, on a video call, or in a sprint room, maintainers can now ensure that those users who helped resolve an issue receive credit for their contributions. Any user who is credited this way can edit their credit attribution if they want to extend that attribution to a supporting organization or customer.

Friendly path aliases for release nodes

We also made a relatively small change that will have a big impact. Path auto is now enabled for project releases, so you for any project a specific release can now be found at:
And you can also find a list of all the releases for a project at:

Take, for example, the Token module:

You can find the complete index of releases for this project at: https://www.drupal.org/project/token/releases and individual releases now have friendly urls, like this one: https://www.drupal.org/project/token/releases/8.x-1.0-alpha2

Spam Fighting Improvements

Fighting spam on Drupal.org is a never ending battle, but in June we deployed a refinement to our spam fighting tools that helps us to find patterns in registration behavior and prevent spam registrations before they've even started. After flipping on our latest iteration of this spam fighting tool we saw an immediate and dramatic drop-off in suspicious account registrations. With the additional data we've been able to collect we already see ways to improve this even further, so we hope to continue make Drupal.org a cleaner home for the community.

Highlighting Supporting Technologies

Drupal is many things to many different people, but one central function of Drupal is to be the hub of interconnected and complementary technologies. Several of the companies that build these technologies have chosen to support the Drupal project by becoming supporters. To better highlight some of these supporting technologies that work well with Drupal, we've added a supporting technologies listing to the marketplace.

Sustaining support and maintenance DrupalCon

DrupalCon Dublin is coming up soon, from September 26 - 30th. This year we smashed all our previous records for session submissions, and the caliber of speakers and topics is higher than ever before.

In June we opened registration for the event. We encourage you to buy your tickets now! Early bird registration will end soon.


Infrastructure is the bedrock of Drupal.org - and we're continuing to tune the infrastructure for efficiency, economy, and performance. Alongside the launch of registration for DrupalCon Dublin, we implemented APDQC to improve the performance of the Events website under heavy load.

We've also been upgrading our configuration management from Puppet 3 to Puppet 4, and continuing to standardize our configuration across all of our environments to make our infrastructure durable, consistent, and portable.


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.

If you would like to support our work as an individual or an organization, consider becoming a member of the Drupal Association.

Follow us on Twitter for regular updates: @drupal_org, @drupal_infra

Categories: Drupal

InternetDevels: The BigPipe Drupal 8 module for your website performance optimization

Fri, 2016-07-15 06:46

We once told you about some great new features of Drupal 8
(in part 1 and part 2). Now it’s time to have a closer look at one
of the most exciting innovations for Drupal 8: the BigPipe Module.

Read more
Categories: Drupal

Zivtech: Foster a Culture of Training

Fri, 2016-07-15 06:00
What Are Your Values? What really matters? People. I see our staff get married, have children, buy houses, enjoy their lives, their coworkers, and their working environment, and I know that I was part of that. They also created our value.
What You Gain Early on we adopted this idea that we were going to train up our people, and that we weren't going to just expect them to come in all ready to go. We were going to bring people in at all different levels including having no experience at all. Over the years we found that we gained a lot from doing that, so we have much better employee retention than most of our peers. A lot of our people have been here almost since our start.

Our team is very close, and communicates very well. Think of a team as neurons in your brain. The more connections that they have, the better they communicate, the stronger the team.

They are harmonious because they've all been trained in the same way. We don't have a lot of strong conflicts about how we do things. All of our projects are done in the same way.

We're not undoing old opinions, and we also have a lot of generosity towards each other. People give you retention, loyalty, and generosity because you gave them something. You took a chance on them when they didn't have a lot of opportunities, and you invested a lot in them. We also have a lot of developers with other strengths. They are more well-rounded. Our staff includes people with many outside skills, including musicians, artists, writers, and polyglots. Their diverse cognitive frameworks help solve problems creatively.

In a culture of training, everyone values the idea of working together to teach each other. That extends not just to our own team, but to how we interact with our clients. Ultimately I find that clients often value being taught more than they value the end product.

We have this whole team of great communicators who value teaching. Whether they're the project manager, the developer, or the QA person, they're always finding that chance to teach the client something.

Download the full Grow Your Own white paper for free.
Categories: Drupal

Powered By