All RPGs and Storygames by Tod Foley are now available at DrivethruRPG and RPGnow. Bring these games to your table!
Allows to exclude certain configuration forms to be editable, when the site is on configuration read-only mode.
Filters can be created with set of form id or route name. Since filters are config entities, can be exported/imported like any other configuration.
1. Filter by Form ID
2. Filter by Route name - This is not supported yet.
Simple module that allows lookups of addressesRoadmap
Currently takes postcode and returns longitude and latitude
Import coupons from a CSV file into a selected promotion on Drupal Commerce. For promotions such as Groupon.
At DrupalSouth 2017, I presented a session on the new Workflows module, which just went stable in Drupal 8.4.0. Workflows was split out from content moderation as a separate module, and can be used independently to create custom workflows. In this presentation, I gave a demonstration of how to create a basic workflow for an issue tracker.by Kim Pepper / 29 November 2017
Since 2011 we have had access to a content moderation tool in Drupal 7 in the form of Workbench Moderation. This module introduced the concept of Draft ➡ Review ➡ Published workflows, with different user roles having specific permissions to move from one state to the next.
Unfortunately, the underlying Drupal core revision API was not designed to deal with this, and there were some pretty crazy workarounds.
Content moderation has long been a key feature request for Drupal, and so effort was made to port Workbench Moderation across to Drupal 8.
Content Moderation drove a lot of cleanup in Drupal core APIs, including proper support for forward revisions, and adding revision support to other content entities besides Content Types, such as Custom Blocks. More are on the way.
In Drupal 8.3, the Workflows module was split out of Content Moderation. Why you may ask? Well, because the Workflows module provides the state machine engine that Content Moderation relies on.What is a State Machine?
A state machine defines a set of states and rules on how you can transition between those states.A door state machine
In our simple example of a door, it can only be opened, closed or locked. However, you can't go directly from locked to open, you need to unlock it first.Content Moderation Workflow Configuration
Content Moderation provides a set of Workflow states and transitions by default.Content Moderation StatesContent Moderation Transitions
If we were to put this together in a state machine diagram, it would look like the following:Content Moderation State Machine
From the above diagram, it becomes clear what the allowed transitions are between states.
So now Workflows has been configured with our Content Moderation states and transitions, what is left for Content Moderation to do?What Does Content Moderation Do?
It turns out quite a lot. Remember, that Workflows only provides the state machine. It in no way prescribes how you should manage the current state of a particular entity.
Content Moderation provides:
- Default Workflows configuration
- A fairly complex WorkflowType plugin which works with the Revision API.
- Storage for individual states on content entities
- Configuration of which entity bundles (Content types, etc.) should have Content Moderation
- A number of admin forms for configuring the workflows and how they apply
We want to build a very simple issue tracker for our example. The state machine diagram is the following:Issue Tracker State Machine
That's the simple bits out of the way. Now, in order to build an issue tracker, we will need to replicate the rest what Content Moderation does!
Fortunately there is a module that can do most of the heavy lifting for us.Workflows Field
“This module provides a field which allows you to store states on any content entity and ensure the states change according to transitions defined by the core workflows module.”
Perfect! Let's download and install it.
Next we want to add a new Workflow. We can assign it a label of Issue Status and you'll see that we have a new Workflows Field option in the Workflow Type dropdown.Add new workflow
We can then configure the desire Workflows states and transitions.Issue StatesIssue Transitions
Thats the our Workflows configured. Now we need to create a new Issue content type to attach our workflow to. It's assumed you know how to create a content type already. If not, check out the User Guide.
Next, we need to add our Workflows Field to our Issue content type. Follow the usual steps to add a field, and in the drop down choose Workflows as the field type, and our previously created Issue Status workflow.Add workflows fieldTest it out!
Now we can test our our workflow by creating a new Issue from the Content page. If everything was configured correctly, we should see a new field on the edit form for Status.Issue status form
Given the transitions we defined in our workflow, we should only be allowed to see certain values in the drop-down, depending on the current state.Testing workflow constraintsWhat next?
That's it for setting up and configuring a custom workflow using Workflows Field. Some next steps would be:
- Add permissions for certain users (there's an issue for that #2904573 )
- Add email notifications
Let me know in the comments!Tagged Workflows, Content Moderation
Dated 29 November 2017Add new comment
If you ever have need of timed or delayed payments, we have some good news: recurring billing (also known as subscriptions) is new and improved in Commerce 2. Check out this week's High5 episode and learn more! What is recurring billing?
It's anything where we want to have a transaction happen after the initial time when a customer is on our site. That might be monthly or yearly, or it might be when you want the last half of the payment to go through in a couple days or a week.How does it work?
It's not like we store pictures of everyone's credit cards and just keep applying charges to them. Instead, we store tokens, or references to the credit cards. This is much safer because it means that even if the site got hacked, no one would have access to your actual banking information. At no point does Commerce ever store your actual credit card.
If you're interested in reading more about tokenization, Wikipedia has a lot of good information on the subject.How is this different from Commerce 1?
We sort of had tokenization (a.k.a card on file) in Commerce 1. It was a contrib module and wasn't actually part of Commerce itself. Some payment gateways supported it, some didn't, some did but only partially… it was much more of an ad hoc thing.
Now, tokenization is built into Commerce, so any major payment gateway that gets set up and has the capacity to store tokens (which is most of them), will do so. You don't need to do anything special for your payment gateway to handle recurring billings. As long as we have that token, we can keep making charges to it until that token becomes invalid (i.e. the card gets cancelled).
It was actually a credit to Commerce 1 that it had tokenization at all. It's a complex thing. For instance, if a payment doesn't go through, do we have to cancel the subscription? Do we have to get the product back? Do we do that immediately, or give them a window of time to put in the new card? A lot of ecommerce setups just avoided that entirely, so it was definitely a strength of Commerce 1, and now it's really a strength of Commerce 2.The bottom line
Recurring billing rocks, and is now built right into Commerce 2.
Advanced Access is an access control suite designed to provide an extensible access control system that leverages plugins to determine access pathways. The module extends the concepts of the node_access implementation in code to support additional entity types and to make the interface between access modules simple.
I have decided to remove paid promotions from the Webform module to focus on promoting the Drupal Community as a whole, the Drupal Association, and Webform module, I am also comfortable stating that I am not asking for forgiveness for my decision.
It is important that the Drupal community understand that I reached out to Lingotek and chose to promote their services within the Webform module's UX. Lingotek has made and continues to make amazing contributions to Drupal and the community. I want to thank them for allowing me to promote their services in such an experimental way.
Removing the paid promotion
I documented my original intentions in a blog post about promoting paid services within the Drupal community. I have come to fully agree with lslinnet's comment...
The Drupal community needs to explore ways to help support and fund core contributors and project maintainers. The goal of the paid promotion experiment was to see how everyone, including myself, felt about this concept.
MortenDK's (mortendk) very upset and direct tweet triggered the largest debate...
Yes, the promotions of third-party services within a module's UX could open some floodgates that could create a horrendous user experience and first impression of Drupal. First impressions are very...Read More
Acquia Developer Center Blog: Creating a Decoupled Drupal Application in 30 Minutes with Lightning, BLT, and DrupalVM
Acquia’s Professional Services team recently released an open-source application that demonstrates how Drupal and Node.js can easily be paired to create beautiful and functional decoupled applications. See how easy it was to create the Drupal backend using a combination of Acquia and Drupal community projects such as Lightning, BLT, and DrupalVM. This will allow you to follow the same process to rapidly create your own custom decoupled applications.Tags: acquia drupal planet
it's been since March 2016 when we posted our last update on reaching Milestone 2 for porting Rules to Drupal 8. In the last 1.5 years, we haven't made significant progress because of limited resources available to contribute to the module. From an initiative perspective this is unfortunate, because we would like to fulfill the mission of providing a stable release for the Rules module in Drupal 8.
During DrupalCon Vienna we had various good talks but nothing confirmed yet. Our overall status summary is:
Milestones 1 & 2 have been completed
Milestone 3 is still pending
So we are at 70% of providing a stable release for Rules in Drupal 8
Fago can’t dedicate time required to develop the module further. What Rules is really missing at the moment is development capacity to help finish the last milestone. We have some early alpha releases out and are “only” missing 30% to complete development but to provide Rules’ capabilities to the ecosystem this investment would be really needed. If we look at the usage statistics, we can see that more than 5000 Drupal 8 sites already rely on Rules and there is a potential for almost 300,000 Drupal 7 sites with active Rules installations to migrate. It would be great to have all of them not rely on alphaware that doesn’t have an upgrade path or security coverage.
Various supporters already have helped us achieve 2 out of 3 milestones. Especially in the last weeks we have seen good activity in the Rules issue queue. Still, the Rules initiative won’t get much further without dedicated development capacity available. Even if we got more funding today, fago the current principal maintainer of the Rules module wouldn’t have enough capacity to do the work himself. So, if you are or if you know a good developer that could work on Rules, thanks for reaching out in the issue queue or contacting me directly via drupal.org.
We are hosting initiative meetings every second Thursday. Details and agenda can be found in our roadmap issue.
Josef / dasjo
Valuebound: Drupal Commerce: Splitting a package into multiple shipments using Packer & PackerManager
Drupal 8 commerce shipping contributed module introduced an extendable and prioritized concept of Packer and PackerManager. Packer allows sites to automatically split an order into multiple shipments based on stock location, weight, dimensions, or some other criteria.
Let’s see what Packer and PackerManager do.Packer and PackerManager
- Packer: Creates one or more shipments for a given order. We can create an end number of Commerce Packer class, which implements `Drupal\commerce_shipping\Packer\PackerInterface`. PackerInterface provides abstract methods:
In every corner of the world, your potential customers are waiting for your website to start “speaking” their language. And it’s easy to provide that with Drupal 8, a true polyglot among CMSs. Unmatched multilingual capacities are among Drupal 8’s most lucrative features that inspire website owners to choose “the great eight” — either to get a website or to upgrade their existing one. Well, it’s really hard to resist!Read more
How to integrate Workbench moderation in Drupal 8
Popper has no dependencies and plays well with popular front-end frameworks.Installation:
Composer is recommended. Use:
composer require 'drupal/popper_js:1.x-dev'