This is not a test. This is reality. World-wide.
The monthly Drupal core bug fix/feature release window is scheduled for this Wednesday, October 7. A Drupal 7 core release is planned for this window (since there hasn't been one in a while), but it will not come out on the scheduled date. This is due to various scheduling issues, and also to give more time to get a few more patches committed in time for the release.
The delay will push the release out by a couple days, or possibly into early next week. I will post a new announcement once the code is frozen and a release date has been set.
This release window is for a bug fix/feature release only (no security fixes). Upcoming release windows after this one include:
- Wednesday, October 21 (security release window)
- Wednesday, November 4 (bug fix/feature release window)
One of our members needed to fix an issue for a site in Internet Explorer 11. At the same time, he wanted to avoid changes that might mess up other browsers. The site looks fine in Firefox, Chrome, Safari and Opera.
In this tutorial we will show you how to add custom CSS for just Internet Explorer 10 and 11.
With the call for papers officially open, we wanted to take a moment to give you all of the details you should know about sessions: what tracks we are offering, how to submit an awesome session submission, and how session selection works.
If you want to communicate with readers on a blog, the best way to achieve this is by setting up comments. If you're happy to deal with spam and the occasional troll, then comments are great for communicating with readers and fostering a community.
The functionality has changed a lot in Drupal 8. In Drupal 7, the comments system was fairly rigid. You could only use them on content types and only have a single comment type. If you needed to support multiple comment types like review or feedback, you were out of luck.
In Drupal 8, the comments system has been rebuilt. They can be attached to any entity type by adding a "Comments" field. You can also now have different comment types. This allows you to do all sorts of things like having public and private comments on a single content type.
In the last tutorial, we created a Blog content type and added fields to it. Let's continue working on it by adding support for comments. We'll configure the user permissions so that comments can be submitted anonymously, but will need to be approved before they're published.
Appnovation announced an additional $11,500 to support the D8 Accelerate project efforts to help move Drupal 8 from the initial beta to a full release.
If you find yourself going out of way to keep your accounts secure and care about your website support, you are on the right page, reading information you need. Everyone, who has their own accounts in Facebook, Gmail, Twitter, LinkedIn or any other network, is concerned about protection against social media threats. Here in this article we are going to suggest some effective tips to help to reduce the risk of hacker attacks.Read more
This past week, a new open database for economic, demographic, and market data was launched called Vizala. Vizala is a Drupal site and at the core of its user experience is a module called Views Save that allows users to personalize the site by saving views of data that are meaningful to them.
Views Save takes all of the functionality and flexibility provided by the Views module and its extensions, and enhances it by allowing users to save/bookmark any view of content. Basically, if Views can display it, then it can be saved with Views Save. It works with any configuration set by administrators or users including exposed filters, sorting, and any options added by extensions. Views Save works with all Views display types, plugins, handlers etc.
When a view is saved, it becomes an entity in Drupal. This allows you to use Views to generate lists of saved views per user. Views Bulk Operations (VBO) can be used to allow users to manage their lists. Saved views being stored as entities also allows you to take take advantage of a lot of other Drupal functionality including Fields and content permissions. Future development may involve Rules integration to allow alerts to be created that are based on saved views.
Example use cases for Views Save include …
- Sites that allow users to customize and save maps
- Analytics sites that allow you to save any view of the data, and create recurring reports
- When notifications are not required for a site, it could also be a replacement for the Search API Saved Searches module
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:
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.
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
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.
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
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
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.
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.