The Drupal 8 core has far more features than the Drupal 7 core. Many popular contributed modules have been included in the core, including five field types.
Here are the 5 new fields in Drupal 8:
Welcome back. If you just found this, you might want to start with Part 1 before reading on.
Okay, now we’re going into our custom theme folder (that’s based off the STARTER foundation sub-theme. Check out Justin’s Blog post, on how to set that up.
So, now that you’ve got your custom sub-theme...
Drupal is fantastic at caching itself (I mean, you've gotta be with a code base this hefty). Drupal 8 will see the dawn of render cache in core which is why most metrics you see of D8 are uncached (because it's basically cheating its so fast cached). If you want to play around with Render Cache in D7, it can be done but still needs some work (Drupal.org actually runs Render Cache backport to handle comments in issue queues among other things).
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 first 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!
Not all security vulnerabilities are equal!
Some are highly critical and require immediate action (like SA-CORE-2014-005, aka Drupalgeddon, was) or your site could be irrepairably damaged and you'll have to restore from backups.
And while you should take action on any security advisory that affects your site as soon as possible (or hire someone else to do it), some security vulnerabilities present less risk, so you might choose to delay updating and focus on more important things in your business or personal life.
But how do you make that decision?
However, those labels aren't very instructive because they don't really tell you want your at risk of.
Each security advisory also includes the full set of values provided to the Risk Calculator - which contain a wealth of information about the vulnerability - you just need to know how to decode and understand it.
That's what this article is about!
Read more to learn how to understand the Risk Calculator used in Drupal Security Advisories!
I believe that the "digitalization" of the world is a "megatrend" that will continue for decades. On the one hand, organizations are shifting their businesses online, often inventing new ways to do business. On the other hand, customers are expecting a better and smarter user experience online.
This has led to two important sub-trends: (1) the number of sites an organization is creating and managing is growing at a rapid clip, (2) so is the underlying complexity of each website.
Forrester Research recently surveyed large enterprises about their website portfolio and found that on average they manage 268 properties across various channels. On top of that, each website is becoming more and more advanced. They evolved from simple HTML pages to dynamic websites to digital experience platforms that need to integrate with many other business systems. The combination of these two trends -- increasing number of sites and the growing complexity of each site -- poses real challenges to most organizations.
At Acquia, we are seeing this explosion of websites in the enterprise every day. Many organizations have different websites for different brands and products, want different websites for each country or region they operate in, or offer separate portals for their affiliates, dealers, agents or franchises. We're also seeing organizations, small and large, operate a large number of marketing campaign websites. These organizations aren't focused on scaling back their online properties but rather how best to manage them over time.
I outlined this trend and its challenges almost five years ago (see Acquia product strategy and vision) and most of it is still relevant today, if not more relevant. In this blog post, I want to give you an update and share some lessons learned.Current situation
Most larger organizations run many different types of websites. It's not unusual for a small organization to have ten websites and for a large organization to have hundreds of websites. Some of our largest customers operate thousands of websites.
Most organizations struggle to manage their growing portfolio of digital properties. It's not unusual that an organization has more than 25 different content management systems. Often this means that different teams are responsible for them and that they are hosted on different hosting environments. It is expensive, creates unnecessary security risks, poses governance challenges, leads to brand inconsistency, makes it difficult to create a unified customer experience, and more. It costs large organizations millions of dollars a year.Drupal's unfair advantage
When managing many sites, Drupal has an unfair advantage in that it scales from simple to complex easily. That scalability, coupled with a vast ecosystem of modules, elevate Drupal from a single site point solution to a platform on which you can build almost any kind of site: a brand site, a corporate website, a customer support community, a commerce website, an intranet, etc. You name it.
This is in contrast to many of Drupal's competitors that are either point solutions (e.g. SharePoint is mainly used for intranets) or whose complexity and cost don't lend themselves to managing many sites (e.g. Adobe Experience Manager and Sitecore are expensive solutions for a quick marketing campaign site, while WordPress can be challenging for building complex websites). So the first thing people can do is to standardize on Drupal as a platform for all of their site needs.
By standardizing on Drupal, organizations can simplify training, reduce maintenance costs, streamline security, and optimize internal resources – all without sacrificing quality or requirements. Standardizing on Drupal certainly doesn't mean every single site needs to be on Drupal. Transitioning from 25 different systems to 3 still translates into dramatic cost savings.The Acquia advantage
Once an organization decides to standardize on Drupal, the question is how best to manage all these sites? In 2013 we launched Acquia Cloud Site Factory (ACSF), a scalable enterprise-grade multi-site management platform that helps organizations to easily create, deploy, and govern all their sites. Today, some of Acquia's biggest customers use ACSF to manage hundreds of sites - in fact on average an ACSF customer is currently managing 170 websites within their Site Factory platform and that number is growing rapidly.
Acquia commissioned Forrester Research to analyze the benefits to organizations who have unified their sites on a single platform. Forrester found that moving to a single platform dramatically reduced site development and support costs, conserved IT and marketing resources, and improved standardization, governance, and scalability — all while accelerating time-to-market and the delivery of better digital experiences.
One of the things we've learned is that a complete multi-site management solution needs to include advanced tools for both developers and content managers. The following image illustrates the different layers of a complete multi-site management solution:
The different layers of the Acquia Cloud Site Factory solution stack.
Let's go through these individually from the bottom up.Infrastructure management
Consider an organization that currently has 50 websites, and plans to add 10-15 more sites every year. With ACSF these sites run on a platform that is scalable, secure, and highly reliable. This infrastructure also allows hardware resources to be logically isolated based on the site's needs as well as scaled up or down to meet any ad-hoc traffic spikes. These capabilities enable organizations to simplify multi-site management efforts and eliminate operational headaches.Code management
If this organization with 50 sites had individual codebases for each site, that would be 50 disparate codebases to manage. With ACSF, the underlying code can be shared and managed in one central place but the content, configuration, and creative look-and-feel can be catered to each individual sites' needs. ACSF also enable developers to easily add or remove features from their codebases for individual sites. ACSF also comes with tools to automate the process of rolling out updates across all their sites.Site management
Organizations with many sites also need efficient ways to manage and govern them effectively; from developer tools such as Git, Travis, or Behat that enable them to build, test, and maintain sites, to tools for non-developers to quickly clone and spin up sites using site templates defined by a brand manager or a digital design team. ACSF enables customers to effortlessly manage all their sites from a single intuitive dashboard. Developers can create groups of users as well as sites allowing certain users to manage their dedicated domain of sites without stepping over other sites. Non-technical content managers can quickly spin up new sites by cloning existing ones they have access to and updating their configuration, content, and look-and-feel. These features allow organizations to launch sites at unprecedented speed inherently improving their overall time to market.Content sharing
Finally, I should mention personalization. For a few years now we have been developing Acquia Lift. Acquia Lift builds unified customer profiles across all your websites, and uses that information to deliver real-time, contextual, and personalized experiences. For instance, if the organization in the above example had 50 websites for each of their 50 different products, Acquia Lift can present relevant content to its users as they browse across these different sites. This enables organizations to convert anonymous site visitors into known customers and establish a meaningful engagement between them.Conclusion
I believe that the "multi-sites era" will continue to accelerate; not only will we see more sites, but every site will become increasingly complex. Organizations need to think about how to efficiently manage their website portfolio. If you're not thinking ahead, you're falling behind.
This tutorial should be useful for those who are interested in Symfony web development. In Symfony, there are many console commands to help you in your work. We will consider the most frequently used Symfony commands. For example, the cache cleaning command:Read more
After a month of Drop Guards closed beta we aggregated the most important business benefits from our beta testers. We want to share those benefits with you:
1. Focus your capacity
As a manager of a company one of your main activities is to hold distractions off your team. You will try to create an environment where your team can focus their time on their work and what they can do best. So how does Drop Guard help you here?
Drop Guard will monitor your websites for new updates. The configuration is very flexible so you can adapt Drop Guard to your workflow easily. What will happen, when you read that there is a new security update for Drupal? You can call your customer and tell them that their site is up to date. Automatically. And what will happen at your team? They will be glad because they don't need to loose their current focus and switch over to updating all your client sites. You will safe time and money and you will relieve your team.
Drop Guard will even take care about the patches that might be a part of your project's modules. The developer does not need to look through all the patched modules to update the website. Those patches will be detected by Drop Guard and they will be reapplied after the update automatically.
2. Create sustainable monthly revenue
Customers still need support after a project has been released. The services you offer could be ongoing user support or continuous update support with a SLA for security updates. Sometimes those security updates need to be applied very quickly so you'll need someone who monitors those sites and their available updates all arround the clock - even at the weekend. With Drop Guard you can sell this SLA service without the need for developer to monitor those sites. The updates will be processed automatically in a short time. It will help you scaling your business and keep sales fluctuations away from your business by adding monthly recurring revenue.
3. Improve the satisfaction of your customer and your team
Drop Guard helps your support team to keep your websites updated and secure. It will grow your monthly recurring revenue and your development team can focus on more important tasks in your complex projects. If updates are available there is no need to tell "Our developer will take care of it when they are free" - it will be "Drop Guard will take care of it automatically".
We're intrested in every critical input around the topic "can automatic updates improve the Drupal ecosystem?". We'd like to have a constuctive conversation about these three topics:
- Create a monthly recurring revenue with Drupal update services
- Optimize the customer relationship by fast and uncomplicated updates
- Save time so that your team can focus on important project work
We're looking forward to a dialogue with you!
We're also represented at DrupalCon in Barcelona from September 21st to 25th, you will find us at booth no. 605 – visit us and discover our prepared surprise for you!
With DrupalCon Asia planning kicking off, we took some time last week to loop the community in and let everyone know where we are as well as how you can get involved in the Con!. You can watch a video of the webcast that we hosted here.
If you're interested in getting involved, there are many ways that you can do so:
We're excited to announce another Greater Los Angeles Drupal special event: Silicon Beach Drupal at Flipagram. This event focuses heavily on the needs of startups, innovative ways to use the Drupal framework and related technologies, and the nuts and bolts of product development and customer acquisition.
This time we're meeting from 7-9pm Pacific Time on September 17, 2015, and are being hosted by our friends at Flipagram in Century City, CA. There is free parking, free food and beer, ping pong, and like-minded people to meet and mingle with.
There are two main presentations at this event, How to Host on the AWS 12 Month Free Tier and Flipagram’s UI/UX Problem Solving.
How to Host on the AWS 12 Month Free Tier
At this special event, Dylan Burris (wwwprola on Drupal.org), Lead Developer, will show you simple yet robust ways to create high traffic, business-grade websites on Amazon Web Services' 12 month free tier, further demonstrating the Drupal-based AWS management platform he introduced during his lightning talk at the LA Drupal meetup in August, 2015.
We'll show you our Drupal-based point-and-click tools for building infrastructure optimized for popular content management systems, including Drupal and WordPress, and effective workflows, which are built in a matter of minutes and will sustain your needs for the life of your website.
What's Amazon AWS Free Tier?
Amazon Web Services (AWS) offers new customers 12 months of free hosting. We’re going to show you simple ways to take control and build a web hosting platform you can start using in a matter of minutes, but will continue to scale with you in a professional environment.
This web hosting platform will give you freedom to create in your own personal way, and keep you and your clients happy with high performance, scalable and resilient infrastructure for the life of their website.
Even if you’re already familiar with AWS, you will discover new, simpler ways to create websites and manage resources. And, if you’re not familiar, members who show up will receive continued support for answering questions through our website.
Flipagram’s UI/UX Problem Solving
Looking to work with a company to solve meaningful problems? Check out their jobs and meet Flipagram decision makers at the event!Call for Presenters!
Flipagram is in the big red building on Santa Monica Blvd. and Beverly Grove. Parking garage entrance is next to SmithHouse's "SH" logo. Parking will be validated!
10351 Santa Monica Blvd Suite 310
Los Angeles, CA 90025
Flipagram makes it incredibly easy for anyone with a phone to create and share compelling visual stories using their photos, videos and music. With tens of millions of monthly users worldwide and growing, Flipagram is fast becoming the world’s favorite app for telling amazing short-video stories that can inspire, entertain or inform -- anyone, anywhere.
To learn more about Flipagram, see the Flipagram website, download it for Android or iOS, or see Flipagram Raises $70M, Scores Record Label Deals Thanks To 30M+ Music Hungry Users on TechCrunch.Tags: FlipagramSilicon Beach DrupalPlanet Drupal
The Buzz is all about PHP 7, and rightly so, it's pretty incredible some of the performance metrics its pulling even relative to Facebook's HHVM. Brad Fisher wrote about a one-line installer to get up and going with PHP 7 if you want to play around with it. But then reality sets in...
This week one of our members came up with an interesting question about the Webform module. They wanted to redirect users to different pages depending on their answers.
Here's how you can make that work using Webform conditionals.
In the first installment of this series we started our journey towards creating some simple but powerful functionality. The goal we set was to have the possibility to load a form on each node page and to be able to choose which form type should be used on the different node bundles.
The first step is done. We created a custom plugin type called ReusableForm already featured with a base plugin class that new plugins can extend. Additionally, we saw that each plugin will interact with a form class that is defined in their annotation. And like with the plugins, we also created a base class new forms can extend.
It follows to see how we can configure the core node types to use one of the plugins defined on the site and how to render the relevant form when viewing the node. But first, in order to have something to work with, let’s create our first ReusableForm plugin that uses a very simple form.Our first plugin
Inside the src/Form folder of our module, create a class called BasicForm.php (or whatever you want to call it). Inside, we can have this simple form definition:
Continue reading %Drupal 8 Third Party Settings and Pseudo-Fields%
Each year the Sydney Drupal Community puts on a two day "DrupalCamp", generally held over a weekend at a location where attendees can get away from it all and get down to some serious Drupal talk.
Brad Fisher (@bradallenfisher) started a #purespeed channel in our slack channel a few months back. Since then, we’ve both been doing a lot of work to tune every aspect of drupal page delivery. What will follow is a series of blog posts about tuning every part of the stack. We’ll cover:
There’s many dirty little secrets in Drupal 7 core’s API when it comes to inconsistencies and oversights. It’s a big part of why so much care is being placed in D8 and its taking so long, because people realize this is a platform that’s used for the long haul and core decisions today will have lasting impacts a decade from now.
One of the options in Nittany Vagrant is to build a local, development version of an existing Drupal site - copying the files and database, then downloading it to the Vagrant VM. Its is pretty straightforward, but there is the occasional trouble spot.
Here is a short video of how to do it.
I recently had to switch profiles for this website. In the process of doing that, I immediately afterwards said “wow, I feel like other people have had this issue”. Sure enough they have… on this blog early last year by our own @aitala in the post How to Remove Drupal Install Profile.