New Releases Available From Privateer Press

Tabletop Gaming News - 26 October 2017 - 6:00am
The latest releases are now available from Privateer Press. The Trenchers are getting themselves some further bulking up, with a couple of new sets. Cryx is getting a couple retooled jack kits. And then there’s Company of Iron. If you love Warmachine and Hordes, but want something a bit smaller in model count, you can […]
Categories: Game Theory & Design

Car Specification

New Drupal Modules - 26 October 2017 - 5:39am
What is Car Specification module ?

Car Specifications intends to improve adding car specification content by providing:

1. A select field from which you can pre-select a vehicle by
passing year / make / model / trim.
2. Taxonomy Vocabulary .
3. Autocomplete taxonomy fields.
4. --Show-- button prepopulates taxonomy fields with car data.

Purpose of this module is to easy add and save general technical specification about cars.

Categories: Drupal


New Drupal Modules - 26 October 2017 - 5:20am

Integration API with the ChartJS library that provides a "render element" for generating graphs.

In addition to the standard graphs of GraphJS, a new type called "halfdonut" is added. With this, from a doughnut type graph, "half doughnut" type graphs can be generated.

Installation and configuration

ChartJS API Plugin can be installed like any other Drupal module. Place it in the modules directory for your site and enable it on the `admin/modules` page.

This module use lastest version of ChartJS.js library from CDN.

Categories: Drupal

Words on a Screen: Tips for Designing PbP Scenarios

RPGNet - 26 October 2017 - 12:00am
How does the PbP format affect scenario design?
Categories: Game Theory & Design

Appnovation Technologies: Meet the Appnovation Fall 2017 Co-ops

Planet Drupal - 26 October 2017 - 12:00am
Meet the Appnovation Fall 2017 Co-ops Get to know Appnovation's Fall 2017 cohort of post-secondary co-op students. This September 2017 has been both busy and exciting here at Appnovation! We've relocated to a brand new office in the Railtown area of Vancouver, BC, we've hopped into a brand new fiscal year, and we've hired a super cool group of co-op students to help break in the n...
Categories: Drupal

PreviousNext: Lightning talk: Database Deadlocks & Render caching - A case study

Planet Drupal - 25 October 2017 - 7:46pm

In this week's Lightning talk, I go through a case study on an investigation into Deadlocks and Render caching and why cache contexts are so important to get right. Check out the video below to find out how we were able to withstand 10x the throughput with smarter caching.

by Adam Bramley / 26 October 2017 Tagged Cache Contexts, Drupal 8

Posted by Adam Bramley
Senior Drupal Developer

Dated 26 October 2017

Add new comment
Categories: Drupal Blog: AGILEDROP: History of the Druplicon, the famous Drupal symbol

Planet Drupal - 25 October 2017 - 6:54pm
Does everybody know a story how the Drupal was created? It's quite interesting. Dries Buytaert and Hans Snijder were students at the University of Antwerp back in 2000. Back then a broadband internet connection was a luxury, so Hans and Dries set up a wireless bridge among the student dorms to share Hans’s ADSL modem connection among eight students. Dries made an online forum, where they shared news like where they were meeting, having dinner, etc. This software was nameless for a while. Then Dries graduated and left the dorm. They wanted to stay in touch so the internal site had to go… READ MORE
Categories: Drupal

Lullabot: Decoupled Drupal Hard Problems: Image Styles

Planet Drupal - 25 October 2017 - 3:52pm

As part of the API-First Drupal initiative, and the Contenta CMS community effort, we have come up with a solution for using Drupal image styles in a decoupled setup. Here is an overview of the problems we sought to solve:

  • Image styles are tied to the designs of the consumer, therefore belonging to the front-end. However, there are technical limitations in the front-end that make it impossible to handle them there.
  • Our HTTP API serves an unknown number of consumers, but we don't want to expose all image styles to all consumers for all images. Therefore, consumers need to declare their needs when making API requests.
  • The Consumers and Consumer Image Styles modules can solve these issues, but it requires some configuration from the consumer development team.
Image Styles Are Great

Drupal developers are used to the concept of image styles (aka image derivatives, image cache, resized images, etc.). We use them all the time because they are a way to optimize performance on our Drupal-rendered web pages. At the theme layer, the render system will detect the configuration on the image size and will crop it appropriately if the design requires it. We can do this because the back-end is informed of how the image is presented.

In addition to this, Drupal adds a token to the image style URLs. With that token, the Drupal server is saying I know your design needs this image style, so I approve the use of it. This is needed to avoid a malicious user to fill up our disk by manually requesting all the combinations of images and image styles. With this protection, only the combinations that are in our designs will be possible because Drupal is giving a seal of approval. This is transparent to us so our server is protected without even realizing this was a risk.

The monolithic architecture allows us to have the back-end informed about the design. We can take advantage of that situation to provide advanced features.

The Problem

