The surest way to corrupt a youth is to instruct him to hold in higher esteem those who think alike than those who think differently.
Content over Immersion: Using Kinect instead of a VR headset and how it worked better for us - by Zac Zidik
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 ....
.... 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
One of our members asked how to create a map with custom points to highlight specific areas.
In this tutorial we will show you how to create custom maps by using the Image-Maps online tool.
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.
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.
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:
Migrate manifest provides a Drush command for running migrations using a manifest format.
Originally this functionality lived in Drush. It was briefly maintained in Migrate Tools as part of Migrate Plus but due to lack of interest by the maintainer it has been split into a standalone project.
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.
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.
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.
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!
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.
"Debugging is actually all about finding the bug. About understanding why the bug was there to begin with. About knowing that its existence was no accident." ...