Style Node Title

New Drupal Modules - 22 January 2018 - 6:26am

This module adds a class to the title field for content types. This module will be very usefull when you want design different style for specific nodes of single content type.

Instructions for use:

Pre-requisite, if using nested fieldsets group using htmlelement

1) Add the field "field_style_title" as a checkbox to your content type and place with the title for easy editor use.
2) On the content check the field_style_title to add class to the title

Categories: Drupal

Mediacurrent: Power your Drupal 8 Project with Docksal

Planet Drupal - 22 January 2018 - 6:09am

Hello and welcome to my first blog post for Mediacurrent! Today’s post will be all about Docksal and how it can help you get up and running developing on Drupal 8 quickly and easily. This post was inspired by the great session I saw at DrupalCon 2017 and will explain how using Docksal will save you time getting up and running for a new Drupal development project. I’ll also talk about some of the technologies behind Docksal such as Docker and Oracle VM VirtualBox.

Categories: Drupal

Noughts and Crosses

New Drupal Modules - 22 January 2018 - 5:59am

This is basically fun game module. In this module, two players can play tic tac toe interactively.
The player who succeeds in placing three of their marks in a horizontal, vertical, or diagonal row wins the game.

Complete module is based jQuery, however, non-js feature is also available.

Features :
1. Two players(Humans) can play this game.
2. A block is provided so that it can be integrated in any part of site.
3. Instant results are provided.

Categories: Drupal

Imprecise Date Field

New Drupal Modules - 22 January 2018 - 5:28am
Categories: Drupal

User can delete own profile and its content

New Drupal Modules - 22 January 2018 - 3:07am

This module is created to so that users can delete their profiles.
The 'Delete Profile' button is available to the users when he wish to update profile through 'Edit profile Page'. Use of this button by users will delete the profile as well as the content related to the user.

Categories: Drupal

Next Previous Post View

New Drupal Modules - 22 January 2018 - 2:57am

I have developed a Drupal 8 module and named it "Next and previous link" The Drupal plug-in will allow the website visitors to jump on the next or previous post without going back to the main page to see all the posts. Drupal developers can use this plug-in for particular content types. Suppose, there are many large content bundles, then the developer can apply the plug-in for a specific bunch of content.

To understand how this plug-in will work, you can click on the following demo link

Categories: Drupal

LC sms.ru client

New Drupal Modules - 22 January 2018 - 2:19am

Leads capture module sms.ru delivery service ("deliveryman").

This module allow delivery leads info to sms by service sms.ru.

For using:

Categories: Drupal

Amazee Labs: What the hell is GraphQL?

Planet Drupal - 22 January 2018 - 2:16am
What the hell is GraphQL?

With the growing popularity of GraphQL, the obligatory host of more or less founded opinions - trying to tell you that it's all just a hype - is also on the rise throughout the internet. 

Some of them have a point, some don’t, and you bet we have an opinion too.

Philipp Melab Mon, 01/22/2018 - 11:16

The end of the year is now way past us and I crunched some numbers. The most frequent question I’ve been asked was: «Philipp, could you mute yourself? Your keyboard is very loud.» But that one wouldn't promise a good blog post. So, instead, I will write about the second most frequently asked question: «Why would you use GraphQL instead of REST?»

Honestly, because I wanted to avoid a discussion, which I knew would take too long, I often gave one of the following diplomatic answers: «They serve different use cases.», «It’s a matter of taste.», «GraphQL can’t do everything …»

So here’s my new years' confession: I lied

Common perception of GraphQL

When reading opinions about GraphQL distinct patterns keep popping up. Let's have a look at them. 

GraphQL is there to reduce HTTP requests

When fetching complex related data sets with REST, you need to issue multiple requests. GraphQL avoids that by specifying all information requirements upfront. This is true, but just a small part of the picture. HTTP2 would be a better option to just reduce the overhead of multiple requests, without turning everything else upside down.

GraphQL is a supplement to React

That is a widespread misunderstanding since GraphQL was born out of requirements that emerged with complex Javascript clients, which in turn happen to be implemented with React quite often these days. But GraphQL doesn’t make any assumptions about the client technology it is consumed with. It doesn’t even assume it’s used above HTTP.

GraphQL is not cacheable

A GraphQL query may contain information from different entities, varying fields with arbitrary naming and therefore responses can’t be cached. Responses can be cached, but it’s harder. Besides, it is part of the client’s responsibility to construct queries intelligently, so they can be cached instead of blindly cramming everything into one request.

GraphQL is insecure

Or a less drastic wording: GraphQL has a larger attack surface. Depending on your application, that’s true. Since one query can request a cascading amount of related entities, there’s a lot more potential for something going south. This can be mitigated by designing the schema in a way that doesn’t allow funky constructs or using static query complexity analysis to reject queries that could get out of hand. But both approaches require experience and engineering. It’s definitely easier to safeguard a REST API.

GraphQL is a replacement for REST

