DrupalEasy: DrupalEasy Podcast 180 - Pimping GovCon (Sarah Thrasher - GovCon)

Planet Drupal - 1 July 2016 - 6:37am

Direct .mp3 file download.

Sarah Thrasher (sarahjean), front-end developer with Acquia, joins Andrew (remember him?), Kelley, and Mike to discuss the upcoming Drupal GovCon, what is means to be a junior developer, how the Drupal community is helping to make sure our community members stays healthy, and we bid farewell to Mike using the word "pimp". All that and our picks of week and five questions!

Interview DrupalEasy News Three Stories Sponsors Picks of the Week Upcoming Events Follow us on Twitter Five Questions (answers only)
  1. Learning Japanese
  2. DrupalVM
  3. Speaking at Drupalcon
  4. Chicken
  5. Before 2008 was a print designer. They had an internal site that needed update so hey, Drupal. Read "Using Drupal" from cover to cover and created the site.

Sorry about the audio quality in this episode. We had to go to our emergency recording of the call which is only two channels (our regular recording is one channel per participant) and heavily compressed.

Intro Music Subscribe

Subscribe to our podcast on iTunes, Google Play or Miro. Listen to our podcast on Stitcher.

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

Zivtech: Challenges of Front End Development

Planet Drupal - 1 July 2016 - 6:21am

With phone in hand, laptop in bag and earbuds in place, the typical user quickly scans multiple sites. If your site takes too long to load, your visitor is gone. If your site isn’t mobile friendly, you’ve lost precious traffic. That’s why it’s essential to build well organized, mobile ready sites.

But how do you get good results?

  • Understand whom you’re building for
  • Employ the right frameworks
  • Organize your codebase
  • Make your life a lot easier with a CSS preprocessor
Let’s look at each of these points.
Design For Mobile When you look at usage statistics, the trend is clear. This chart is from Mary Meeker's 2016 Internet Trends Report.

A vast array of mobile devices accomplish a variety of tasks while running tons of applications. This plethora of device options means that you need to account for a wide assortment of display sizes in the design process.

As a front end developer, it’s vital to consider all possible end users when creating a web experience. Keeping so many display sizes in mind can be a challenge, and responsive design methodologies are useful to tackle that problem.

Frameworks that Work

Bootstrap, Zurb, and Jeet are among the frameworks that developers use to give websites a responsive layout. The concept of responsive web design provides for optimal viewing and interaction across many devices. Media queries are rules that developers write to adapt designs to specific screen widths or height.

Writing these from scratch can be time consuming and repetitive, so frameworks prepackage media queries using common screen size rules. They are worth a try even just as a starting point in a project.

Organizing A Large Code Base Depending on the size of a web project, just the front end code can be difficult to organize. Creating an organizational standard that all developers on a team should follow can be a challenge. Here at Zivtech, we are moving toward the atomic design methodology pioneered by Brad Frost. Taking cues from chemistry, this design paradigm suggests that developers organize code into 5 categories:
  1. Atoms
  2. Molecules
  3. Organisms
  4. Templates
  5. Pages

Basic HTML tags like inputs, labels, and buttons would be considered atoms. Styling atoms can be done in one or more appropriate files. A search form, for example, is considered a molecule composed of a label atom, input atom, and button atom. The search form is styled around its atomic components, which can be tied in as partials or includes. The search form molecule is placed in the context of the header organism, which also contains the logo atom and the primary navigation molecule.

Now Add CSS Preprocessors Although atomic design structure is a great start to organizing code, CSS preprocessors such as Sass are useful tools to streamline the development process. One cool feature of Sass is that it allows developers to define variables so that repetitive code can be defined once and reused throughout.

