All RPGs and Storygames by Tod Foley are now available at DrivethruRPG and RPGnow. Bring these games to your table!
This is a simple module to log Drupal role changes. All role changes for a user (whether made through the admin UI, Drush/Drupal Console, or programmatically) will be logged with "info" severity to the PSR-3 logging interface (aka "watchdog").
Formatter Suite provides a rich suite of field formatters to help present numbers, dates, times, text, images, and entity references. The included 17 field formatters compliments those available in core.
Acquia Developer Center Blog: Experience Express in Darmstadt: Celebrating Drupal 8's Most Important Release Yet
Though there was no DrupalCon Europe this year, the European Drupal community stepped up and organized their own conference, Drupal Europe, in Darmstadt, Germany last month. An incredibly successful gathering held in the Darmstadtium venue, a beautiful convention center in the center of this college town, Drupal Europe demonstrated the unique power that grassroots initiatives can have in our open-source community.Tags: acquia drupal planet
This module is based on jQuery plugin iPicture to create interactive image walkthroughs. It can overlay tooltips and hints on top of the image, and presents rich content like HTML, photos and videos. It is easy to integrate into your site and can be customized and extended with CSS.
In this article will see how to use the Drupal migration framework to migrate custom sites to drupal 8.
This project is a tool which provides Drush commands to generate Behat tests automatically based on the configuration already created for the site.
This is a quick way to set up tests once functionality has already been implemented.Usage $ drush generate behat-generator-content-test
This module adds a new filter to the Drupal text formats.
This filter enables the user (admin) to strip specified HTML tags from the HTML text that uses this filter.
Nearly 7 million people live in Massachusetts, and millions more visit the state each year. These people come from different backgrounds and interact with the Commonwealth for various reasons.Graphic showing more than 3 million visitors go to Mass.gov each month.
We need to write for everyone while empathizing with each individual. That’s why we write at a 6th grade reading level. Let’s dig into the reasons why.Education isn’t the main factor
The Commonwealth has a high literacy rate and a world-renowned education network. From elementary school to college and beyond, you can get a great education here.
We’re proud of our education environment, but it doesn’t affect our readability standards. Navigating the Women, Infants, and Children (WIC) Nutrition Program might be challenging for everyone.Complexity demands simplicity
People searching for nutrition services are doing so out of necessity. They’re probably frustrated, worried, and scared. That affects how people read and retain information.Learn about our content strategy. Read the 2017 content team review.
This is the case for many other scenarios. Government services can be complicated to navigate. Our job is to simplify language. We get rid of the white noise and focus on essential details.Time is not on our side
You don’t browse Mass.gov in your free time. It’s a resource you use when you have to. Think of it as a speedboat, not a cruise ship. They’ll both get you across the water, just at different speeds.Graphic showing desktop visitors to Mass.gov look at more pages and have longer sessions than mobile and tablet visitors.
Mass.gov visitors on mobile devices spend less time on the site and read fewer pages. The 44% share of mobile and tablet traffic will only increase over time. These visitors need information boiled down to essential details. Simplifying language is key here.Exception to the rule
A 6th-grade reading level doesn’t work all the time. We noticed this when we conducted power-user testing. Lawyers, accountants, and other groups who frequently use Mass.gov were involved in the tests.
These groups want jargon and industry language. It taught us that readability is relative.Where we are today
We use the Flesch-Kincaid model to determine reading level in our dashboards. It accounts for factors like sentence length and the number of syllables in words.
This is a good foundation to ensure we consistently hit the mark. However, time is the most important tool we have. The more content we write, the better we’ll get.
Writing is a skill refined over time, and adjusting writing styles isn’t simple. Even so, we’re making progress. In fact, this post is written at a 6th grade reading level.
Interested in a career in civic tech? Find job openings at Digital Services.
Module were working with the following features:
A variable_set that was configured via a module config page
Ensuring that the module would load the monsido js file and the site embed js in the same group ensuring that they're loaded in the correct order AFTER jquery.
This is not going to be one of those blog posts.
Drupal gives you the ability to re-use fields. If you have an "Image" field, you could choose to use that same field on every content type on your site. However, it's not always clear whether re-using fields is a good idea. Sometimes it is, sometimes it isn't.
Here's an overview of the advantages and disadvantages to consider before re-using Drupal fields.
Now that we have automated our deployment, it wouldn't be too hard to wire it with our code management setup. In this post, we will hook the Ansible scripts with our Git hosting setup so that a deployment gets triggered when you do a "git push". The idea is, deployment shouldn't be a chore, so that developers don't even think of it and only focus on the business logic of their application.
This is a public update on the work of the Governance Task Force.
The Governance Task Force has been working hard to prepare the proposal. We currently have a completed draft that we are actively refining for editorial improvement. As part of the review, we believe it is important to get initial feedback from some key stakeholders to ensure there are no major issues identified. We'll consider making changes to the proposal at our discretion. The proposal will then be delivered to the community and we’re very excited to soon share this. While things may change, we believe we are on time to deliver the proposal before the end of October.
Our team is actively discussing the handoff and next steps that follow from our work. We recognize that there may be ongoing support needed and want to do what we can to help follow-up efforts. It is imperative that momentum is maintained after our proposal is delivered.
We will be recommending a public commentary period before any recommendations move forward for the community to share their thoughts. This commentary period will likely outlast the task force. The task force will officially disband at the end of October, as we have stated in our charter. This does not mean that the work is complete, as there may be discussion and, most importantly, approved recommendations will need support to move forward. The task force wants to do what we can to enable the next steps and we are actively discussing how this might happen, even if we, as individuals, participate without an official charter.
We continue to be committed to serving the community and operating in a transparent way. If you wish to reach us, please fill out this Google form and we will respond as soon as we’re able.
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 Critical security release for the Print module to fix a Remote Code Execution (RCE) vulnerability.
The Print module provides printer-friendly versions of content, including send by e-mail and PDF versions.
The module doesn't sufficiently sanitize the arguments passed to the wkhtmltopdf executable, or HTML passed to dompdf or other PDF generation tools.
See the security advisory for Drupal 7 for more information.
NOTE: This vulnerability has a lower risk in Drupal 6 than in Drupal 7 (where it's Highly Critical). This is because you can't pass shell commands to execute using the HTTP basic auth user/pass, like you can in Drupal 7.
Here you can download the Drupal 6 patch.
If you have a Drupal 6 site using the Print module, we recommend you update immediately! We have already deployed the patch for all of our Drupal 6 Long-Term Support clients. :-)
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 Drupal.org).