Drupal

Chart.js

New Drupal Modules - 13 May 2016 - 10:54am

This is yet another JavaScript based charting module. But as the chart.js website says

Simple yet flexible JavaScript charting for designers & developers

Categories: Drupal

Composer deploy

New Drupal Modules - 13 May 2016 - 10:03am

The project is very similar to Git deploy but for Composer.

Normally drupal.org inserts version information when a project is packaged. Packages installed via Composer do not contain this information in some cases.

  1. The required version is a dev version
  2. Composer runs in --prefer-source mode

Composer Deploy hooks into the Drupal update system and attempts to provide the version of modules and themes from Composer metadata.

Categories: Drupal

Service Links mailto

New Drupal Modules - 13 May 2016 - 9:10am

The Service Links mailto module integrates with the Service Links module. It adds an extra service on the 'Service Links > Services' page. The output of the mailto link can be configured on the 'Service Links > Widgets' page.

Categories: Drupal

Mediacurrent: Friday 5: 5 Tips to Integrate 3rd Party APIs

Planet Drupal - 13 May 2016 - 8:59am

TGIF! We hope you've had a great week.

We're hot off the heels of DrupalCon but couldn't disappoint and skip this week. We give you, Episode 8! This Friday, Senior Drupal Developer David Younker joins us to discuss 5 Tips to Integrate 3rd Party APIs.

He provides some great tips for integrating 3rd party APIs and feeds in Drupal 7 sites. Watch the video below to learn more about Using Aggregator, Using Feeds, Custom Solutions, API Keys, and OAuth.

Categories: Drupal

Ajax Privatemsg

New Drupal Modules - 13 May 2016 - 7:32am

Introduction
-----------
This module makes the current private message module forms ajax.

Requirements

------------
Drupal 7.x
privatemsg 7.x

Installation
------------
1. Copy the entire ajax_privatemsg in
the Drupal sites/all/modules directory.

2. Login as an administrator.
Enable the module in the "Administrator" -> "Modules"

How to use:
-----------
1.After installation it will automatically makes forms ajax.

Categories: Drupal

Red Route: There's more than one way to Drupalise a cat

Planet Drupal - 13 May 2016 - 5:28am

One of the components in the design is something I'm calling tiles - as always, naming things is one of the hardest parts.

The component includes an image with a transparent overlay, showing the title. On hover and focus, some extra information becomes visible. For instance, for a gallery, the address will be shown, and for an exhibition, the artists and tags will be shown. Here's a Codepen which gives you an idea:

See the Pen Tiles... by malcomio (@malcomio) on CodePen.

Different versions of this component are used in quite a few places. On an exhibition page, it applies to a teaser view of the gallery linked via a node reference field. In various views, it applies to the views fields. To get the markup right for the views fields, I needed to create a custom template. But I didn't want to create the same template for each view that needed to use the tile pattern - that would be a nightmare to maintain.

Having read about Twig template extends I was tempted to try them for this use case - it seems like an interesting new feature, so why not try it out?

I created an initial template called views-view-fields--tiles.html.twig, and then set the view template to use it. For instance, I wanted to apply this markup for the exhibitions_new view, so I created a template called views-view-fields--exhibitions-new.html.twig, which contained just one line:

{% extends "themes/gall/templates/views/views-view-fields--tiles.html.twig" %}

It seemed to work OK, but didn't seem like the right approach. For one thing, it would leave me with a theme cluttered with loads of one-line templates, which would get pretty annoying pretty quickly. For another, it felt like a gratuitous use of a solution - a hammer looking for some nails to bash.

The solution I went with in the end was much more familiar from previous Drupal versions, although it uses the new hook_theme_suggestions_HOOK_alter hook:

/** * Implements hook_theme_suggestions_HOOK_alter(). */ function gall_theme_suggestions_views_view_fields_alter(array &$suggestions, array $variables) { // Set up views to use the tiles template. $tiles_views = array( 'exhibitions', 'exhibitions_a_z', 'exhibitions_new', 'exhibitions_this_gallery', 'galleries_a_z', 'galleries_new', ); $view_id = $variables['view']->id(); if (in_array($view_id, $tiles_views)) { $suggestions[] = 'views_view_fields__tiles'; } }

For someone familiar with previous versions of Drupal, it's another thing which is similar but different. More to learn, and some things to unlearn, but we're not starting from scratch, and we can have more options in our toolkit.

Tags:  Drupal Drupal 8 The Gallery Guide All tags
Categories: Drupal

nielsdefeyter.nl: Watch Drupalcon Now Orleans sessions on Youtube

Planet Drupal - 12 May 2016 - 4:47pm
As always the Drupal Association puts videe-recording of most sessions on DrupalCon Youtube. That is also true for the now ongoing DrupalCon New Orleans 2016. An excellent option for learning and understanding Drupal . (and following the event!) Recored video-sessions on YouTube Link DrupalCon New...
Categories: Drupal

Ajax Dblog

New Drupal Modules - 12 May 2016 - 1:15pm

The Ajax Dblog module provides ajax functionality to the dblog overview page (the watchdog log page). Loading message details onto the overview page using Ajax.

Categories: Drupal

State of Drupal presentation (May 2016)

Dries Buytaert - 12 May 2016 - 11:25am

DrupalCon New Orleans comes at an important time in the history of Drupal. Now that Drupal 8 has launched, we have a lot of work to do to accelerate Drupal 8's adoption as well as plan what is next.

In my keynote presentation, I shared my thoughts on where we should focus our efforts in order for Drupal to continue its path to become the leading platform for assembling the world's best digital experiences.

Based on recent survey data, I proposed key initiatives for Drupal, as well as shared my vision for building cross-channel customer experiences that span various devices, including conversational technologies like Amazon Echo.

You can watch a recording of my keynote (starting at 3:43) or download a copy of my slides (162 MB).

Take a look, and as always feel free to leave your opinions in the comments!

Categories: Drupal

Dries Buytaert: State of Drupal presentation (May 2016)

Planet Drupal - 12 May 2016 - 11:25am

DrupalCon New Orleans comes at an important time in the history of Drupal. Now that Drupal 8 has launched, we have a lot of work to do to accelerate Drupal 8's adoption as well as plan what is next.

In my keynote presentation, I shared my thoughts on where we should focus our efforts in order for Drupal to continue its path to become the leading platform for assembling the world's best digital experiences.

Based on recent survey data, I proposed key initiatives for Drupal, as well as shared my vision for building cross-channel customer experiences that span various devices, including conversational technologies like Amazon Echo.

You can watch a recording of my keynote (starting at 3:43) or download a copy of my slides (162 MB).

Take a look, and as always feel free to leave your opinions in the comments!

Categories: Drupal

ThinkDrop Consulting: Onward with OpenDevShop Inc

Planet Drupal - 12 May 2016 - 9:27am

Today I am awaking to the last "official" day of DrupalCon New Orleans with a huge new wind at my back.

It felt like an appropriate time to post what is likely my last blog post as ThinkDrop Consulting LLC.

My partners and I have been in a whirlwind tour of the convention, spreading the news of our product, and our new company: OpenDevShop Inc. In order to focus entirely on development and hosting tools, I am closing up ThinkDrop Consulting.

We've been building the OpenDevShop platform since late 2011 for my clients and myself, and in January of this year, we incorporated.

Our mission: to make hosting, testing, and scaling websites as easy as possible; to make infrastructure management as easy to deal with as content; and to foster a community around these types of tools.

OpenDevShop Inc is a member of the newly formed Aegir Coop. The cooperative is a group of companies and individuals who have organized together to support and develop the Aegir ecosystem.

We are working hard to not only grow this business but to grow the Aegir community, both users but especially contributors. We have a lot of work to do if Aegir is going to live up to modern expectations of infrastructure management and deployment tools.

Today we have two Birds of a Feather sessions back to back at DrupalCon: one for OpenDevShop and one for the Aegir Coop.

The energy behind the Drupal Community has never been higher. Let's follow in their footsteps and bring together everyone that cares about better Infrastructure Management and DevOps.

Come join the Aegir & OpenDevShop communities in room 292 (AshDay) from 1pm - 3pm, and maybe later if they let us stay.

Please check out our new company website, opendevshop.com.

We will see you around the community!

Tags: devshopPlanet Drupal
Categories: Drupal

Left pad

New Drupal Modules - 12 May 2016 - 8:08am

String left pad

Usage

/** @var ContainerInterface $container */ $service = $container->get('left_pad.default'); // Results in '00005' $result = $service->leftPad('5', 5, 0);

Don't worry, it also includes an interface if you want to override the service!

Categories: Drupal

LevelTen Interactive: Learn with LevelTen: DrupalCon Session Twitter Recap

Planet Drupal - 12 May 2016 - 7:50am

The LevelTen team used the hashtag #learnwithl10 to document the various sessions they attended and what they learned on Tuesday and Wednesday of DrupalCon New Orleans.

...Read more
Categories: Drupal

DrupalEasy: DrupalEasy Podcast: New Orleans Day 1

Planet Drupal - 12 May 2016 - 7:50am

Direct .mp3 file download.

Hosts Ryan Price, Mike Anello, Ted Bowman and Kelley Curry are joined by guests Mike Herchel (of the Lullabot Podcast) and Steve Edwards (formerly of the Acquia Podcast) to discuss the events on Day 1 of DrupalCon. We start with the Prenote and Driesnote, and then discuss sessions each person was interested in throughout the day.

Check in later this week for more episodes from DrupalCon New Orleans 2016.

Follow us on Twitter Intro Music

House of Drupalcon from #Prenote

By Adam Juran, Campbell Vertessi and Jeremy "JAM" Macguire

Subscribe

Subscribe to our podcast on iTunesGoogle Play or Miro. Listen to our podcast onStitcher.

If you'd like to leave us a voicemail, call 321-396-2340. Please keep in mind that we might play your voicemail during one of our future podcasts. Feel free to call in with suggestions, rants, questions, or corrections. If you'd rather just send us an email, please use our contact page.

Categories: Drupal

Apigee

New Drupal Modules - 12 May 2016 - 7:32am
Categories: Drupal

OSTraining: Drupal 8 CookieConsent EU Law module

Planet Drupal - 12 May 2016 - 4:53am

One of are OSTraining members asked how to add cookie notification to a drupal 8 site.

The CookieConsent is a module provides a solution to deal with the EU Cookie Law.

And is particularly useful if you want to use the SuperCookie module

Categories: Drupal

Wunderkraut blog: Dropcat - the configuration files

Planet Drupal - 12 May 2016 - 4:26am

In a series of blog posts I am going to present our new tool for doing drupal deploys. It is developed internally in the ops-team in Wunderkraut Sweden , and we did that because of when we started doing Drupal 8 deploys we tried to rethink how we mostly have done Drupal deploys before, because we had some issues what we already had. This is part 2.

The idea with dropcat is that you use it with options, or/and with configuration files. I would recommend to use it with config files, and with minor settings as options. 

You could use just use a default settings file, that should be dropcat.yml, or as in most cases you have one config file for each environment you have – dev, stage, prod etc.

You could use an environment variable to set which environment to use, this variable is called DROPCAT_ENV.  To use prod environment you could set that variable in the terminal to prod with:
export DROPCAT_ENV=prod

Normally we set this environment variable in our jenkins build, but you could also set it as an parameter with dropcat like:
dropcat backup --env=prod

That will use the dropcat.prod.yml file

By default dropcat uses dropcat.yml if youi don't set an environment. 

Thing will be more in the next blog posts, but first we now look into a minimal config file, in our root dir we could hav a dropcat.yml file with this config:

app_name: mysite local: environment: tmp_path: /tmp seperator: _ drush_folder: /home/myuser/.drush remote: environment: server: mytarget.server.com ssh_user: myuser ssh_port: 22 identity_file: /home/myuser/.ssh/id_rsa web_root: /var/www/webroot temp_folder: /tmp alias: mysite_latest_stage site: environment: drush_alias: mysitestage backup_path: /backup original_path: /srv/www/shared/mysite_stage/files symlink: /srv/www/mysite_latest_stage/web/sites/default/files url: http://mysite.com name: mysitestage mysql: environment: host: mymysql.host.com database: my_db user: my_db_user password: my_db_password port: 3306

The settings is grouped in a way that should explain what they are used for – local.environment is from where we deploy, remote.environment is to where we deploy. site.environment is for drush and symlinks (we use for the files folder), mysql.environment, is for… yeah you guessed correctly – mysql/mariadb. 

appname

This is the application name, used for creating a tar-file with that name (with some more information, like build date and build number).

local

These are the settings from where we deploy, it could be localy, it could be a build server as jenkins. 

tmp_path

Where we temporary store stuff.

Seperator

Used for i name of foler to deploy as seperator like myapp_DATE


drush_folder

Where drush-settings from you deploy from, normaly in your home folder (for jenkins normaly: /var/lib/jenkins/.drush), and this is also to which path the drush alias is saved on dropcat prepare.

Remoteserver

The server you deploy you code too.

ssh_user

User to use with ssh to your remote server

ssh_port

Port used to use ssh to your server

identity_file

Which private ssh-key to use to login to your remote server

web_root

Path to which your site is going to be deployed to.

temp_folder

Temp folder on remote server, used for unpacking tar file.

alias

Symlink alias for you site


Sitedrush_alias

Name of you drush alias, used from 'local' server. Drush alias is created as a part of dropcat prepare.

backup_path

Backup path on ”local” server. Used by dropcat backup

original_path

Existing path to point a symlink to – we use for the files folder

symlink

Symlink path that points to original_path

url

URL for you site, used in drush alias

name

Name of site in drush alias.


Mysqlhost

name of db host

database

Database to use

user

Database user

password

password for db user to host

port

Port to use with mysql

We are still on a very abstract level, next time we will go through that is needed in an normal jenkins-build.

Categories: Drupal

Wunderkraut blog: Dropcat - the configuration files

Planet Drupal - 12 May 2016 - 4:26am

In a series of blog posts I am going to present our new tool for doing drupal deploys. It is developed internally in the ops-team in Wunderkraut Sweden , and we did that because of when we started doing Drupal 8 deploys we tried to rethink how we mostly have done Drupal deploys before, because we had some issues what we already had. This is part 2.

The idea with dropcat is that you use it with options, or/and with configuration files. I would recommend to use it with config files, and with minor settings as options. 

You could use just use a default settings file, that should be dropcat.yml, or as in most cases you have one config file for each environment you have – dev, stage, prod etc.

You could use an environment variable to set which environment to use, this variable is called DROPCAT_ENV.  To use prod environment you could set that variable in the terminal to prod with:
export DROPCAT_ENV=prod

Normally we set this environment variable in our jenkins build, but you could also set it as an parameter with dropcat like:
dropcat backup –env=prod

That will use the dropcat.prod.yml file

By default dropcat uses dropcat.yml if youi don't set an environment. 

Thing will be more in the next blog posts, but first we now look into a minimal config file, in our root dir we could hav a dropcat.yml file with this config:

app_name: mysite local: environment: tmp_path: /tmp seperator: _ drush_folder: /home/myuser/.drush remote: environment: server: mytarget.server.com ssh_user: myuser ssh_port: 22 identity_file: /home/myuser/.ssh/id_rsa web_root: /var/www/webroot temp_folder: /tmp alias: mysite_latest_stage site: environment: drush_alias: mysitestage backup_path: /backup original_path: /srv/www/shared/mysite_stage/files symlink: /srv/www/mysite_latest_stage/web/sites/default/files url: http://mysite.com name: mysitestage mysql: environment: host: mymysql.host.com database: my_db user: my_db_user password: my_db_password port: 3306

The settings is grouped in a way that should explain what they are used for – local.environment is from where we deploy, remote.environment is to where we deploy. site.environment is for drush and symlinks (we use for the files folder), mysql.environment, is for… yeah you guessed correctly – mysql/mariadb. 

appname

This is the application name, used for creating a tar-file with that name (with some more information, like build date and build number).

local

These are the settings from where we deploy, it could be localy, it could be a build server as jenkins. 

tmp_path

Where we temporary store stuff.

Seperator

Used for i name of foler to deploy as seperator like myapp_DATE


drush_folder

Where drush-settings from you deploy from, normaly in your home folder (for jenkins normaly: /var/lib/jenkins/.drush), and this is also to which path the drush alias is saved on dropcat prepare.

Remoteserver

The server you deploy you code too.

ssh_user

User to use with ssh to your remote server

ssh_port

Port used to use ssh to your server

identity_file

Which private ssh-key to use to login to your remote server

web_root

Path to which your site is going to be deployed to.

temp_folder

Temp folder on remote server, used for unpacking tar file.

alias

Symlink alias for you site


Sitedrush_alias

Name of you drush alias, used from 'local' server. Drush alias is created as a part of dropcat prepare.

backup_path

Backup path on ”local” server. Used by dropcat backup

original_path

Existing path to point a symlink to – we use for the files folder

symlink

Symlink path that points to original_path

url

URL for you site, used in drush alias

name

Name of site in drush alias.


Mysqlhost

name of db host

database

Database to use

user

Database user

password

password for db user to host

port

Port to use with mysql

We are still on a very abstract level, next time we will go through that is needed in an normal jenkins-build.

Categories: Drupal

Pages

Subscribe to As If Productions aggregator - Drupal