flink: Views Aggregator Plus revisited: new Economics and Market Research Site

Planet Drupal - 11 hours 31 min ago

In a previous post, we reflected on how our Drupal module Views Aggregator Plus came about: "….that [government] project was eventually put on ice, but during its course another module baby was born. We called it Views Aggregator Plus and set her free in Drupalland. It seemed a waste not to share it."

Views Aggregator Plus now enjoys thousands of installs across the world. There is a 90 second video about it on YouTube and quite a few mentions on Google etc. To us it’s lovely that our efforts didn’t go to waste.

The three real-live examples described in the previous post highlighted the module’s row aggregation capability. This is where Views result rows are grouped and compressed based on the identical values of one column, while at the same time applying aggregation functions (like sum, average, enumeration) on the other columns -- the project page explains this better with an example.
This type of data summary can provide useful insights on the entire dataset.

But Views Aggregator Plus does straightforward column aggregations easily too.

The following example was mentioned to us the other day. It can be found on Vizala.com, a new online database for economic, demographic, and market research information.

If you look at these examples ....

Industry output by country
Agricultural land by country
Total international trade by country
Imports by industry & country

.... you can see that the grey aggregation row (near the the top) provides totals and averages for any year that is selected.
Also, no matter what configuration of exposed filters is set by the user, VAP automatically updates the totals and averages for that group of countries.

* * *

Image of aggregation taken from Wikipedia, "Pheromone"


File under: Planet Drupal

PreviousNext: Logging in a Docker Hosting World

Planet Drupal - 14 hours 55 min ago

Docker is reinventing the way we package and deploy our applications, bringing new challenges to hosting. In this blog post I will provide a recipe for logging your Docker packaged applications.


Drupal CMS Guides at Daymuse Studios: 10 Web Services and Tools for Drupal Developers and Agencies

Planet Drupal - Mon, 2015/10/05 - 11:30pm

You're wearing too many hats in your web development firm. Whether you're a freelancer or agency, reduce frustration and cost with these 10 web services.


J-P Stacey: Freelancers unite! (briefly) at Drupalcon Barcelona

Planet Drupal - Mon, 2015/10/05 - 9:33pm

Continuing the trend from Drupalcon Amsterdam, I hosted an informal BoF session at Drupalcon Barcelona, for freelancers to chat among themselves. As a lot more of Drupal's space is being occupied by big players these days, I like to think this helps "single players" carve out a space at the conference.

My notes are publicly available, as a g.d.o wiki page no less: so I won't add to them too much here. However, it's interesting to see that:

Read more of "Freelancers unite! (briefly) at Drupalcon Barcelona"


Unimity Solutions Drupal Blog: Multi Domain MultiLingual Corporate Site Project

Planet Drupal - Mon, 2015/10/05 - 8:30pm

This Blog covers the highlights of how Drupal could be used effectively to build a multi domain, multilingual site for a large Multi National Company.


Another Drop in the Drupal Sea: Build a Website That Works for You!

Planet Drupal - Mon, 2015/10/05 - 6:45pm

No matter what tool you use to create a website, you still need to put time into planning before you actually start designing and building the site. If you rush to start with the design and build process you run the risk of having a project that takes more time and money than desired and generates less of a return on investment. There are key questions you need to answer to ensure that you create a clear and comprehensive website definition document.

read more


Drupal Watchdog: You Know It Don't Come Easy

Planet Drupal - Mon, 2015/10/05 - 6:36pm

Drupal has long been described as a content management system for developers. It’s been criticized for its Drupal-centric jargon and characterized as unfriendly to inexperienced and experienced web site creators alike. In the DrupalCon Barcelona 2007 State of Drupal address, project creator Dries Buytaert stressed the need to focus on Drupal’s usability.

Not long afterward, the first formal usability study took place at the University of Minnesota, just after the release of Drupal 6 in February, 2008. Several studies of Drupal 7 were conducted in subsequent years. In June, 2015, community members returned to the university for Drupal 8’s first formal evaluation.

These formal usability tests are just one metric about Drupal’s user experience. Anyone who has introduced a new site builder to Drupal, or tried to help a Dreamweaver-savvy friend get started, has a pretty good idea where existing major challenges lie. Drupal.org has methodology suggestions to empower anyone to conduct their own studies, which can take place any time. New features in Drupal 8 are evaluated as they’re introduced, as well. For example, the Drupal User Experience team has conducted more than 70 informal sessions on Drupal 8-specific changes. The formal studies, however, lend a certain gravitas to recommendations for improvements; as we return to Barcelona for DrupalCon 2015, the history from formal evaluations provides a valuable metric to reflect on how far the project has come.

