Subscribe to feed Planet Drupal - aggregated feeds in category Planet Drupal
Bijgewerkt: 4 uur 53 min geleden

Jeff Geerling's Blog: Composer and Drupal are still strange bedfellows

do, 2017/05/04 - 4:31am

More and more sites are being built in Drupal 8 (over 160,000 as of DrupalCon Baltimore 2017!). As developers determine best practices for Drupal 8 site builds and deployment, they need to come to terms with Composer. In one of the most visible signs that Drupal is 'off the island', many modules are now requiring developers to have at least a fundamental grasp of Composer and dependency management.

But even more than that, many developers now use Composer in place of manual dependency management or a simpler tools like Drush Make files.

With these major changes comes some growing pains. Seeing these pains on a daily basis, I wrote Tips for Managing Drupal 8 projects with Composer to highlight some best practices and tricks for making Composer more powerful and helpful.

But many developers still wrestle with Composer, and mourn the fact that deployments aren't as simple as dragging zip files and tarballs around between servers, or checking everything into a Git repository and doing a git push. For example:

  • If I manage my codebase with Composer and follow Composer's own recommendation—don't commit dependencies in my vendor directory, what's the best way to actually deploy my codebase? Should I run composer install on my production web server? What about shared hosting where I might not have command line access at all?
  • Many modules (like Webform) require dependencies to be installed in a libraries folder in the docroot. How can I add front end dependencies via Composer in custom locations outside of the vendor directory?

And on and on.

Over 3,000 community members attended DrupalCon Baltimore 2017.
(Photo by Michael Cannon)

During a BoF I led at DrupalCon Baltimore 2017 (Managing Drupal sites with Composer), we identified over 20 common pain points people are having with Composer, and for many of them, we discussed ways to overcome the problems. However, there are still a few open questions, or problems which could be solved in a number of different ways (some better than others).

I've taken all my notes from the BoF, and organized them into a series of problems (questions) and answers below. Please leave follow-up comments below this post if you have any other thoughts or ideas, or if something is not clear yet!

Categorieën: Drupal 6 security update for Remember Me

wo, 2017/05/03 - 10:10pm

As you may know, Drupal 6 has reached End-of-Life (EOL) which means the Drupal Security Team is no longer doing Security Advisories or working on security patches for Drupal 6 core or contrib modules - but the Drupal 6 LTS vendors are and we're one of them!

Today, there is a Moderately Critical security release for the Remember Me module.

Remember Me adds a "Remember me" checkbox to the login form.

It had a bug where it would override the session cookie lifetime, regardless of whether the user checked "Remember me" or not. This could affect applications that set the session cookie lifetime to a very short value, like banking websites.