That's the big misunderstanding. In my opinion, GraphQL shouldn’t be perceived as an alternative to REST, but as the layer underneath. Conceptually, a REST endpoint is nothing but a persisted GraphQL query.

From a consumers perspective, GraphQL can do anything REST can. Period. There is no valid reason to choose REST over GraphQL.

From a providers perspective, the reduced subset of actions and predictable responses of a REST API are a lot easier to manage.

GraphQL’s elevator pitch

This brings me to the 3rd most asked question of 2017: What’s GraphQL’s elevator pitch?

GraphQL shifts control from data storage and structures to client and product development.

This also answers the question of “when” to use GraphQL: Whenever you want your client to be more powerful. This might not be the case for a public HTTP API. But whenever you control the client, GraphQL is the better choice. And keep in mind that “client” doesn’t necessarily mean web browser, React frontend or smartphone application. GraphQL provides a structured way to describe information requirements that are not limited to HTTP.

It is for example possible to use GraphQL in combination with Twig to turn Drupal’s push-based rendering model upside down and give theme developers all the power they longed for. But this story has already been told.

Categories: Drupal

Form mode field extra

New Drupal Modules - 21 January 2018 - 11:54pm

This module will help in adding custom classes and field wrapper prefix and suffix in form mode
You can use a different setup for different form mode.

How to use
1. Go to "Manage Form Display" of a node type
3. Click on settings of any field
4. Enter prefix and suffix wrapper elements or Enter CSS Class
5. Click "Update" button
6. Remember to click "Save" button after making necessary changes.

Categories: Drupal

PreviousNext: Managing Composer Github access with Personal Access Tokens

Planet Drupal - 21 January 2018 - 7:20pm

All PreviousNext Drupal 8 projects are now managed using Composer. This is a powerful tool, and allows our projects to define both public and private modules or libraries, and their dependencies, and bring them all together.


However, a if you require public or private modules which are hosted on GitHub you may run into the API Rate Limits. In order to overcome this, it is recommended to add a GitHub personal access token to your composer configuration.


In this blog post, I'll show how you can do this in a secure and manageable way.

by Kim Pepper / 22 January 2018

It's common practice when you encounter a Drupal project to see the following snippet in a composer.json file:

"config": { "github-oauth": { "github.com": "XXXXXXXXXXXXXXXXXXXXXX" } },

What this means is, everyone is sharing a single account's personal access token. While this may be convenient, it's also a major security risk should the token accidentally be made public, or a team member leaves the organisation, and still has read/write access to your repositories.

A better approach, is to have each team member have their own personal access token configure locally. This ensures that individuals can only access repositories they have read permissions for, and once they leave your organisation they can no longer access any private dependencies.

Step 1: Create a personal access token

Go to https://github.com/settings/tokens and generate a new token.

You will need to specify all repo scopes.

Finally, hit Generate Token to create the token.

Copy this, as well need it in the next step.

Step 2: Configure Composer to use your personal access token

Run the following from the command line:

composer config -g github-oauth.github.com XXXXXXXXXXXXXXXXXXXXXXX

You're all set! From now on, composer will use your own individual personal access token which is stored in $HOME/.composer/auth.json

What about Automated Testing Environments?

Fortunately, composer also accepts an environment variable COMPOSER_AUTH with a JSON-formatted string as an argument. For example:


You can simply set this environment variable in your CI Environment (e.g. CircleCI, TravisCI, Jenkins) and have a personal access token specific to the CI environment.


By using Personal Access Tokens, you can now safely remove any tokens from the project's composer.json file, removing the risk this gets exposed. You can also know that by removing access for any ex-team members, they are no longer able to access your organisations repos using a token. Finally, in the event of a token being compromised, you have reduced the attack surface, and can more easily identify which user's token was used.


Tagged Composer, Security, Drupal Security
Categories: Drupal

Internal Server Error

New Drupal Modules - 21 January 2018 - 6:28pm

Coming soon.

Categories: Drupal

Agiledrop.com Blog: AGILEDROP: Drupal events in 1st quarter of the year

Planet Drupal - 21 January 2018 - 5:40pm
We've stepped into a beginning of a new year, and there will be many events organised by the Drupal community in the first couple of months. We've made a list of Drupal camps and summits that you can attend in the first quarter of the year. Drupal events are bringing together Drupal developers, site builder, themers, end users and those interested in learning more about Drupal. We are attending Drupal events because of, sessions and collaborative discussions. DrupalCamp NJ 2018 United States, Princeton, NJ The campus of Princeton University 3. February 2018 09:00-18:00 This will be the 7th… READ MORE
Categories: Drupal

fluffy.pro. Drupal Developer's blog: Monolog: namespaced logger?

