All RPGs and Storygames by Tod Foley are now available at DrivethruRPG. Bring these games to your table!
Drupal 8 brought a lot of new features along with it. Making it easier to create rich and beautiful pages. Among the new features included in Drupal 8.7, we saw the stable built-in drag-and-drop Layout Builder, updated Media Library interface, and more. These changes impact site builders, administrators, editors, module developers, themer's, and distribution developers. Drupal 8.8 will be released in December 2019 and will be the last minor release with features.
Let’s look at what Drupal 8.8 has in store for us:
It’s been a decade that the Drupal community has been waiting for the most wanted end-user feature - Better media handling! The addition of WYSIWYG integration completes the final milestone. Read more about it here - https://wimleers.com/blog/media-embedding-drupal-8.8. Drupal 8.8 will come along with complete media management, this enables the site builders and content authors to easily embed media in Drupal.
Check out the media embedding here - https://youtu.be/sTc2JJzs9iU| New and modern administration theme Claro
Claro is a concise, clean, responsive theme with an improved look and enhanced web accessibility. Built on top of the Seven theme, it is now a contributed project. There is a probability that the Claro theme will be added to Drupal 8.8.0 core as an experimental theme.| Composer in Drupal core initiative
To know more visit - https://www.drupal.org/docs/develop/using-composer/using-drupals-composer-scaffold| JSON:API module in Drupal 8.8 is expected to be significantly faster
This has been possible due to the resolution of the following issues:
- Include paths are resolved for every resource in a resource collection;
- Resource normalization is not leveraged and shared;
- ResourceType value objects are computed on every request.
New cache layers were introduced which minimized the cost by reusing computed entities.| Content Moderation and Workspaces core modules can be used on the same site with Drupal 8.8.0!
Starting with Drupal 8.8.0, the Content Moderation and Workspaces modules are no longer incompatible, so they can be installed and used together.
When both modules are installed, the Latest revision local task provided by Content Moderation is no longer available because Workspaces always shows the latest workspace-specific revision on the canonical entity view page (e.g. /node/1). Additionally, when a moderation workflow is enabled for an entity type/bundle and if there are entities in draft (non-default/unpublished) moderation states in a workspace, that workspace can not be published to Live until all the draft entities reach a publishable moderation state.| jQuery UI is being phased out from the Drupal core
- Sync directory is defined in $settings['config_sync_directory'] and not $config_directories.
The ability to support multiple configuration directions in the $config_directories is now deprecated. If you have custom or contributed code that relies on this ability you need to move your setting either to $settings or another to storage. To know more about this visit - https://www.drupal.org/node/3018145
- Event is dispatched before configuration import and export to transform of the configuration - https://www.drupal.org/node/3066005
These events allow modules to interact with the configuration deployment workflow. This was previously only possible with the contrib Config Filter module.
- Modules can be excluded from the configuration synchronization -https://www.drupal.org/node/3079028
A few modules help in developing a Drupal site but are not intended to be deployed to production. Until Drupal 8.8.0 developers had to rely on contrib solutions such as Config Split to separate the development configuration. But sometimes it is not necessary to share the development configuration and instead it is more important to guarantee that development modules can not be included in the configuration export. This is precisely what the lesser-known Config Exclude contrib module did and its functionality is now available for everyone.| Path aliases have been converted to revisionable entities
With Drupal 8.8.0, custom URL aliases are now provided by a new path_alias revisionable content entity type. The path.alias_storage service has been kept in place for backward compatibility, and its hook has been deprecated. Check out this link for code changes recommended to fully utilize the new system and prepare your code for Drupal 9 - https://www.drupal.org/node/3013865Conclusion
With all of these features, the upcoming and previous versions of Drupal 8 are very lucrative for content editors. Kudos to all the Drupalers who have worked on Drupal 8.8 and chalking out the path to Drupal 9.
Reference - Drupal.orgRuchika.Mohite Mon, 10/14/2019 - 18:44
This module extend Inline Entity Form( https://www.drupal.org/project/inline_entity_form )
and adds revision functionality to Inline Entity Form.
->Allow Entity Reference Revision to be added/edited/viewed within
modal dialog, without requiring a page reload.
This module is a POC that solves the dilemma uncovered by PSA-2016-003, allowing access controlled anonymous uploads that are served performant via public storage once reviewed.
For details, see README.
The description below applies to the planned initial release of the module.
The primary goal of this module is to help site owners using Commerce Recurring for subscriptions implement a plan change interface (upgrades, downgrades, cancellations) for their customers.Features
There are two main functions the module provides to enable this:
Allows site builders to set minimum and maximum number of a paragraph type allowed on a field.Installation / Configuration
Install as per any other Drupal Module. https://www.drupal.org/docs/8/extending-drupal-8/installing-drupal-8-mod...
Read our Roadmap to understand how this work falls into priorities set by the Drupal Association with direction and collaboration from the Board and community.
Note from the author: "I'm back in the hot seat! As many of you know, I took on the role of interim executive director in September 2018 while the Drupal Association underwent an executive search. This summer we found a fantastic new leader in Heather Rocker, and now that she's had a few months to settle in, I'm able to return to my regular duties, like bringing you these updates. Thanks for your patience!"
- Tim Lehnen(hestenet)
September was a flurry of activity here at the Drupal Association at large. Coming off a season of travel to a number of Drupal events, we headed straight into our semi-annual staff off-site here in Portland, and followed that up by attending Google's second-ever CMS Leadership summit.
Despite the whirlwind of events taking place in September, we've also landed some major milestones on our roadmap, and are hard at work getting some exciting things together to talk about with you all at DrupalCon Amsterdam at the end of October. As an added bonus, this month's report includes a short retrospective about the impact of the GitLab migration on our maintenance work.Project News Composer Initiative work committed for release in Drupal 8.8.0
A major community initiative for Drupal 8.8.0 has been the push to make Drupal's internal scaffolding and filetree consistent, whether you start using Drupal by using the .zip download, or by using Composer from the get-go. Starting with Drupal 8.8.0 - no matter how you start your journey with Drupal, you'll be ready to use Composer's advanced dependency management when you need it.
Drupal Association engineering team member Ryan Aslett(mixologic) has been the initiative lead for this effort for more than a year. We're thrilled that his work and the work of many volunteers has been committed for release in Drupal 8.8.0!
We want to thank the following contributors for participating in this initiative in collaboration with us:
The work is not over! There are still a number of clean ups and refinements being worked on in the Drupal core queue, and the Drupal Association team is working hard in October to ensure that Drupal.org itself will be ready to deliver these Composer-ready packages of Drupal 8.8.0 on release.Reminder: Drupal 8.8.0 is coming soon!
Speaking of Drupal 8.8.0 - it enters the alpha phase during the week of October the 14th, in preparation for release in December of this year.
Drupal 8.8.0 is the last minor release of Drupal before the simultaneous release of Drupal 8.9.0 and 9.0.0 next year. You can find more information about the Drupal release cycle here.
If you want to help ensure a smooth release, we invite you to join the Drupal Minor Release beta testing program.Drupal.org Update Preparing our infrastructure for Automatic Updates
In September we spent a good amount of time outlining the architectural requirements that will need to be met in order to support delivering the update packages that are part of the Automatic Updates initiative.
We are only in the first phase of this initiative, which focuses on: 1) Informing site owners of upcoming critical releases, 2) Providing readiness checks that site owners can use to validate they are ready to apply an update, and 3) offering in-place automatic updates for a small subset of use-cases (critical security releases).
As this initiative progresses, and begins to cover more and more use cases, it should greatly reduce TCO for site owners, and friction for new adopters. However, to make that forward progress we are seeking sponsors for the second phase of work.Readying our secure signing infrastructure
With the help of a number of community contributors (see below), a new architecture for a highly secure signing infrastructure has been laid out. As we roll into Q4 we'll get ready to stand this new infrastructure up and begin securing the first automatic updates packages.
Going into early October, a number of contributors came together at BadCamp to help advance this effort further. Without the collaboration between community members and Drupal Association staff, these initiatives would not be possible.
We'd like to thank the following contributors to the Automatic Updates/Secure Signing Infrastructure initiative:
In conjunction with the Drupal core team, the DA engineering team has been supporting the work to ensure that contributed projects are ready for the release of Drupal 9.
Early testing has shown that over 54% of projects compatible with Drupal 8 are *already* Drupal 9 ready, and we'll be continuing to work with the core team to get out the word about how to update the modules that are not yet compatible.Infrastructure Update A brief retrospective on the GitLab migration
Drupal.org's partnership with GitLab to provide the tooling for Drupal and the ~40,000 contributed projects hosted on Drupal.org has been a significant step forward for our community. We're no longer relying on our own, home-brew git infrastructure for the project, and we're gradually rolling out more powerful collaboration tools to move the project forward.
But what has that meant in terms of maintenance work for the Drupal Association engineering team?
There was some hope as we were evaluating tooling providers that making a switch would almost entirely eliminate the maintenance and support burden. While that was a hopeful outlook, the reality is that maintaining 'off-the-shelf' software can be at least as much work as maintaining mature existing tools.
GitLab in particular is still iterating at a tremendously rapid pace, releasing updates and new features every month. However, that speed of development has also meant frequent maintenance and security releases, meaning the DA team has had to update our GitLab installation almost once a week in some months.
Does that mean we're unhappy with the change? Absolutely not! We're still thrilled to be working with the GitLab team, and are excited about the new capabilities this partnership unlocks for the Drupal community (with more coming soon!).
However, it is a good lesson to anyone running a service for a large community that there's no free lunch - and a great reminder of why the support of Drupal Association members and supporting partners is so essential to our work.
As always, we’d like to say thanks to all the volunteers who work with us, and to the Drupal Association Supporters, who make it possible for us to work on these projects. In particular, we want to thank:
- Tag1 - Renewing Signature Supporting Partner
- Gitlab - *NEW* Premium Technology Supporter
- Four Kitchens - Renewing Premium Supporting Partner
- Phase2 - Renewing Premium Supporting Partner
- WebEnertia - Renewing Premium Supporting Partner
- Thunder - Renewing Premium Supporting Partner
- Palantir -Renewing Premium Supporting Partner
- Specbee - Renewing Premium Supporting Partner
- Pantheon - Renewing Premium Hosting Supporter
- Cyber-Duck - *NEW* Classic Supporting Partner
- Websolutions Agency - *NEW* Classic Supporting Partner
- Unic - *NEW* Classic Supporting Partner
- Kalamuna - Renewing Classic Supporting Partner
- ThinkShout - Renewing Classic Supporting Partner
- Amazee - Renewing Classic Supporting Partner
- Access - Renewing Classic Supporting Partner
- Studio Present - Renewing Classic Supporting Partner
- undpaul- Renewing Classic Supporting Partner
- Mediacurrent - Renewing Classic Supporting Partner
- Appnovation - Renewing Classic Supporting Partner
- Position2 - Renewing Classic Supporting Partner
- Kanopi Studios - Renewing Classic Supporting Partner
- Deeson - Renewing Classic Supporting Partner
- GeekHive - Renewing Classic Supporting Partner
- OpenSense Labs - Renewing Classic Supporting Partner
- Synetic - Renewing Classic Supporting Partner
- Axelerant - Renewing Classic Supporting Partner
- Centretek - Renewing Classic Supporting Partner
- PreviousNext - Renewing Classic Supporting Partner
- UniMity Solutions - Renewing Classic Supporting Partner
- Code Koalas - Renewing Classic Supporting Partner
- Vardot - Renewing Classic Supporting Partner
- Berger Schmidt - Renewing Classic Supporting Partner
- Authorize.Net - Renewing Classic Technology Supporter
- JetBrains - Renewing Classic Technology Supporter
- GlowHost - Renewing Classic Hosting Supporter
- Sevaa - Renewing Classic Hosting Supporter
- Green Geeks - Renewing Classic Hosting Supporter
If you would like to support our work as an individual or an organization, consider becoming a member of the Drupal Association.
We recently completed a special data integration project for the University of Minnesota, Office of the Executive Vice President and Provost, Faculty and Academic Affairs. Faculty Affairs, as they are referred to, uses a product called Activity Insight from Digital Measures (referred to internally as “Works”) to capture and organize faculty information.
Hubspot Webform Handler uses Hubspot API to webforms to hubspot forms.
This module provides a user interface to deploy the content and block to another server in the simple method(eg - Staging to Production).
After install this module, please follow the below steps :
1) In the admin top menu, click the settings link under the Deploy menu.
2) Enter the request url to push the content and block.
3) Enter the username and password for authentication.
4) Select the content type and block type to push to another server.
Note : We need to follow the above 3 steps in the requesting server also.
This module integrates the sliCarousel library with Drupal which allows you to create responsive slider which is easy to use.
sliCarousel is a responsive slider/carousel which has the following features;
A proper Mojito starts with a bar spoon of sugar and 2-3 slices of lime in the bottom of a shaker. Top that with 14-16 fresh mint leaves, and muddle them gently into the padding to release the delicate oils. Be careful not to bruise the leaves or they will release chlorophyll, which will give us a bitter drink. Fill the glass with ice, 1.5 oz white rum, 1/2 cup club soda, and stir gently. Voila, a perfect blend of refreshment for you.
All of the browsers listed in Drupal's browser support policy support matchMedia so this asset library is deprecated in Drupal 8.8 and will be removed in Drupal 9.