Configuration management (CM) in Drupal 8 is great. However, when more complex configuration scenarios arise, we must find solutions to problems that core CM functionality doesn’t address (yet).
Learn all about Twig templates in Drupal 8 from our very own Larry Walangitan.
This is the fourth post in a series about coding standards. In this post we’ll talk about why good, standardized documentation is crucial to your project, and review Drupal coding standards regarding documentation and comments.
Drupal 8.3.0, the next planned minor release of Drupal 8, is scheduled for Wednesday, April 5, 2017. Minor releases include new features, usability improvements, and backwards-compatible API improvements. Here's what this means now for core patches.Alpha vs. Beta releases
In previous Drupal 8 minor releases, the first pre-release version of the minor was labeled as beta1, and expectations were slightly different for later betas. For Drupal 8.3.0, we've recategorized this first pre-release version as alpha1, to distinguish it from the subsequent beta releases. (We will also no longer have "beta target" issues; some strategic issues are considered for backport to 8.3.x, but only after they are fixed in 8.4.x, and only up until the new beta phase begins.)
This change should provide better clarity and fairness on which issues are accepted for commit. The overall timeline for the minor release is not changed; alpha1 simply replaces the previous beta1, and the previous, stricter beta2 now becomes beta1. (More information on alpha and beta releases.) The release candidate phase is the same as for past releases.Drupal 8.3.0-alpha1 will be released the week of January 30
- In preparation for the minor release, Drupal 8.3.x will enter the alpha phase the week of January 30.
- Developers and site owners can begin testing the alpha.
- The 8.4.x branch of core will be created, and future feature and API additions will be targeted against that branch instead of 8.3.x. All outstanding issues filed against 8.3.x will be automatically migrated to 8.4.x once it is opened.
- All issues filed against 8.2.x will then be migrated to 8.3.x, and subsequent bug reports should be targeted against the 8.3.x branch.
- During the alpha phase, core issues will be committed according to the following policy:
- Most issues that are allowed for patch releases will be committed to 8.3.x and 8.4.x.
- Drupal 8.2.x will receive primarily critical bugfixes in preparation for its final patch release window. (Drupal 8.1.x and 8.0.x are not supported anymore and changes are not made to those branches.)
- Most issues that are only allowed in minor releases will be committed to 8.4.x only. A few strategic issues may be backported to 8.3.x, but only at committer discretion after the issue is fixed in 8.4.x, and only up until the beta deadline.
Roughly two weeks after the alpha release, the first beta release will be created. All the restrictions of the alpha release apply to beta releases as well. The release of the first beta is a firm deadline for all feature and API additions. Even if an issue is pending in the Reviewed & Tested by the Community (RTBC) queue when the commit freeze for the beta begins, it will be committed to the next minor release only.
The release candidate phase will begin the week of February 27, and we will post further details at that time.
See the summarized key dates in the release cycle, allowed changes during the Drupal 8 release cycle, and Drupal 8 backwards compatibility and internal API policy for more information.
As a reminder, we have until the start of the alpha to add great new features to Drupal 8.3.x. Stabilizing experimental modules (such as Inline form errors and Migrate Drupal), landing some key Media Initiative components, and working on bugfixes are all priorities for 8.3.0. Help with these changes now for a great Drupal 8.3.0!
Are you looking for an easy way to find errors thrown by your Drupal modules and themes?
A lot of new developers are learning to create their first Drupal 8 modules or Drupal 8 themes. Often they've made a very small typo or spacing error and are looking for an easy way to debug their mistake.
Follow this tutorial, and you'll quickly be able to see a detailed list of recent errors on your Drupal site.
This feature provides the base implementation for the carousels in your website.
Admins will be able to create carousels on the spot and place it anywhere in the site.Features
- Carousel block type.
So, what is chaos magic? Some would say magic is inherently chaotic, others say such wildness is the purview of the sorcerer and other spell-casters are a bit more ordered. Yet some wizards (and some bards) tread a narrow path in which they manipulate raw energy, affect chance, and teter on the edge of madness. There are dangers, one being the chaos magic surge. When one of those occurs anything could happen - maybe the sun is suddenly eclipsed or the caster grows a long purple moustache! (Yes, there is a wonderful random table to roll on.)
For wizards there is a School of Chaos Magic to study, whilst bards can opt for the College of Entropy, home of natural gamblers, the sort of people who rely on luck as much as on knowledge and skill. Each provides various advantages as characters rise in level.
After the aforementioned Chaos Magic Surge table, which makes entertaining reading, there\'s a chaos magic spell list which is available to bards, sorcerers with the wild magic bloodline, and wizards. This provides wonderful opportunities to mess with your opponents\' (and quite often your allies\') heads.
This is one to have fun with. As a player, grapple with something unpredictable. As a DM, enjoy watching your players\' faces as someone\'s very being warps and oozes like a Salvadore Dali painting or a spellbook develops a mouth and starts answering back! And yet, it\'s not silly - it\'s just strange, a way to make magic mysterious and surprising again!
I've previously written about dynamic forms in Drupal, using #states to show or hide input boxes depending on other inputs. Since then, Drupal 7 and 8 have both got the ability to combine conditions with OR and XOR operators. This makes it possible to apply changes when a form element's value does not equal something, which is not obvious at all.
This is an experimental Migrate source to import Data from a Drupal 8 site.
Currently provides sources for Nodes, Users and Terms including configurable fields. Contributions are very welcome, we are also interested in co-maintainers or bringing it into Drupal core.
This has not been extensively tested yet, use with caution.