Ever fall in love with a lie? Ever fall in love with a lie? Ever felt a gun for the trigger? Ever gone so fast you could die?
Drupal 8 is here and ready to use right now.
However, not all of the contributed modules are available yet. That includes Backup and Migrate which was the most popular way to backup and restore Drupal 7 sites.
These four videos, sponsored by the excellent team at InMotion Hosting, offer a backup and restore solution that you can use with Drupal 8 today.
Association websites should be built to handle everything from membership drives to billing activities. Having a website by itself isn't enough; associations also need robust member management databases running behind their websites. There are many vendors who specialize in products that meet this need. These products are commonly referred to as an Association Management System (AMS) and it's rare to find a large organization that doesn't use one.
The Migrate team would like to finish up the Migrate subsystem for next month's release of Drupal 8.1.0. They've collected a number of issues for the upcoming global sprint weekend:
There are issues available for all levels of expertise. If you need help, the Migrate maintainers are in #drupal-migrate on irc.freenode.net as usual and are happy to answer questions.
ImageX Media: Can These "Under the Radar" Keyword Tools Help You Optimize Your Content Marketing Strategy? We’ll Help You Find Out.
Thanks to new innovations in the search engine optimization space, there’s more tools than ever before. This article explores 5 powerful keyword research tools that might not even be on your competitors’ radar yet.
We had a discussion in one of our previous blogs that Drupal 6 is “dead”,
however if you’re a site owner and still not sure whether you need Drupal 7,
we’ve prepared this article specifically for you.
This blog post is part of a series on everyday tools and strategies for code review, drawn from Drupal contribution experiences. xjm is a Drupal 8 core maintainer and release manager.
If you have spent much time developing software with others, you've probably asked yourself some of these questions at one time or another:Tags: acquia drupal planet
This year, DrupalCon North America heads to New Orleans, and I can't tell you how excited I am. Together with all the other members of our local Louisiana Drupal user group, we are truly looking forward to hosting the Drupal community as much as you all are excited to come experience everything New Orleans has to offer. For those visiting for the first time, I hope your expectations are exceeded. For those of you who are familiar with New Orleans, we welcome you back, and I hope you will be comforted with old haunts.
There is a discussion underway about adopting a similar release schedule for Drupal 7 that Drupal 8 is using (i.e., a six-month feature release schedule, with pseudo-semantic versioning).
This is not a major change to current policy, but it would mean that new features or other potentially disruptive patches to Drupal 7 core would be limited to two windows per year, with the corresponding releases given a round number (for example, Drupal 7.50, Drupal 7.60, etc.) to indicate their importance.
I'd like to bring the discussion to a close soon so that if we do adopt the new schedule, the first such release can be slated for April 20 (the same day as the Drupal 8.1.0 release).
If you have any feedback on this proposal, please try to comment within the next week here: https://www.drupal.org/node/2598382
Sometimes the content improves accessibility but is considered visual noise (says the designer).
So as the developer you have a lot of ways to... pat the cat(?) But not all cats react the same to being patted :D
It’s strange but true: seven years after the PDF reference was published as an ISO standard (ISO-32000-1), there are still developers who think that the Portable Document Format is a closed document format owned by Adobe. PDF is often perceived as a strange, impenetrable document format. It’s high time we bury that idea and take a look at what’s going on in the world of PDF today...
This will be a momentus year for Drupal.
Some people may be predicting a year of security vulnerabilities. I believe we have a year of innovation ahead of us.
Drupal's ecosystem of contributed modules is playing catch-up since the release of version 8. It has been years since CCK and Views were just experiments in the contrib module space. They are now established as foundation of Drupal core. Contrib (the wider community of Drupal developers) can now get back to innovating.
"Get back to innovating" isn't much of a prediction. I thought about it some more and came up with three things I think are likely to happen in 2016...CMS-as-a-Service
The era of the monolythic, does-it-all, CMS is coming to an end. The Drupal community talk a lot about progressive decoupling  . But, the idea of a fully decoupled backend is becoming established in other areas. Services like Contentful already provide a fully decoupled, headless CMS.
Systems become decoupled, we move to a microservice architecture, and evaluate server-less options. It is conceivable that a Content API could become part of the infrastructure. Amazon are the leading Infrastructure-as-a-Service provider. A Content API (or CMS-as-a-Service) would fit in their suite of cloud computing services.
I did an experiment recently where I put Amazon's API Gateway in front of an EC2 instance running Drupal. This gives a more robust API on top of Drupal 8's Rest support. Monitoring, traffic management, and flexible security controls are standard. This approach offers several advantages, including: Swagger support; CloudFront caching for performance; and input/output translation with data models defined with JSON schema.Acquia IPO
Going public was always on the cards for Acquia, but they said they are in no rush to IPO. This could be the year. Adoption of D8 will being changes to the user base and continued adoption at the enterprise level.
This will be accompanied by more consolidation in the Drupal world. One of the biggest risks I see is with Drupal companies taking on bigger projects. A single client becomes a large contributer to their revenue, in some cases I've heard as much as 70%. This is a risky situation to be in, if you rely on one client for a majority of your business. The solution is for Drupal companies to come together to form larger entities.
This is just a continuation of an existing trend. Wunderkraut, was the most high-profile merger in the community. Followed by many more, involving companies such as FFW, MediaCurrent, Phase2, and i-Kos.Composer Support and Decoupled Components
Composer support in Drupal needs some work. There are some big wins to be had by embracing the Composer (and Packagist) workflow.
Commerce Guys are leading the way with Drupal Commerce. They have been factoring out components into separate libraries. Other PHP projects beyond Drupal are making use of them, and contributing to their development. Expect more contrib projects to factor out separate PHP packages of re-usable code. Then Drupal modules become just a thin layer of glue.
There has been a trend for PHP Frameworks to decouple their core components. The Symfony Components split from the full stack framework has meant much wider adoption. They are used in many PHP projects, including Drupal.
PHP-FIG exists to promote interoperability between frameworks. This year will see further initiatives to clean up Drupal's code. Such as, removal of anti-patterns like service locator. The eventual aim will be to decoupling components from Drupal core.
Can you imagine using Views on a non-drupal project?
The process of debugging can be a difficult one, and the process of troubleshooting performance even more so. Luckily there are some great tools out there to help with improving the performance of web applications. Previously I wrote about generating flamegraphs from XHProf to visual stacktraces and identify bottlenecks. Flamegraphs are very helpful, but still require you to setup XHProf, download the tools for making the flamegraph SVG, and appropriately change your code to save the XHProf data. Luckily there is one of my favorite tools, Blackfire, that provides continuous PHP performance testing.
One second can define a conversion or not, and this is highly critical when it comes to eCommerce. Bottlenecks can happen in your catalog, viewing products, or even the Drupal Commerce order's life cycle. A great example can be found on this Drupal commerce issue: https://www.drupal.org/node/2653904. It's a patch to improve the deletion of line item references from orders to cut down on number of saves for orders. There's profiling done with both XHProf and Blackfire.What is Blackfire?
What about Blackfire makes it my favorite? Blackfire provides on-demand profiling, unlike XHProf, which is always collecting data. Blackfire has a PHP extension called Probe that collects raw performance data when requested. Then the Agent sends that data to Blackfire's website for processing and viewing. Companion is a browser extension (Chrome only currently) that will trigger the Probe to collect performance data on a page.What you get
It speaks for itself. Here is a Blackfire profiling result from a catalog page in the Commerce Kickstart 2 demo store (Drupal without caches enabled.)
As you can see, we spend a lot of time in Views. Enabling Views cache for our catalog (and anonymous page cache) would greatly speed up our page's load time. Here are results with page caching enabled, and search based Views caching. From 1.88s to 55ms!How to get started
While there is some pretty amazing documentation on installing Blackfire's components, I'll provide a quick start guide. Well, it's a quick start if you use Docker! Blackfire provides an image for their probe and agent. All you need to do is link it to your php-fpm (or whatever container serves your PHP.)
If you use Docker Compose, you would need to add the following configuration, and add a new link to this container from your PHP container. You will just need to get your API credentials from your Blackfire account. Restart your app and you're good to go!blackfire: image: blackfire/blackfire ports: ['8707'] environment: BLACKFIRE_SERVER_ID: xx-xx-xx-xx-xxxx BLACKFIRE_SERVER_TOKEN: dsfsd! BLACKFIRE_LOG_LEVEL: 4
See the full documentation for Docker integration: https://blackfire.io/docs/integrations/docker
Each day, more Drupal 7 modules are being migrated over to Drupal 8 and new ones are being created for the Drupal community’s latest major release. In this series, the Acquia Developer Center is profiling some of the most prominent, useful modules available for Drupal 8. This week: Scheduled Updates.Tags: acquia drupal planetscheduled updatedrupal 8
There are two exciting Drupal community events happening in Portland soon. The first is the Drupal Global Sprint Day on January 30th - this coming Saturday - which is a day focused on bringing together volunteers to contribute work such as documentation, testing, code, and design to the Drupal project. The project needs improvements from a wide variety of skill sets, and it’s a great way for new folks to contribute to Drupal. The second is Drupal Global Training Day, a free Drupal 8 training for new community members. We’re thrilled to be involved with both!Drupal Global Sprint
We’re hosting the Portland sprint at our office. Bring your projects and come code with us! If you've wanted to contribute to Drupal 8, but don't know how to begin, we’re happy to help you get started. New contributors are encouraged to attend, as we will be providing sprint training and new contributor onboarding, so don't worry if you've never contributed to Drupal before. The sprint starts at 9:00 am and goes until 5:00 pm. Programming help, snacks, coffee, tables, and wifi will all be provided by ThinkShout.Drupal 8 Training
February 6th is the Drupal Global Training Day. We will be leading the Portland training at the Drupal Association headquarters, and it's open to everyone. This free training is ideal for new community members and people who are new to Drupal – but PHP developers not familiar with Drupal should also find the training valuable. The training includes coffee and snacks. Participants need only bring a laptop. Everything you need to know to get started will be discussed in detail at the event. We’ll cover:
- An introduction to CMS
- File management and databases
- Site building basics with content types, fields, and views
- Installation of modules and themes
- Deploying to your web host with Git
- Introduction to Drupal 8 theming with Twig templates
- Drupal 8 configuration management
These two global Drupal events offer something for Drupal folks of all skill levels, helping us to tap into Portland’s strong Drupal community. I hope you’ll join us for either (or both!) of these great events.
The last two months finally saw rapid progress in the development of the Search API module's Drupal 8 version. Acquia generously agreed to fund all available time for both Joris Vercammen (borisson_) and me in December and January to work on this port and related modules (especially Facets).What we did
With this backing, we were able to make a lot of head-way and got a lot of large blocking issues out of the way, among them a overhaul for the fields UI, some necessary major internal refactorings and most of the Views integration. All of this is now baked into the new Alpha 12 release, created today. Over the next couple of days, we will then also create releases for the other related modules with a working D8 version: Facets, Search API Solr Search, Search API attachments (Alpha 2) and maybe also Search API pages.
That way, we should be able to avoid a confusion of versions and conflicts for any users interested in trying out the current state of work of this module suite, or already starting to build a new site using them.
Going forth, we will also try to keep this system of creating a set of compatible releases for future Alpha versions.
As noted in the release notes, though, be careful when building sites already with this module version, as there will be no upgrade paths until Beta and some changes until then are still likely to break the storage structure (and would thus lead to loss of configuration, unless handled correctly). Also, this release (like all other non-stable releases for any module) will not be covered by Drupal's Security Team, so any discovered security vulnerabilities would be reported, worked on and fixed publicly.
That being said, though, one of the greatest improvements in the module's D8 version, at least under the hood, is it's vastly improved test coverage. That, along with Drupal.org's automated testing, enables us to be very confident in each new feature we add and each bug we fix, thus also improving the maintainability and speed of feature development in the future. And it hopefully makes it much less likely that any major bugs go unnoticed for long.
But there are also lots of improvements visible right on the surface: we carefully reviewed all major encountered problems and pitfalls with the module's D7 version and worked to make the new D8 version another large leap forward to support as many search use cases as possible, while still becoming much more user-friendly than the D7 version – probably one of the largest points of criticism overall.
So, how does it look for the further path towards a stable D8 release for the Search API (and, subsequently, for its numerous add-on modules)?
Currently, there are no immediate plans for further funding, so while I will of course still work on the port whenever I can, the pace will necessarily slack down a bit again. I also neglected maintenance of my various D7 modules in the last months, so there's also a lot of catching-up to do there. (Incidentally, a great way to help this effort if you are not comfortable with D8 yet: just go into any of my modules' issue queues and try to answer support requests, reproduce or fix bugs, test patches, etc., there.)
However, while there are still a lot of beta blockers left, most of them are relatively minor compared to the ones we now resolved, so I think a first Beta release in March should be within reach. Then it will be a matter of determining the MVP for an initial stable release and working towards that – but I expect a much shorter period for Beta than it has been for Alpha, maybe only a month or two.
Florida DrupalCamp is coming up on March 5th, and DrupalEasy is happy to be involved as a sponsor and organizer. This year's event will be better than ever, with three amazing featured speakers flying in from three different countries! Karen Stevenson, Morten DK, and Jesus Manuel Olivas will be presenting double-length sessions on the lastest Druapl 8-related topics.-->
Media partners are an important part of any DrupalCon. They help us spread the word about the event to people who might not have heard of it otherwise, and get to attend (and report on) the events. Our media partners are critical to DrupalCon's success, so we'd like to say a big thank you to all of our partners for DrupalCon Asia.
I looked at my Drupal 8 Module Acceleration Program (D8 MAP) Trello board this morning and was struck with the enormity of what we have accomplished over the past 4 months.
If you want an overview of the Drupal 8 Module Acceleration Program check out my post on Acquia.com.Tags: acquia drupal planet