When I was invited to attend Drupal 8’s study, I was eager and hesitant. Eager, because who doesn't want to geek out on eye tracking feedback and all the experience-capturing equipment while spending focused time with key players who are working toward sorely needed improvements? Hesitant, because four years into the development of Drupal 8 seemed like a difficult time in the cycle to introduce meaningful change.


myDropNinja.com: Understanding Drupal Security Advisories: Vulnerability type

Planet Drupal - Mon, 2015/10/05 - 4:09pm

Every Wednesday, the Drupal Security Team publishes "Security Advisories" (or SA's) to tell users about security vulnerabilities in Drupal core and contrib modules, with advice on how to solve the issue so that their site is secure.

This is the second in a series of articles about how to better understand all the information in a security advisory, so that you know how to take the appropriate action for your site!

There are several different types of security vulnerabilities, each with a cryptic (and highly technical) name like Cross Site Scripting (XSS) or SQL Injection.

There's plenty of technical articles on the internet explaining what those mean from a coder perspective, including how to prevent them (by writing better code) or even how to exploit them.

But what do they mean for you, the site builder or site owner?

The most important question for you is: If an attacker exploits your site with a particular vulnerability, what will they be able to do to your site or users?

Of course, you should take action on any security advisory that affects your site as soon as possible (or hire someone else to do it). But what could happen if you didn't?

Some vulnerabilities would allow an attacker to completely take control over your site, whereas others would only allow them to access some non-public data. How can you tell which are which?

Read more to learn how the different vulnerability types could impact your site or users!


Drupalize.Me: Meet Drupal Site Builder Scott Wilkinson

Planet Drupal - Mon, 2015/10/05 - 3:02pm

In this Drupalize.Me interview, we interview Scott Wilkinson, a builder of Drupal sites that solve problems for his freelance clientele. This interview is part of an ongoing series where we talk with a variety of people in the Drupal community about the work they do. Each interview focuses on a particular Drupal role and this interview with Scott focuses the site builder role, filled by a person who builds Drupal sites by expertly piecing together and configuring modules, themes, and settings.


ERPAL: Starting projects with Drupal 8 - Our strategy in 4 steps

Planet Drupal - Mon, 2015/10/05 - 12:01pm

We are finally almost there to release Drupal 8 RC1. For us, the release candidate means that Drupal has a stable API, a feature freeze and "should" be free of critical bugs as far as there are no new ones found. That counts for Drupal8 core. We will start with Drupal 8 projects from the release of RC1. The question is only: How to create estimations for a system we, honestly spoken, don't know yet with the same depth of details as we know Drupal 7. There are so many pitfalls related to the decision making of Drupal 8 architectures. As we usually need many contrib modules in our Drupal applications, and this will not change in Drupal 8, they are not yet ready and stable enough for a bug free experience in our development team. So we are all in a difficult situation where we want to start with Drupal 8 from now on the one side but want to be able to estimate projects reliably on the other site. There needs to be some trade-offs which I want to discuss in this blog post - so please feel free to add your thoughts in the comments below.


1) Focus on Drupal core and REST

Drupal 8 core provides already so many features we need for data queries, data structure and user management. Nevertheless there are many useful contrib modules out there that are needed to render the query results in the way we need it (formatter). Some are already ported, others have not even started to be ported to Drupal 8. Struggling with bugs in contribs can take a huge amount of time in projects. That's normal as we all miss the experience with new "things". To prevent our team from estimation failures, we will start with the headless approach in Drupal 8. We've already made our experience in the last year using Drupal 7 headless and it works well. This means that for applications or content sites where no requirements are against this approach, build our own frontend in HTML/CSS/Javascript to be independent from most contribs.


2) Try to split projects

The bigger the project we want to build with Drupal (not only Drupal 8) the bigger the risk. As in Germany most clients want fixed prices for their projects, we need a fine-grained planning of small feature junks. Keeping project requirements as small as needed reduces the risk to oversee some details that will crash your estimation during the development. From an agile perspective small development steps with detailed requirements reduce also the risk to build a product that nobody needs.


3) Give some discount to contribute

