![]() ![]() ![]() Then document the setup in your site's editor documentation while it's all fresh and clear in your mind. Make sure you run through each scenario using each role. With all the states, transitions, transition ordering, roles, and permissions, there are plenty of opportunities for misconfiguration even for a total pro with great attention to detail like yourself. You can add the patch to your composer.json file if you're tired of your workflow states getting accidentally changed. Well, that's a bug as of 8.5.3 that will be fixed in the next 8.5 bugfix release. Minimize Accidental Transitionsīut why wouldn't my content's workflow state stay the same by default when editing the content (assuming the user has access to a transition that keeps it the same)? I have to set an order correctly to keep a default value from being lost? You may have to add additional transitions to make this all make sense.Īs for the ordering of workflow states themselves, this will only affect ordering when states are listed, for example in a Views exposed filter of workflow states or within the workflows administration. To set the right order, you have to map each state to what should be its default value when editing. If an editor misses setting this option correctly, they will simply get the first transition, so make sure that first transition is a good default. Ordering of the transitions here is very important because the state options on the content editing form will appear as a select list of states ordered by the transition order, and it will default to the first available one. Therefore, make sure that draft content can stay as draft when edited, etc. In fact, it would be very easy to accidentally publish what you had archived, because editing the content will set it back to published as the default setting. You'd have to change the status to published and then back to archived. In the above (default core) example, it is not possible to edit archived content and maintain the same state of archived. The transitions represent which options will be available for the state when you edit content. Make sure the transitions include non-transitions. If they can change the state from "Needs Work" to "Needs Review," make sure they can change it back to "Needs Work." You must allow Non-Transitions If you can't think of a clear, descriptive verb that applies, you can go with 'Set state to %your_state" or "Mark as %your_state." Don't sweat the names of transitions too much though they don't seem to ever appear in an editor-facing way anyway.ĭon't forget to allow editors to undo transitions. The transitions should be named as verbs. You might want some paper to map out all the paths between workflow states that content might go through. Transitions between workflow states must be thought through Typically, you'll want to lock down who can publish content, allowing content contributors to create new drafts only. Transitions between workflow states will be what you assign as permissions to roles. It makes a much simpler mental model for everyone. Try to use the same workflow on all content types if you can. A good compromise is to ask that the team tries something simple first and adds complexity down the line if needed. If you create an editorial workflow that is too strict and complex, editors will tend to find ways to work around the system. Stakeholders may ask for many roles and many workflow states without knowing the increased complexity and likelihood of editorial confusion that results. Resist increases in roles, workflows, and workflow states and make sure they are justified by a business need. ![]() I've been doing some work with this for a new site for a large organization, and have some tips and tricks. The documentation gives a good overview.Ĭontent Moderation requires the Workflows core module, allowing you to set up custom editorial workflows. Think of it like the contributed module Workbench Moderation in Drupal 7, but without all the Workbench editor Views that never seemed to completely make sense. The Content Moderation core module was marked stable in Drupal 8.5.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |