All RPGs and Storygames by Tod Foley are now available at DrivethruRPG and RPGnow. Bring these games to your table!
We are in the seventh week of GSoC 17 to integrate Google Cloud Machine Learning Engine to Drupal. Before proceeding, please have a look at our previous blogs and mainly the major planning week. This week started with the aspiration to create a basic version of the ml_engine module, but we could reach only till creating basic entities. The major problem we faced was the daunting bugs in creating the entities. I made a mistake by spending almost a week trying to solve the issue without updating the issue queue. Recently have added it to the issue page. Let me share a screencast of the progress.
Our initial reference in creating the entity was the examples module. It has a sub module content_entity_example that explains how to create a content entity to store Contacts. We made a similar one called Project by tweaking few functionalities. Here is the code. It gave a problem of having the same Tensorflow input fields for all projects. The fields we created using entity manage fields were getting reflected in all the project entities. It was a good place to start playing with entities. With the design to use different inputs for each project in mind, the Contact and Node modules that ships with the core was referred. It gave the insight to store the ML Engine Project and its Input as separate Drupal entities.
The Project is a config entity that handles the ML Engine settings data. It holds job, model and version names, training steps, deployment URL etc. The Argument is a content entity that handles the command line arguments to the Tensorflow code. The Argument entity fields for Tensorflow code can be varied but Projects fields are fixed.
With one week left for the second major evaluation, we have some major works to be completed to achieve the deliverables. The first one is to complete coding the entities. Second, convert the selected Drupal Views to CSV. Third, enable each project entity to run training, deployment, and prediction. Finally to create a plugin to format the prediction output. The second and the final tasks are the hard ones. I am expecting the coming week to be hectic. We will complete the coding and submit it for mentor review.
Acquia Developer Center Blog: Acquia Dev Scan: Taming Expanding Databases in Drupal 8, Reservoir on DrupalEasy, and a Conference for Decoupled Drupal Developers
When Acquia-related developer content starts piling up around the Web, it's time for an Acquia Dev Scan.
In this edition: Taming Expanding Databases in Drupal 8, Reservoir on DrupalEasy, and a Conference for Decoupled Drupal DevelopersDealing with expanding cache_render tables in Drupal 8
There are a number of scenarios in Drupal 8 where you might notice your MySQL database size starts growing incredibly fast, even if you're not adding any content.Tags: acquia drupal planet
This blog post summarises the seventh week of writing code for Drupal for the Google Summer of Code.tameeshb Wed, 07/19/2017 - 19:42 Tags GSoC Google Summer of Code 2017 Drupal Drupal Blog
Now that Drupal 8 is “production ready,” and agencies are ready to expand their capabilities by building in Drupal 8, clients are asking about it, and the community’s focus has shifted to developing for it.
Drupal 8’s predecessor, Drupal 7, has been around since January 2011, which means that by late 2016 everyone working in Drupal was very familiar with the ins-and-outs of how Drupal 7 worked.Tags: acquia drupal planet
Since content is king, content marketing is a must-have strategy. With the content you present on the web, you can attract visitors and keep them interested. But have you ever wanted to interact and collaborate with your users through the content? Do you need them not just passively perceive your content, but take some actions with it? This is possible with H5P (HTML 5 Package).Read more
Like many of you, I have a few sites that are fairly complex, utilize dozens of modules - and still run on Drupal 6. At this point, I don't want to invest the time to migrate them to Drupal 7 because I feel the momentum is finally beginning to shift into high gear for Drupal 8.
So, how do you know whether the Drupal 8 ecosystem is ready for a relatively straightforward migration? Thankfully, there are some great resources available!
One of our clients requested to integrate AppNexus ads with their Drupal 8 site. The requirements were very simple:
- Ability to display ads as blocks.
- Ad blocks should be configurable: tagId, Sizes. And pass those variables via apntag.defineTag().
- Ability to pass global page options via apntag.setPageOpts().
Since there wasn't any module that would support this I decided to create a module that will be very easy to use and at the same time will be extendable and useful in other projects.
The module comes with a simple PHP class that helps to generate pageOpts from hook_page_attachments(). You may create your own class using that class as an example.
It feels great to build a Drupal tool that has achieved more than 1 million downloads and helps people from different places around the world to create, build and deploy Drupal applications. It's been quite a journey, which took almost four years and required a lot of time and effort. It’s only fitting that I walk you through my Drupal Console journey.
I hope that taking you through my experience working on the Drupal Console will motivate you become part of a project, collaborate or take the first step. So here are the most important milestones.The Beginning: The commit that started all
After been organizing a few hangouts and trying to decide to start a contributed project related to Drupal 8, David Flores pushed the first commit to the project repo. It was just a README.md file but every journey, even those that impact many people, start with one single step. That file marked the beginning of Drupal Console.jmolivas Tue, 07/18/2017 - 15:20
I recently shared the community needs and potential strategies for evolving community governance, which resulted from the Community Discussions we held in person and online throughout April and May. You can find the webinar recording and written transcript, as well as the meeting minutes from all Community Discussions, at https://www.drupal.org/community/discussions.
Many community members who participated in these discussions agreed that the next step to take in this process is to hold a Community Governance Summit. However, we are not yet clear on where and when this event should take place, who should participate, and several other important details. I worked with community members to develop this survey so we can answer those questions.
Please take 5 minutes to take this community survey and tell us your thoughts about the Community Governance Summit. This survey will remain open until 11:59pm EDT on July 28, 2017. We will analyze the findings and report back on what we learned in a follow-up blog post by Friday, August 4.
Thank you for your time and participation.
In last two blog post we discussed the basics of getting started with Drupal Commerce and the steps of e-commerce products creation. As we move forward with our learnings, we will write about how we dealt with those.
There is Business logic which demands few things out of the box where we create custom modules to aid a process. I came across a situation where we had to use Drupal Commerce module but the product was coming from the content type. Even though we had to import the product as commerce…
For the second time, around 100 people gathered in Heidelberg, Germany, for the 2-day Drupal Business & Community Days Heidelberg 2017 conference. Its unique concept combined two session tracks focusing on community and business topics.Josef Dabernig Tue, 07/18/2017 - 07:37
Apart from sprints and BoFs, the two session tracks allowed attendees to switch between community and business focused sessions. The community track focused on sessions in English for a more international crowd, while the business track sessions were held in German and attracted more attendees from the DACH (Germany Austria Switzerland) region.
Here are some of my highlights from the conference:
Die Firma sind wir! by Dietmar „dietmarg“ Giegler and Luca Curella was a talk about how Reinblau switched to holocracy. The cooperative of roughly 18 freelancers is using bi-weekly governance meetings moderated by a facilitator to allow for the improvement of the organisational structure by everyone involved.
Dr. Julia Schönborn (karmajob) in "Der ehrbare Kaufmann“ CSR: Verantwortungsvoll handeln und richtig darüber sprechen shared insights about how Corporate Social Responsibility (CSR) can be used as a holistic approach to focus all efforts of a company with regards to social responsibility.
I found it interesting that this approach has been mostly associated with big corporations in the past while smaller Drupal agencies, for example, also see their social responsibility extended to the contribution of open source code and providing a good working environment.
A look into a possible Future for all of us: React, GraphQL and Drupal by Michael "schnitzel" Schmid from Amazee.io shared all the findings we gained from creating multiple decoupled websites based on React, GraphQL and Drupal.
If you are keen to find out more about the topic, the Decoupled Developer Days are taking place in New York August 19-20, 2017.
Along with these highlights, there were also some other inspiring presentations, and during the 2 days, Drupal Business & Community Days Heidelberg 2017 provided a great way to connect with the German and international Drupal community.
Together with regional experts and enthusiasts for digital and open source we were able to connect and have in-depth collaborations and exchanges in a relaxed environment.
A common problem that I’ve faced, particularly in the last few years, is how to deliver the complex, component driven design that clients want while also giving content authors full flexibility with those components without creating an un-maintainable, or brittle product.
Drupal core announcements: July 17th, 2017 Symfony security fix in Security component (CVE-2017-11365) - Drupal not affected
Symfony contacted the Drupal Security team about today's Symfony security release addressing an issue in UserPasswordValidator. This announcement is to reassure the Drupal community that Drupal 8 is not affected by this fix, as it does not make use of this security component. There is no Drupal 8 release scheduled for this, and there is no action you need to take on your Drupal site(s).
Drupal 8.4.0, the next planned minor release of Drupal 8, is scheduled for Wednesday, October 4, 2017. Minor releases include new features, usability improvements, and backwards-compatible API improvements. Here's what this means now for core patches.
The goal of the alpha phase is to begin the preparation of the minor release and provide a testing target for theme or module developers and site owners. Alpha releases include most of the new features, API additions, and disruptive changes that will be in the upcoming minor version.Drupal 8.4.0-alpha1 will be released the week of July 31
In preparation for the minor release, Drupal 8.4.x will enter the alpha phase the week of July 31. Core developers should plan to complete changes that are only allowed in minor releases prior to the alpha release. (More information on alpha and beta releases.)
- Developers and site owners can begin testing the alpha. (Note for Drush users: Drupal 8.4.x requires Drush 8.1.12.)
- The 8.5.x branch of core will be created, and future feature and API additions will be targeted against that branch instead of 8.4.x. All outstanding issues filed against 8.4.x will be automatically migrated to 8.5.x once it is opened.
- All issues filed against 8.3.x will then be migrated to 8.4.x, and subsequent bug reports should be targeted against the 8.4.x branch.
- During the alpha phase, core issues will be committed according to the following policy:
- Most issues that are allowed for patch releases will be committed to 8.4.x and 8.5.x.
- Drupal 8.3.x will receive primarily critical bugfixes in preparation for its final patch release window. (Drupal 8.2.x and older versions are not supported anymore and changes are not made to those branches.)
- Most issues that are only allowed in minor releases will be committed to 8.5.x only. A few strategic issues may be backported to 8.4.x, but only at committer discretion after the issue is fixed in 8.5.x (so leave them set to 8.5.x unless you are a committer), and only up until the beta deadline.
Roughly two weeks after the alpha release, the first beta release will be created. All the restrictions of the alpha release apply to beta releases as well. The release of the first beta is a firm deadline for all feature and API additions. Even if an issue is pending in the Reviewed & Tested by the Community (RTBC) queue when the commit freeze for the beta begins, it will be committed to the next minor release only.
The release candidate phase will begin the week of September 4, and we will post further details at that time.
See the summarized key dates in the release cycle, allowed changes during the Drupal 8 release cycle, and Drupal 8 backwards compatibility and internal API policy for more information.
As a reminder, we have until the start of the alpha to add great new features to Drupal 8.4.x. Several experimental modules have 8.4.x alpha deadlines:
- Workflows and Content Moderation (must reach beta stability)
- Media (must become stable to provide a stable API for contrib media modules)
- Settings Tray (must become stable)
- Place Blocks (must become stable)
- Inline Form Errors (must become stable)
- Datetime Range (must become stable)
Help is most welcome with issues on the roadmaps for the linked modules now for a great Drupal 8.4.0!
There are a number of scenarios in Drupal 8 where you might notice your MySQL database size starts growing incredibly fast, even if you're not adding any content. Most often, in my experience, the problem stems from a exponentially-increasing-in-size cache_render table. I've had enough private conversations about this issue that I figure I'd write this blog post to cover common scenarios, as well as short and long-term fixes if you run into this issue.
Consider the following scenarios I've seen where a cache_render table increased to 10, 50, 100 GB or more:
Oh! Hey there, my name is Piyush Jain and as a new staff member at the Drupal Association I wanted to learn what the community likes so much about DrupalCon.
This week, I spoke with Rachel Lawson (rachel_norfolk), who has been part of the Drupal community for 11 years, and attended 6 DrupalCons.