Planet Drupal - 21 January 2018 - 11:47am
Using monolg library and monolog-cascade extension you can't configure the "namespaced" loggers. What does it mean? Imagine you have tons of classes and you need to log information from them into a log file. There is nothing special in this. Just define loggers with the needed handler(s) and instantiate them directly in a place where you want them to use with a help of monolog-cascade. It means in your monolog-cascade config file you have to define needed loggers in advance and you have to reference needed loggers by their names. But what if you need an additional logger (with absolutely different handlers/processors) for some of the classes? Will you go through all the classes and change logger names where you instantiate them? I think it doesn't look like a good idea when a small requirement (for instance, change the log file name for records from a bunch of classes) leads to edits in an application code. It's something that must be configurable and that's why I decided to write a tiny library called monolog-cascade-namespaced.
Read more »
Categories: Drupal

DrupalEasy: Testing a local Drupal site emails with Lando and Mailhog

Planet Drupal - 21 January 2018 - 9:29am

Over the past few months, I've been evaluating three Docker-based local development environments trying to figure out which is best not only for me, but also for students of our long-form Managing Professional Drupal Development Workflows with Pantheon (next semester starts February 17) and Drupal Career Online (March 26) classes.

I've been test driving Docksal (actually, I've been using it for over a year), DDEV Community, and Lando (I'm a recovering Kalabox user) trying to figure out where the "sweet spot" is for flexibility, ease of use, documentation, Windows-compatibility (we routinely have students on Windows machines), performance, and some other criteria.

I recently stumbled upon a cool open source project (thanks Brian!) called Mailhog that makes it dead easy to test outgoing emails from a local development environment. While I tested it on Lando, both Docksal and DDEV both support Mailhog and have supporting documentation here and here

The general idea of Mailhog is that it acts as a local STMP server that by default, doesn't send emails to the addressed recipients. Rather, it includes a clean UI that allows the developer to view outgoing emails. 

Getting Mailhog up-and-running in an existing Lando site is quite easy. Simply add the following to your .lando.yml


    - mail.lemp.lndo.site
    type: mailhog
      - appserver

Then, run "lando rebuild". Caution should be used when using this command, as while most services retain their data during a rebuild, some may not. So far, I can confirm that my databases come through just fine. 

After rebuilding, you're just about done. When you run "lando start" the next time, you'll see a new set of URLs for the local Mailhog UI (you can also get this information via "lando info").



On your local Drupal site, if you're using the SMTP module or another SMTP-based sending solution, be sure to disable it:



Then, sending an email from a local contact form (screenshot shows a local copy of DrupalEasy.com):



Results in this in the Mailhog UI:



Then, if you want to "release" a message to its intended recipient, Mailhog provides you the option to do that as well via a button when viewing an email:



The button leads to an SMTP settings form:



Summarizing, regardless of if you're using Lando, Docksal, DDEV, or another local development stack, Mailhog is a great tool to help you test sending emails from your local development environments. 

While the screenshots in the blog post demonstrate setting up Mailhog with Lando, I can confirm that the process is just as easy with Docksal using the documentation, as I was able to configure it for a local client site in about 5 minutes.

For more information about using Mailhog with Lando, see the official documentation page.  

Categories: Drupal


New Drupal Modules - 21 January 2018 - 1:17am
Categories: Drupal

Matt Glaman: Drupal, Coffee, Burgers - A small world afterall

Planet Drupal - 20 January 2018 - 8:00am
Drupal, Coffee, Burgers - A small world afterall mglaman Sat, 01/20/2018 - 10:00 This year I joined a coffee exchange for some members of the Drupal community. I had known there was one floating around, but finally got signed up. Over the past two years, I have gotten more and more into coffee - being a coffee snob about roasts and learning brewing techniques. Last week we were paired up. And sent out some roasts.
Categories: Drupal

CKEditor Letter Spacing

New Drupal Modules - 20 January 2018 - 6:50am

This module adds a "tracking" dropdown to WYSIWYG that allows users to apply the letter-spacing CSS property to text.


Manual library download:

Categories: Drupal

Eelke Blok: Preparing your Drupal 8.3 site with Media for Drupal 8.4

Planet Drupal - 20 January 2018 - 6:36am

If you have the Media module for Drupal 8 installed, you need to remove it before you can upgrade to the latest core version (8.4). Unfortunately, there are a few gotchas involved with the process. This blog post is about getting rid of the old contrib Media module, so the site can be updated to Drupal 8.4 in a subsequent step. This is based on my personal experience. YMMV, as they say.

Categories: Drupal


New Drupal Modules - 19 January 2018 - 11:24pm

eXtplorer is a web-based File Management Component for all your needs. It has a desktop-application-like interface with drag&drop, grid and a directory tree and makes heavy use of the Sencha ExtJS Javascript Library.
You can use it to access and modify the files and directories on your server via FTP or direct file access.

Download extplorer_D7.tar.gz

Categories: Drupal


New Drupal Modules - 19 January 2018 - 11:09pm

Provides missing OO functionality in Drupal 8, mainly focused on themes.


Categories: Drupal


Subscribe to As If Productions aggregator - Drupal