In a decoupled application your back-end service and your front-end consumer are separated. Your back-end serves your content, and your front-end consumer displays and modifies it. Back-end and front-end live in different stacks and are independent of each other. In fact, you may be running a back-end that exposes a public API without knowing which consumers are using that content or how they are using it.

In this situation, we can see how our back-end doesn't know anything about the front-end(s) design(s). Therefore we cannot take advantage of the situation like we could in the monolithic solution.

The most intuitive solution would be to output all the image styles available when requesting images via JSON API (or REST core). This will only work if we have a small set of consumers of our API and we can know the designs for those. Imagine that our API serves to three, and only three, consumers A, B and C. If we did that, then when requesting an image from consumer A we would output all the variations for all the image styles for all the consumers. If each consumer has 10 - 15 image styles, that means 30 - 45 image styles URLs, where only one will be used.


This situation is not ideal because a malicious user can still generate 45 images in our disk for each image available in our content. Additionally, if we consider adding more consumers to our digital experience we risk making this problem worse. Moreover, we don't want the presentation from one consumer sipping through another consumer. Finally, if we can't know the designs for all our consumers, then this solution is not even on the table because we don't know what image styles we need to add to our back-end.

On top of all these problems regarding the separation of concerns of front-end and back-end, there are several technical limitations to overcome. In the particular case of image styles, if we were to process the raw images in the consumer we would need:

  • An application runner able to do these operations. The browser is capable of this, but other more challenged devices won't.
  • A powerful hardware to compute image manipulations. APIs often serve content to hardware with low resources.
  • A high bandwidth environment. We would need to serve a very high-resolution image every time, even if the consumer will resize it to 100 x 100 pixels.

Given all these, we decided that this task was best suited for a server-side technology.

In order to solve this problem as part of the API-First initiative, we want a generic solution that works even in the worst case scenario. This scenario is an API served by Drupal that serves an unknown number of 3rd party applications over which we don't have any control.

How We Solved It

After some research about how other systems tackle this, we established that we need a way for consumers to declare their presentation dependencies. In particular, we want to provide a way to express the image styles that consumer developers want for their application. The requests issued by an iOS application will carry a token that identifies the consumer where the HTTP request originated. That way the back-end server knows to select the image styles associated with that consumer.


For this solution, we developed two different contributed modules: Consumers, and Consumer Image Styles.

The Consumers Project

Imagine for a moment that we are running Facebook's back-end. We defined the data model, we have created a web service to expose the information, and now we are ready to expose that API to the world. The intention is that any developer can join Facebook and register an application. In that application record, the developer does some configuration and tweaks some features so the back-end service can interact optimally with the registered application. As the manager of Facebook's web services, we are not to take special request from any of the possible applications. In fact, we don't even know which applications integrate with our service.

The Consumers module aims to replicate this feature. It is a centralized place where other modules can require information about the consumers. The front-end development teams of each consumer are responsible for providing that information.

This module adds an entity type called Consumer. Other modules can add fields to this entity type with the information they want to gather about the consumer. For instance:

  • The Consumer Image Styles module adds a field that allows consumer developers to list all the image styles their application needs.
  • Other modules could add fields related to authentication, like OAuth 2.0.
  • Other could gather information for analytic purposes.
  • Maybe even configuration to integrate with other 3rd party platforms, etc.
The Consumer Image Styles Project

Internally, the Consumers module takes a request containing the consumer ID and returns the consumer entity. That entity contains the list of image styles needed by that consumer. Using that list of image styles Consumer Image Styles integrates with the JSON API module and adds the URLs for the image after applying those styles. These URLs are added to the response, in the meta section of the file resource. The Consumers project page describes how to provide the consumer ID in your request.

{ "data": { "type": "files", "id": "3802d937-d4e9-429a-a524-85993a84c3ed" "attributes": { … }, "relationships": { … }, "links": { … }, "meta": { "derivatives": { "200x200": "", "800x600": "" } } } }

To do that, Consumer Image Styles adds an additional normalizer for the image files. This normalizer adds the meta section with the image style URLs.


We recommend having a strict separation between the back-end and the front-end in a decoupled architecture. However, there are some specific problems, like image styles, where the server needs to have some knowledge about the consumer. In these very few occasions the server should not implement special logic for any particular consumer. Instead, we should have the consumers add their configuration to the server.

The Consumers project will help you provide a unified way for app developers to include this information in the server. Consumer Image Styles and OAuth 2.0 are good examples where that is necessary, and examples on how to implement it.

Further Your Understanding

If you are interested in alternative ways to deal with image derivatives in a decoupled architecture. There are other alternatives that may incur extra costs, but still worth checking: Cloudinary, Akamai Image Converter, and Origami.

Hero Image by Sadman Sakib

Categories: Drupal

Fruit Ninja Game Series Up On Kickstarter

Tabletop Gaming News - 25 October 2017 - 3:00pm
Fruit Ninja, the popular mobile game about slicing fruit, is getting not one, not two, but three games based on it. Each has its own style and game type, from deck-building, to dice game, to party game. The whole game series is up on Kickstarter now. About the campaign: The Fruit Ninja Tabletop Game Series […]
Categories: Game Theory & Design