(A note about the timing of this release: The Drupal 7 fix was released on April 23rd, however, we don't have any customers who depend on this module. So, it falls outside of the set of modules that we usually release security patches for on the same day they are released. But this is a module we like, so we decided to port the fix! :-))

Here you can download the Drupal 6 patch.

If you have a Drupal 6 site using the Remember Me module, we recommend you update immediately!

If you'd like all your Drupal 6 modules to receive security updates and have the fixes deployed the same day they're released, please check out our D6LTS plans.

Note: if you use the myDropWizard module (totally free!), you'll be alerted to these and any future security updates, and will be able to use drush to install them (even though they won't necessarily have a release on


OpenLucius: Drupal 8 development: non-content | Part 1/3: Backend configuration form

wo, 2017/05/03 - 7:20pm

Within a Drupal 8 website, there are usually a number of texts that the content manager must be able to manage but that are not real content items.

We resolve this by making a user-friendly configuration form in the backend of Drupal 8, accessible to content managers. This allows us to make sure that all non-content is easy to manage, so that content managers do not have to dig through all kinds of screens in a technical backend to find the correct settings.


Acquia Developer Center Blog: Contribution Stories: Beyond Websites - Using Drupal for Digital Signs

wo, 2017/05/03 - 6:53pm

Using Drupal 8 to power real-time signage systems. Drupal gets better when companies, organizations, and individuals build or fix something they need and then share it with the rest of us. Our community becomes better, stronger, and smarter when others take it upon themselves to make a positive difference contributing their knowledge, time, and energy to Drupal. Acquia is proud to play a part, alongside thousands of others, in making tomorrow’s Drupal better than today’s. One of them is Adam Weingarten and Mike Madison’s.

Tags: acquia drupal planet

Acquia Lightning Blog: Lightning's Oxford Comma Helper

wo, 2017/05/03 - 4:58pm
Lightning's Oxford Comma Helper phenaproxima Wed, 05/03/2017 - 10:58

(This was originally posted on Medium, and re-posted here by the author.)

I added a useful function to the Lightning distribution of Drupal 8! Its purpose is to apply the Oxford comma (with the final conjunction) to an array of strings, returning a single nicely formatted string.

I did this because I don’t enjoy seeing this kind of thing littered throughout Drupal:

The following file types are accepted: gif png jpg txt pdf doc

It gets the point across, and clearly, but it feels so…careless to me. A little polish wouldn’t hurt. Now, if you’re using Lightning, you can generate the string like so:

use Drupal\lightning_core\Element; echo 'The following file types are accepted: ' . Element::oxford(['gif', 'png', 'jpg', 'txt', 'pdf', 'doc']);

This will produce “The following file types are accepted: gif, png, jpg, txt, pdf, and doc”. Much nicer! In fact, this opens the door to smoother phrasing in general:

Element::oxford(['gif', 'png', 'jpg']) . ' files are acceptable.';

This will produce the even nicer “gif, jpg, and png files are acceptable.” Yowza!

Element::oxford() will default to using ‘and’ as the final conjunction, but you can override that:

Element::oxford(['apples', 'oranges', 'mangoes'], 'or');

This will produce “apples, oranges, or mangoes”.

The function is smart enough to not apply the Oxford comma if there are fewer than three items. So this:

Element::oxford(['foo', 'bar']);

...will produce “foo and bar”.

I think you get the idea. Go forth, Lightning users, and generate smoother, more grammatically correct lists of items!


BlackMesh: One more down: DrupalCon Baltimore

wo, 2017/05/03 - 3:24pm

This past week, Baltimore definitely earned its nickname – “Charm City.”

That’s because I just got back from there after attending my fifth North American DrupalCon with the BlackMesh team. We had an amazing week full of productive talks, seeing old friends, and making new ones.

The BlackMesh team went into this conference with focus on our government and security services. However, with the wide range of diverse attendees, I was surprised to find myself having great conversations about the services we provide in healthcare, education, and finance markets as well.

Aside from meeting new people, it was great having a lot of our current clients stop by the BlackMesh booth to say hi and talk shop – it was great to see you all again!

Speaking of customers, we were thrilled that our very own Ron Johnson, BlackMesh Sales Engineer, had the opportunity to discuss the work we’ve done with the Sierra Club migrating their Drupal 7 site from a Windows-based platform to a fully managed cloud solution. If you missed it, you can check out the presentation here.

Our president, Eric Mandel, attended this year’s Government Summit. It was a day dedicated to panel discussions, break-out sessions, and case studies pertaining to Drupal initiatives for city, state, and federal governments. Eric shared with me some key takeaways from the summit:

  1. Drupal 8 is definitely ready for government sites. In fact, the platform is already being used for a number of sites at varying levels of government.
  2. Security, compliance, and accessibility are major concerns for government site deployments. While security and compliance have been a priority for quite a while, accessibility is a more recent area of focus for developing government sites.
  3. The multisite capabilities and accessibility improvements offered by Drupal 8 are perfect fits when it comes to meeting the needs of local and federal government agencies.

Thank you to everyone who attended, and particularly those of you who stopped by our booth. It was great to have attendees – particularly first time DrupalCon-ers – come up to our booth because they’ve heard about our work in the Drupal community. It’s a great feeling, and we can’t help but wonder if seeing attendees wearing BlackMesh shirts from previous DrupalCons sparked their interest in us (our t-shirts are a real crowd-pleaser every year)!

DrupalCon is one of our most meaningful and constructive events of the year. Introducing more of the Drupal Community to the BlackMesh brand entails hard work, but is a lot of fun. The Drupal Association does a great job of getting everyone involved in the event and pulling in more resources from different industries. For that, we’re very appreciative and are already looking forward to the next conference.

We’ll see you at the next DrupalCon!

DrupalCon BaltimoreDrupalGovernment

Valuebound: Configuration Management in Drupal 8 VS Drupal 7

wo, 2017/05/03 - 3:00pm

In drupal whenever you are making changes in settings configuration changes are made .For example if we enable a permission then its a configuration change.


Tim Millwood: Enforce SSL in Drupal 8 using a redirect

wo, 2017/05/03 - 12:40pm
Enforce SSL in Drupal 8 using a redirect timmillwood Wed, 03/05/2017 - 11:40

Place this code within .htaccess underneath `RewriteEngine on`.

RewriteCond %{HTTPS} off
RewriteCond %{HTTP:X-Forwarded-Proto} !https
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

Tags drupal-planet drupal drupal 8 ssl Add new comment