Here’s an example. If a project uses a specific shade of mint blue (#37FDFC), it can be defined in a Sass file as $mint-blue = #37FDFC. When styling, instead of typing the hex code every time, you can simply use $mint-blue. It makes the code easier to read and understand for the team. Let’s say the client rebrands and wants that blue changed to a slightly lighter shade (#97FFFF). Instead of manually finding all the areas where $mint-blue is referenced on multiples pages of code, a developer can easily revise the variable to equal the new shade ($mint-blue = #97FFFF; ). This change now automatically reflects everywhere $mint-blue was used. Another useful feature of Sass is the ability to nest style rules. Traditionally, with plain CSS, a developer would have to repetitively type the parent selector multiple times to target each child component. With Sass, you can confidently nest styles within a parent tag, as shown below. The two examples here are equivalent, but when you use Sass, it’s a kind of shorthand that automates the process.

Traditional CSS


Although there are a lot of challenges organizing code and designing for a wide variety of screen sizes, keep in mind that there are excellent tools available to automate the development process, gracefully solve all your front end problems and keep your site traffic healthy.
Categories: Drupal

Nacho Digital: AberdeenCloud is gone! We have 36hs to recover your backups!

Planet Drupal - 1 July 2016 - 5:50am
What's important to learn about the recent AberdeenCloud meltdown? You can not trust your backups and site to a single provider!

Well it is all over the blogosphere, AberdeenCloud breakdown. I already read a couple of articles on the subject and I couldn't agree more with the one from annertech, only way to avoid this kind of issues is offsite backup. I would normally write how to recover from something like this, but sadly as codeenigma explained there isn't much we could do, their servers just collapsed and were gone. But now for 36hs we'll be able to recover our data.

Categories: Drupal

Materialize Actions

New Drupal Modules - 1 July 2016 - 5:05am
Categories: Drupal

Shortcode Audio

New Drupal Modules - 1 July 2016 - 3:54am

This module requires the shortcodes module.
This also works with the Shortcode for Wysiwyg module.

Categories: Drupal

Annertech: The Day that Aberdeen Cloud went Bye-bye

Planet Drupal - 1 July 2016 - 3:22am
The Day that Aberdeen Cloud went Bye-bye This is Tommy, calling from the engine room! Were you affected by the Aberdeen Cloud incident that happened on the 28-06-2016? We weren't, but I'd call that partly luck and partly proactivity. We were actually prepared for this.
Categories: Drupal

Acquia Content Hub

New Drupal Modules - 30 June 2016 - 11:00pm

Acquia Content Hub enables the distribution and discovery of content from any source to create engaging multi-channel digital experiences.

This module allows to connect Drupal site to the Acquia Content Hub service.

Categories: Drupal

DrupalCon News: Call for Papers Closing Soon

Planet Drupal - 30 June 2016 - 2:00pm

It all starts now. Every great DrupalCon session begins as an idea someone shares with our track chairs. There are only a few days left for that next someone to be you.

Categories: Drupal

Acquia Developer Center Blog: Should I Disable PHP Warnings and Notices?

Planet Drupal - 30 June 2016 - 1:54pm

Many developers who work on Drupal (or other web/PHP) projects have error reporting disabled in their local or shared dev environments. They do this for a variety of reasons: some don't know how to enable it, some are annoyed by the frequency of notices, warnings, and errors, and some don't like to be reminded of how many errors are logged.

But there are a few important reasons you should make sure to show all errors when developing:

Tags: acquia drupal planet
Categories: Drupal

Lullabot: Drupal Commerce 2.x with the "Guys" from the Commerce Guys

Planet Drupal - 30 June 2016 - 1:00pm
Matt and Mike sit down to deep-dive into the Drupal 8 version of Drupal Commerce with Ryan Szrama, Bojan Zivanovic, Matt Glamon, in addition to Lullabot's own Matt Robison.
Categories: Drupal

Cruiskeen Consulting: Drupal Camp Wisconsin - Coming soon!

Planet Drupal - 30 June 2016 - 11:09am

Drupal Camp Wisconsin is on! and will be held on July 29-30 in beautiful Madison Wisconsin. This year we will be meeting at the Chemistry biulding on the UW Campus. There are still open slots for presentations --- so please stop by at http://drupalcampwi.org or make a session proposal, or to sign up for the camp. This is always a fun camp, and it did not happen last year, so this is the year to stop by and make Drupal Camp Wisconsin a success!  See you there.

Categories: Drupal

Drupal core announcements: Drupal 8 and 7 core release window on Wednesday, July 06, 2016

Planet Drupal - 30 June 2016 - 10:31am
Start:  2016-07-05 12:00 - 2016-07-07 12:00 UTC Organizers:  xjm catch David_Rothstein stefan.r Event type:  Online meeting (eg. IRC meeting)

The monthly core patch (bug fix) release window is this Wednesday, July 06. Drupal 8.1.4 and 7.50 will be released with fixes for Drupal 8 and 7.

To ensure a reliable release window for the patch release, there will be a Drupal 8.1.x commit freeze from 12:00 UTC Tuesday to 12:00 UTC Thursday. Now is a good time to update your development/staging servers to the latest 8.1.x-dev or 7.x-dev code and help us catch any regressions in advance. If you do find any regressions, please report them in the issue queue. Thanks!

To see all of the latest changes that will be included in the releases, see the 8.1.x commit log and 7.x commit log.

Other upcoming core release windows after this week include:

  • Wednesday, July 20 (security release window)
  • Wednesday, August 03 (patch release window)
  • Wednesday, October 5 (scheduled minor release)

Drupal 6 is end-of-life and will not receive further releases.

For more information on Drupal core release windows, see the documentation on release timing and security releases, as well as the Drupal core release cycle overview.

Categories: Drupal

Facebook Instant Article

New Drupal Modules - 30 June 2016 - 9:14am

Facebook Instant Articles!

Categories: Drupal

Amazon Wysiwyg

New Drupal Modules - 30 June 2016 - 7:22am
Wysiwyg Plugin for Amazon

This module depends on Amazon module

How to configure it
  • Visit /admin/config/services/amazon
    or via menus: Configuration > Web services > Amazon API

    Fill in the configuration with your details.

    Click on Test tab and try to retrieve an item using a valid ASIN code.

Categories: Drupal

Into my Galaxy: GSoC’ 16: Port Search Configuration Module to Drupal 8 : Mid Terms

Planet Drupal - 30 June 2016 - 4:24am

I feel really excited to have cleared the mid-Term requirement for my project in Google Summer of Code (GSoC). The results of the mid-Term evaluations were announced June 28, 00:30 IST. This was the evaluation for the first phase of GSoC. In this evaluation process, set up by GSoC organisers, students and mentors have to share their feedback about the current progress of the project. Mentors need to give a pass/ fail grade. Students can continue coding once they clear the evaluations successfully.

I have been working on Porting Search Configuration module to Drupal 8. Please go through my previous posts if you would like to have a look into the past activities in this port process.

Last week I worked on testing some of the units of this module using the Php unit tests framework. Testing is an important process when it comes to any software development process. It plays a crucial role for any software. It helps us to understand the improve our software to the required level by making use of various test cases. We input various values and check whether the tests are passed according to the requirement. If any condition fails to our expectations, we need to make the required changes to suit the application needs.

Php unit tests are generally used to test some units of an application. To check whether the functions implemented gives the expected output, behaviour of the functions in various test cases, giving different types of arguments as inputs to check the errors or flaws for improving the application.

We need to install the Php unit for this process. You could follow this documentation for this process. Furthermore, they give a detailed analysis of the Php Unit Tests.

Once the installation is completed, we can start writing the unit tests for the functionalities we have implemented. The tests are generally stored in the tests/src/Unit directory of the module. The name of the unit test file will be of the format xyzTest.php. All tests are suffixed by ‘Test’. ‘xyz’ can be replaced by the functionality you are going to test.

The following is a simple test to check the sum of two numbers: sumTest.php

<?php class SampleTest extends PHPUnit_Framework_TestCase { public function testSum() { $this->assertEquals(2+2, 4); } } ?>

As mentioned in this above code snippet, we need to create a class, with class name suffixed by ‘Test’ which is an extension of PHPUnit_Framework_TestCase. Now, we need to write the tests inside as member functions. The functions starting with the name test are executed. Here we are checking the sum of the two numbers. This is a very simple demonstration.

The tests are run by using the command PHPUnit. i.e,

$ phpunit tests/src/Unit/sumTest.php

The output generated on running the above test is:

PHPUnit 5.4.6 by Sebastian Bergmann and contributors.

. 1 / 1 (100%)

Time: 252 ms, Memory: 13.25MB

OK (1 test, 1 assertion)

Stay tuned for future updates on this module port.


Categories: Drupal

Code Enigma: #AberdeenCloud - what happened?

Planet Drupal - 30 June 2016 - 1:54am
#AberdeenCloud - what happened? Language English #AberdeenCloud - what happened?

The only cloud with no silver lining.

Thu, 2016-06-30 09:54By greg


If you were an #AberdeenCloud customer, you’ll be only too aware their platform went bang on the evening of 28th June 2016. Spectacularly.

As it happens, we had spotted the lack of support response, and while there had not (and still has not, I might add - they still have a Sign Up page!) been any communication from #AberdeenCloud that anything was wrong, we were starting to get a little nervous. It took time to ask our customers what they wanted to do, collate the responses, vet a new supplier (our ISO 27001 certification requires we procure carefully), negotiate contracts, and so on, but we had got there.

Having signed a contract with Platform.sh just the day before, we were about to start migrating #AberdeenCloud customers over. Unfortunately, as it turned out, we were just a few days too late.

So what happened? Our timeline of events went something like this:

  • On 28-06-2016 at approximately 1900 UTC we got alerts from Pingdom for one of our customers on #AberdeenCloud.

  • It had happened earlier in the day, but restarting the container had cleared the issue - we figured it was something that was triggered by a Drupal cron event, but had not yet managed to investigate. So we did the same again, restarted the container. It did not come back. This was the first  sign all was not well.

  • Then another site went sideways, so we tried to restart that container. Same happened.

  • At this point we realised trying to restart containers was making things worse. To test we tried to restart the container on a development site we didn’t care about, same happened.

Right about now we realise things are not at all well with the #AberdeenCloud platform. OK, time for an emergency migration then! No one sleeps tonight! So we:

  • Raised an emergency ticket with #AberdeenCloud support (still not responded to, of course).

  • Tried to pull backups from the #AberdeenCloud backup manager (which was still available to us), but it failed for a site with no container running.

  • Tried to pull a stage backup instead, that failed too.

  • Tried to pull a backup from a seemingly still healthy site (it wasn’t healthy, it was just entirely cached by Varnish as it happened) and that also failed.

  • Tried to use `drush` to get databases, but found Drupal sites had no configuration files any more and could not connect to their databases.

And this is when something horrifying became apparent. All those daily backups #AberdeenCloud had been taking for us - and they did work, we had cause to use them just the week before - were, for some unknown reason, taken out by the same platform failure! No backups!

At this point it was time to see if we could pull anything off the running services. We noticed pretty quickly that:

  • phpMyAdmin was still running for all sites, even the ones with dead containers, so we used its “Export” feature to grab all live databases.

  • Version control was still running, so we quickly updated all codebase copies to make sure we had the latest code.

So now we have code and databases, which is good, but still no files. The containers we’d tried to restart were gone. Nothing we could do, it’s dead, Jim. So we tried a few things:

  • We started trying to contact people - we got hold of people who used to work for #AberdeenCloud to see if they could help (they couldn’t) - we sent Sampo, the CEO, a message via LinkedIn pleading for help (he still hasn’t replied, probably never will) - but we ran out of road, couldn’t find anyone able or willing to step in.

  • While the communication effort was going on, we started trying every trick we could think of to get files from “good” containers, via SSH, via the `aberdeen` command line client, via SFTP, copying files to another location to pull down, nothing worked.

  • We also tried spidering the sites using the `wget` command for Linux, to pull as many assets as possible from remaining Varnish caches, but this had very limited success.

At this point we started looking at the root cause, and it became pretty clear the mounted directories containing client uploaded files and Drupal configuration files were no longer there. You could see it when you logged into a container, but it was just a cache. If you tried to check the disk space it didn’t even show up. That storage was just gone.

But far worse, it seems backup storage depended on the exact same service! This is quite astounding really, but it seems there was no separation of service between storage of backups and storage of files and configuration. So if you lose one, you lose the other. Whereas you would expect backups would be somewhere more resilient and, frankly, more simple to access. We’d never had cause to question this before, our backups had always worked and the platform was closed source - there’s no way we could’ve known this was the case, but there you go. Cloud files gone, sites gone (because no Drupal settings) and backups gone - all in one fell swoop!

We were left with no choice but to proceed with what we had, so we:

  • Restored Drupal 6 sites to a virtual machine we had spare (I don’t think Platform.sh supports PHP 5.3, though I may be wrong).

  • Restored Drupal 7 sites to equivalent Platform.sh accounts.

  • Pulled in as many files as we could.

  • Continue to work with customers to help them recover their files and websites.

Anyway, it’s a real shame, because (unknowable backup storage flaw aside) they provided a good service for several years and the platform had proven to be very solid. It’s quite beyond me how someone can allow a business like this to fly into the ground without so much as giving customers a shutdown date with reasonable notice. It is irresponsible beyond belief, but there you go, it happened, and now we have to live with the consequences.

We, at Code Enigma, are obviously very sorry this has impacted on some of our customers. We are doing our best to help people recover their sites, automating the import of files, pulling assets from archive.org, checking support developer local copies for missing data, and we continue to chase Sampo, offering payment for missing files, though I have no confidence he’s ever going to reply.

I will post an FAQ later on other aspects of fallout from this, to help people understand the situation more clearly.

  PageHosting Service Comparison BlogDenial of Service, what you need to know BlogDesign and build a website in a day FAQMy site doesn't load for me, is it down?
Categories: Drupal

Deeson: How does the permissions system work in the Group module for Drupal?

Planet Drupal - 30 June 2016 - 1:42am

We’ve been getting questions about the Group Drupal module and how it relates to the general permission system that ships with Drupal. More specifically, the difference between group roles and user roles. So we figured we’d post a short explanation. 

Consider a regular Drupal site as a one-level thing.

There’s roles and permissions that allow you to do things, but it’s a flat structure. Either you have a permission across the entire site or you don’t. Group adds depth to that structure, allowing you to create smaller levels underneath the main one.

Inside those sub-levels you can have roles and permissions too, just like on the main level. The difference lies in the fact that they’re called group roles and group permissions and they only apply within their section of the site within their group.

Let’s use a practical example to demonstrate this. Suppose you’re building a news website and you allow John and Jane to post articles. But John only writes about sport and Jane only really knows about fashion. Yet they can both publish articles about anything. This is the default story in any Drupal website.

Group would allow you to divide the website into sections such as “Sport”, “Fashion”, “Domestic”, etc. and allow John to only publish articles in Sport and limit Jane to writing about Fashion.

This is just one of the many use cases Group can solve for you.

Interested? Try it out! It’s available for both Drupal 7 and 8, find out more here: https://www.deeson.co.uk/labs/9-reasons-group-drupal-8-awesome

Categories: Drupal

Modules Unraveled: 161 Website Audits and How to Do Them Right with Jon Peck - Modules Unraveled Podcast

Planet Drupal - 30 June 2016 - 12:01am
Published: Thu, 06/30/16Download this episodeWebsite Audits
  • What is a site audit?
  • Why would you do one?
  • Intended audience
    • New clients? Existing clients?
  • What are the goals of a site-audit?
  • How do you approach a site audit?
    • What are some other approaches you’re aware of?
  • What tools and techniques do you use?
  • How do you present the results?
  • How often should you do them?
  • What are some things to avoid?
Episode Links: Jon on drupal.orgJon on TwitterJon on GitHubJon’s about.me pageSite Audit ModuleUnused Modules ModuleSecurity Review ModuleHacked ModuleCache Audit ModuleCoder ModulePHP CodeSnifferDrupal Coding StandardsPHP Copy Paste DetectorPHP Mess DetectorPHP LOCGit StatsGit InspectorESLintESLintwebpagetest.orgGoogle PageSpeed Insightswave.webaim.orgViews Cache Bully ModuleHow to audit Drupal Sites - DCNOLATags: AuditingSecurityPerformanceplanet-drupal
Categories: Drupal

Frederic Marand: Faster Drupal sites with Queue API

Planet Drupal - 29 June 2016 - 11:35pm
These are the slides of the presentation I gave last week at DrupalDevDays Milan about the ways using Queue API can help you speed up Drupal sites, especially in connected mode. read more

Categories: Drupal

Anonymous Viewer

New Drupal Modules - 29 June 2016 - 4:51pm

Finally allows you to view that pesky anonymous user at user/0.

Depends on bad judgment.

Categories: Drupal


Subscribe to As If Productions aggregator - Drupal