We will offer our clients an up to 10% cheaper price if they pay us by the hour and allow us to fix bugs in core and contribs. This helps us to contribute and improve the code base of Drupal 8 and contrib modules. Our clients as well as the community will benefit from a fast growing and stable code base in the future as they put their strategy on Drupal 8.


4) Update early and often

Whereas the update frequency in Drupal 7 becomes slower, Drupal 8 is almost there and as more and more people will use Drupal 8 and contrib modules, the more bugs will be reported and hopefully fixed. This means for us that we need to update early and often to see code and feature changes early and react on them. Keeping modules out-dated for a long time, even for none security related updates will bring additional risk for a broken site. The bigger the difference between your current code base and the latest release, the bigger the risk that your site will break with your update. The same rule as working with GIT in a team Update / GIT pull early and often and fix issues immediately. That's why we integrate Drop Guard also in the process of our on-going development and not only in the deployment process of critical security updates. With the right setup, we don't need to care manually about our update workflow. Drop Guard will do. You can start with Drop Guard for free during our beta period and automate updates as well.


InternetDevels: Configuring Grunt for compiling SASS/LESS to CSS

Planet Drupal - Mon, 2015/10/05 - 11:27am

SASS and LESS preprocessors make front-end development much easier. To compile them to CSS automatically, you can use Grunt.js. Let’s see how to do it through the example of Ubuntu OS.

1. sudo apt-get install npm

Install npm (package manager for node.js)

2. sudo npm install -g grunt-cli

Install grunt-cli to run Grunt in any directory if it is there (this command does not install Grunt).

Read more

David Corbacho: SVG in Drupal, an overview

Planet Drupal - Mon, 2015/10/05 - 11:15am

This blog post is a follow-up of DrupalCon session Next Generation Graphics: SVG.
Drupalcon Barcelona has been a blast for me, I met a lot of old good friends and it recharged my Drupal batteries. Some people has asked me about the slides of my session. Sorry for the delay, I was knocked out by the drupalflu. It was not a myth. Here is some material and thoughts about SVG session:

Me, pretending not to be nervous:


See the slides at dcorb.github.io (with animated gifs and page transitions. But non-clickable links)

Slides at slideshare.net with clickable links, no gifs:

Next generation Graphics: SVG Drupal core and SVG. You can help

Some notes:

Drupal 8 has 79 SVG files in core at the moment. Most of them are SVG icons from ry5n's Libricons used mostly in the toolbar.

Drupal 8 themes by default will look for a "logo.svg" file in the theme folder, instead of "logo.png". See Change record.
This change was introduced at the same time that we were converting the Druplicon logo from PNG to SVG.

There are plenty of graphic assets in Drupal core that could be converted to SVG, starting with the throbber icon. I'm not sure after Drupal 8 hits RC1, if still would be possible to convert them, though.

And if you have a great idea for using a SVG sprite technique to avoid 17 HTTP individual requests! for admin users, please help here.

Finally, check out the SVG Guidelines meta issue, where James Wilson specially, has collected many useful advices to get your SVG in shape.

SVG Community

I created a Twitter list of SVG Experts, if you are interested. A lot of fresh relevant information on SVG, quirks, tips and demos they share daily, that can't be found anywhere else. Some are SVG Working group members, some are developers working on SVG browser implementation, some SVG web developers, and some are creative people testing the limits of SVG in an artistic way.


OpenLucius: Update OpenLucius 01-10-2015 | 10 new teamwork features

Planet Drupal - Sun, 2015/10/04 - 9:46am

Yes, we did it again! After some weeks of hard work, lots of coffee and allnighters we released a new version of our Drupal distro OpenLucius. These are the most important new features: 

1. Notifications

In the main menu you'll see a notification center permanently, also on mobile. You'll receive notifications of following actions:


Cocomore: DrupalCon Barcelona 2015 from mtunay

Planet Drupal - Sun, 2015/10/04 - 12:00am

DrupalCon Barcelona 2015... It was a really successful event again.
There have been more than 2030 people attended the Con.


Drupal core announcements: Drupal 8 "rc target" versus "rc deadline" issue tags

Planet Drupal - Sat, 2015/10/03 - 8:49pm

A quick note for core contributors regarding Drupal 8 issue tags related to the upcoming release candidate phase:

rc deadline issue tag
Issues that are not critical but can only be committed before the first release candidate is released (e.g., issues that change translatable strings or APIs). If they're not finished by the time the release candidate is ready, they must either be postponed to Drupal 8.1.0 or Drupal 9.
rc target issue tag
Rare! Issues that are not critical but can committed during the release candidate phase (for example, documentation changes, certain coding standards improvements, or other issues at committer discretion). Issues with this tag must have committer approval (so check with a committer before adding it).

More information on Drupal 8 release phase issue tags.


Janez Urevc: 1st Drupal 8 media virtual sprint was a success!

Planet Drupal - Sat, 2015/10/03 - 9:51am

On Friday, 2nd Oct 2015, we organized the first virtual media sprint. Four sprinters showed up and worked on D8 media issues.

First a bit of background

At Examiner.com we get an entire day to spend (along with contributions that we do as part of our regular work) on community contributions every other week. We call it "Drupal day" and we love it! It is our way of saying "Thank you!" to the community. We understand that we wouldn't be as successful as we are without incredible efforts that are invested in Drupal and other free software projects we use.

We are currently working on a very cool D8 project where we heavily use modules from media ecosystem. I might write another post solely about that in the near future. My companies' need for solid media handling solution aligns very nicely with my personal interest in the same field. As a result of that I spend most of my Drupal days on improving media ecosystem and thinking about it. Having a day to focus on things that excite you is great, but what if there would be more people joining?

This is when idea for virtual sprint was born. I published the event on our group and invited everyone to join me.


On the actual date three other sprinters joined me:


OSTraining: CustomError Module for Drupal 403 and 404 Error Pages

Planet Drupal - Sat, 2015/10/03 - 2:44am

We previously wrote a tutorial on how to create custom 403 and 404 pages in Drupal.

That tutorial used Drupal's built-in functionality, but that approach does have a few disadvantages.

So today we'll look at another approach, the CustomError module.


OSTraining: How to Install a Drupal Module - Video Tutorial

Planet Drupal - Fri, 2015/10/02 - 10:14pm

Too often we assume that some things are plainly obvious. However, for a brand new user to Drupal, knowing the best practices for Drupal site creation is a must.

This video tutorial will cover the basics of installing a new module in Drupal 7.


Drupal Association News: 0 Drupal 8 Critical Bugs? Here's What Comes Next

Planet Drupal - Fri, 2015/10/02 - 8:30pm

Everyone’s excited for Drupal 8 to come out. Now that we’re flirting with 0 critical bugs, we wanted to give a shout out to everyone who has put their hard work and love into building Drupal 8. We’re almost to the finish line, and everyone deserves hugs and high-fives for all their amazing work.

We’re looking forward to the announcement of a Drupal 8 release candidate as soon as October 7, and we’re working hard to put together materials that everyone can use to shout from the rooftops that Drupal 8 is in its final stage of development. We’ve still got a lot of work ahead of us, but the Drupal Association feels that now is a good time for our community to pause, take a deep breath, give each other pats on the back, and look at what the future holds.

Our communications plan

We’ve fielded a lot of interest in spreading the word about the Drupal 8 release candidate and the eventual release of Drupal 8. We’ve got a plan that we’re excited about, and we’re hoping for help from the community. The more we can all create content about the specific features in Drupal 8, the better! We’d also love to share content made by our community that speaks to different audiences — for example, why Drupal 8 is the best platform for government or university websites. Over the next few weeks, we hope to add our community’s amazing content to the Drupal 8 landing page.

Here are a few other ways you can help:

  • Planning on hosting a release party? Share the details and we'll help spread the word about your event.
  • Are you already building sites with Drupal 8? Share a link in social media and tag it #madewithdrupal8. You can also add it to the list on groups.drupal.org.
  • If you have demos, white papers, blog posts, or some other materials that talk about the virtues of D8, share it on social media and tag it #drupal8rc.

We couldn’t be more excited for Drupal 8. We’re in the last leg now of huge effort and we should all be tremendously proud of ourselves. Big thanks especially to our amazing Core Maintainers and all of our wonderful contributors who have worked hard on the project.

Drupal 8 artwork by Paul Johnson (pdjohnson) and CTI Digital


Gbyte blog: Drupal 8 SEO: Simple XML Sitemap module

Planet Drupal - Fri, 2015/10/02 - 8:10pm
The Simple XML Sitemap module was originally created by gbyte as a temporary replacement for the non-functioning Drupal 8 XML Sitemamp Module. After putting some more work into it however, we decided to use it for some of our future projects, as it is very lightweight and simple to use.