Drupal Commerce: Beta release for Commerce Discount 7.x-1.0

Planet Drupal - 25 October 2017 - 2:30pm

Commerce Discount improves Commerce 1.x by providing a custom entity type for managing Product and Order level discounts, including more complicated discounts like free shipping upgrades and BOGO offers. The module makes it easier for merchants to create promotions that would otherwise require the use of the Rules UI or even custom code, tasks that are similarly beyond the reach of most casual Drupal users.

Even as we've worked to improve the user experience even further in Commerce 2.x by making Promotions a core module, we continue to work to do to improve the experience for 1.x users. Today, after a month of focused contrib time at Commerce Guys team and review from end users like Thomas Jonas at the University of Minnesota, we're proud to announce the release of a long overdue beta version for the module.

Categories: Drupal

Dreamcatcher Card Game Up On Kickstarter

Tabletop Gaming News - 25 October 2017 - 2:00pm
I usually have all sorts of weird dreams. It’s hard to explain what goes on, since most of it comes down to “dream logic” to figure out how they all go together. Thankfully, I rarely have nightmares. You never know, that might be because there’s a divine entity out there trapping them and taking care […]
Categories: Game Theory & Design

Mediacurrent: DrupalCamp Atlanta 2017 Highlights

Planet Drupal - 25 October 2017 - 1:32pm

It's official: the countdown to DrupalCamp Atlanta is on. In just two weeks (November 2 - November 4), Mediacurrent will proudly sponsor another great camp in Buckhead, the tech center of ATL. Known for being a top Drupal event in the southeast, DCATL isn't one to miss. It's not too late to register!

Categories: Drupal

Bay Area Drupal Camp: BADCamp videos now available on the website!

Planet Drupal - 25 October 2017 - 1:25pm
BADCamp videos now available on the website! Grace Lovelace Wed, 10/25/2017 - 1:25pm

Thank you! We had so much fun with all of you at BADCamp that we're already excited for next year!

Review what you learned and see what you missed!

Are there sessions you weren't able to attend at BADCamp this year? Or maybe you're back at work ready to apply what you learned and wishing you had better notes? Never fear! We took video of the slides from each presentation at BADCamp that includes audio from our expert speakers! Just visit our event schedule and click on the sessions you'd like to view. Videos are posted at the top of each session page. 

Share your feedback.

Please take a moment to let us know what you thought about BADCamp—it's just a few questions and will help us improve our future events.

Send Your Feedback

Join us at next year's BADCamp, October 24th through 27th, 2018! 

BADCamp Organizing Collective

Drupal Planet
Categories: Drupal

Bigfoot vs. Yet Card Game Up On Kickstarter

Tabletop Gaming News - 25 October 2017 - 1:00pm
Out in the wild, there’s creatures heretofore unknown to science, but certainly known to the local populations. Some of the cryptids are world-famous, even. But, despite their fame, they remain elusive. That’s why you, a cryptozoologist is headed out into the woods to find them, once and for all. However, you never expected a feud […]
Categories: Game Theory & Design

Orc Blitzer Available From Punga Miniatures

Tabletop Gaming News - 25 October 2017 - 12:00pm
It’s starting to get rather chilly outside. Some of my coworkers have started turning on the heat at their place. I’m still in shorts, t-shirt, and sandals because I’m originally from Chicago. Other people that are still in shorts, t-shirt, and sandals are those out on tropical islands. It doesn’t get too cold there. And […]
Categories: Game Theory & Design

Battlegrounds' beloved butt-protecting frying pan was an accidental addition

Social/Online Games - Gamasutra - 25 October 2017 - 11:53am

"Stuff like that is truly emergent," PlayerUnknown's Battlegrounds creator Brendan Greene tells Eurogamer. "Something that you can never really plan for." ...

Categories: Game Theory & Design

MailChimp Service

New Drupal Modules - 25 October 2017 - 11:50am
MailChimp Service for Drupal 8

The Drupal 8 module for MailChimp Service.


To install from this repository:

Clone the repository into your Drupal site modules directory:

git clone --branch 8.x-1.x cd mailchimp_service

This module require drewm/mailchimp-api": "^2.2

Categories: Drupal

Steam users can now send gift cards digitally

Social/Online Games - Gamasutra - 25 October 2017 - 11:17am

Gone are the days when Steam users would have to venture out into the world to buy and send Steam Gift Cards to friends. ...

Categories: Game Theory & Design

Midweek Snippets

Tabletop Gaming News - 25 October 2017 - 11:00am
We’re halfway there, everyone. The work-week is half-done and it’s getting ever-closer to the weekend. Of course, I’m excited for that. I’m hoping to get in some gaming up at the LGS. Trying to get a whole group together for some Guild Ball. Also starting to make Thanksgiving plans, because that’s a thing I do. […]
Categories: Game Theory & Design


Subscribe to As If Productions aggregator