All RPGs and Storygames by Tod Foley are now available at DrivethruRPG and RPGnow. Bring these games to your table!
Jacob Rockowitz: Webform 8.x-5.x-beta14: Ajaxifying Webforms and Improving User Submission Management
Webform 8.x-5.x-beta14 has become a significant release because it addresses several important features and milestones listed on the Webform roadmap, including support for multiple drafts, Ajax-enhancing submission forms and the administrative UI.
Before I start to "show-n-telling" you about these cool new features, wanted to announce that I am targeting monthly releases and explain my goals for each release of the Webform module.
Initially,I was reluctant to publically commit to regular releases for software that I am maintaining for free. Turns out my public commitment is a good thing. Targeting regular releases motivates me to organize the Webform's roadmap and issue queue while iteratively working on fixing bugs and adding new features. I’m trying to take an agile approach with maintaining the Webform module that seeks to iteratively implement working features knowing that features and functionality can and should evolve over time.
The Webform for Drupal 8 (formerly known as YAML Form module) is a completely new codebase striving to reach reasonable feature parity with the Webform 7.x-4.x module, which is used by a half million Drupal 7 websites. I've also looked at the Webform ecosystem for Drupal 7 - gradually I’m integrating key Webform add-on modules into the core Webform module for Drupal 8.
Ajaxifying Webform Forms and User Interface
If you're a non-profit volunteer, board member, director, or staff, should you be afraid of using Drupal for your website needs?
There's been a lot of doom and gloom in the Drupal Community with Drupal 8 being more complex than ever! Other "content management systems" (a.k.a. CMS's) have long claimed that "Drupal is hard", "Drupal is expensive".
Is Drupal hard? Is Drupal 8 even "harder"? Is it "too expensive" for your non-profit?
Does Drupal suck at non-profits?
In this article, I take a deep dive, looking at what non-profits need from a website and how well Drupal can provide for those needs.
Read on to see what I think, and PLEASE, share your thoughts in the comments below!
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 SMTP module to fix an Information Disclosure vulnerability.
This SMTP module enables you to send mail using a third party (non-system) mail service instead of the local system mailer included with Drupal.
When this module is in debugging mode, it would log privileged information.
With the help of the D6LTS vendors, a new version was released.
If you have a Drupal 6 site using the SMTP 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 Drupal.org).
Meet our last intern: Brandon Reid of our Web & Drupal Developer Internship program! One of his first projects as an intern was to research High Tech Website built on Drupal, so without further ado, here are his findings:
For those who aren't familiar with Drupal. Drupal is the #1 platform for web content management among global enterprises, governments, higher education institutions, and NGOs. Drupal is flexible and highly scalable, publishing a single website or shares content in multiple languages across many devices. Technology and business...Read more
Over the last few years, many of us have seen the need to evolve community governance. Up until now, we had to focus on other priorities, but now is the time to address our needs for community governance especially in light of recent community events.
Our project has matured greatly and participation has expanded from developers and site builders to also include more content editors, designers, and marketing managers who work not only as freelancers or at Drupal shops, but also for large digital agencies or system integrators. We want all community members to be included in these community discussions so the redefined community governance serves everyone. This is an exciting time to create an even healthier future for our ever-growing community.
The Drupal Association is committed to staying in a support role as the community determines how to best evolve community governance to support everyone’s needs. We started helping by hosting Community Discussions that were mediated by Whitney Hess. There were 7 sessions at DrupalCon Baltimore and 7 virtual sessions between April and May. You can find the meeting minutes here.
The Community Discussions surfaced several common needs and identified several strategies for addressing those needs.
The most commonly shared needs of the community are (in order of frequency):
Strategies to address those needs ranged from clarifying the responsibilities and boundaries of the leadership roles throughout the Drupal project, determining how and where to communicate community decisions, improving processes for community management, and providing easier access to documentation about leadership roles and clearly communicating what is expected of Drupal community members.
In terms of next steps, the participants were in agreement that we need to come together in a Governance Summit to start architecting improvements to today’s governance structure. However, the community did not define the best way to hold this meeting. It is still unclear when and where it should be, and who should participate and facilitate. We will send out a community survey next to get input from you to answer these questions.Attend The Webinar
We invite to you attend a webinar on July 6 at 11 am ET / 1600 BST / 8:30 pm IST hosted by Whitney Hess. Whitney will review the findings from our Community Discussions in more detail. We will record the video and share it with you afterwards, along with a written transcript.
Dial in details are below:
Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)
Meeting ID: 589 988 397
International numbers available:
Thank you for your patience and participation as we tackle these big questions and move forward together as a stronger community.
The Drupal CLI. A tool to generate boilerplate code, interact with and debug Drupal.heykarthikwithu Wednesday, 28 June 2017 - 12:05:12 - IST, Asia/Kolkata
This blog post summarises my fourth week of the coding period of Google Summer of Code with Drupal.Code Review
The week began with iterating over previously committed code based on feedback by Colan. After making the changes and pushing them, I later merged the merge request into the 8.x-1.x-dev branch after Colan’s approval.tameeshb Wed, 06/28/2017 - 09:16 Tags GSoC Google Summer of Code 2017 Drupal Drupal Blog