Problem/Motivation

The help text of the Worksflow module does not follow the Help text standards as described in https://www.drupal.org/help-text-standards. It misses the Uses section.

Proposed resolution

Editing the help text according to the standard.

Remaining tasks

  • Add the Uses section
  • Replace Drupal::url()

User interface changes

This is a UI text change

Issue fork drupal-2861849

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

ifrik created an issue. See original summary.

prash_98’s picture

Status: Active » Needs review
StatusFileSize
new1.27 KB

Have added the uses section along with the link to the documentation.

Status: Needs review » Needs work

The last submitted patch, 2: 2861849-2.patch, failed testing.

gaurav.kapoor’s picture

Assigned: Unassigned » gaurav.kapoor
gaurav.kapoor’s picture

Assigned: gaurav.kapoor » Unassigned
Status: Needs work » Needs review
StatusFileSize
new1.22 KB

Re-roll

ifrik’s picture

Status: Needs review » Needs work
Issue tags: -DevDays Seville +DevDaysSeville

prash_98, gauruv.kapoor,

both of your patches do not follow the Help text standard mentioned in the issue summary above. It still doesn't describe the Uses. Also the module description has not been changed. Meanwhile the About section was fine, but you changed that unnecessary.

So if anybody else want to work on this issue, please just start again from scratch, and check the help text standards first.

pepegarciag’s picture

Assigned: Unassigned » pepegarciag

I will work on this.

pepegarciag’s picture

Status: Needs work » Needs review
StatusFileSize
new1.46 KB

I started again from scratch as #6 suggested so I just added the Uses section and make the description fit one sentence. I moved part of the description to the Uses section because it seems to fit there.

pepegarciag’s picture

Assigned: pepegarciag » Unassigned
lomasr’s picture

StatusFileSize
new91.6 KB
new95.47 KB
new1.46 KB

#8 looks good to me. Applied the patch it worked cleanly. Please see before and after screen. small grammar correction needed, I have created a patch for it. "a UI" to "an UI".

pepegarciag’s picture

Status: Needs review » Reviewed & tested by the community
ifrik’s picture

Status: Reviewed & tested by the community » Needs work

Hi,
please check the issue summary before RTBCing something. The remaining tasks listed there are not done, and the Uses section does not follow the defaults that are linked from the issue summary.

Once that is done, the text needs to be checked by somebody who is working on this module because it is still an experimental module and it's functionality is still changing or might have been not really clear.

And as a general note: The person working on a patch shouldn't really RTBC it anyway, because the step of "reviewing by the community" ensures us that somebody else has a fresher look on it.

ifrik’s picture

Issue summary: View changes

The use of Drupal::url() has been deprecated and needs to be replaced as well.
See #2868989: Replace calls of the deprecated Drupal::url() from update.module for details.

lomasr’s picture

StatusFileSize
new2.17 KB

As suggested in remaiing task 1 and 2 are done in the patch. 3rd, I think is not neccesary to be changed as suggested in #13 because it's an external URL. Please review and suggest.

lomasr’s picture

Status: Needs work » Needs review
ifrik’s picture

Status: Needs review » Needs work

The proposed text does not follow the Help text standards as linked in the issue description, and it does not cover all the uses of this module.

sam152’s picture

  1. +++ b/core/modules/workflows/workflows.info.yml
    @@ -1,6 +1,6 @@
    +description: 'Workflow module allows you to create multi-state process to review before content to be published.'
    

    This isn't actually true, workflows has no relationship to content. The workflows plugin in content_moderation is what introduces those semantics.

  2. +++ b/core/modules/workflows/workflows.module
    @@ -27,7 +27,13 @@ function workflows_help($route_name, RouteMatchInterface $route_match) {
    +      $output .= '<p>' . t('The Workflows module provides an UI and an API for creating multi-state process per user role to check what user is posting before publishing the content. For more information, see the <a href=":workflow">online documentation for the Workflows module</a>.', [':workflow' => 'https://www.drupal.org/documentation/modules/workflows']) . '</p>';
    +      $output .= '<h3>' . t('Uses') . '</h3>';
    +      $output .= '<dl>';
    +      $output .= '<dt>' . t('Allows you to manage workflow with states and transitions.') . '</dt>';
    +      $output .= '<dt>' . t('For example - a digital newspaper in which the editors make their articles, but they have to pass before by a supervisor to be published.') . '</dt>';
    

    Same here.

prash_98’s picture

Status: Needs work » Needs review
StatusFileSize
new1.68 KB

Have made the changes as required. Please review.

ifrik’s picture

Status: Needs review » Needs work

Please provide an interdiff.

prash_98’s picture

Status: Needs work » Needs review
StatusFileSize
new3.34 KB

Uploading the interdiff..

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

prash_98’s picture

Any updates with the issue?

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

ifrik’s picture

Status: Needs review » Needs work

prash_98: Did you even look at the Help text standards?

I'll work on this during the sprint weekend.

prash_98’s picture

I have gone through it @ifrik and do let me know where I am making any error ...

shubhangi1995’s picture

StatusFileSize
new5.51 KB
new5.51 KB

Hi all
The patch contains following changes
1) change in short description from above patch
2) change in use in help page
3) change in url
I am also attaching the interdiff
@ifrik sorry i missed your last comment , if still inaccurate please provide correct patch.

Thanks

shubhangi1995’s picture

Status: Needs work » Needs review

Status: Needs review » Needs work

The last submitted patch, 26: 2861849_edit_help_description_26.patch, failed testing. View results

yogeshmpawar’s picture

Assigned: Unassigned » yogeshmpawar
yogeshmpawar’s picture

Assigned: yogeshmpawar » Unassigned
Status: Needs work » Needs review
StatusFileSize
new3.26 KB

Rerolled the patch.

lomasr’s picture

StatusFileSize
new33.33 KB

#30 worked fine for me.

amietpatial’s picture

StatusFileSize
new191.36 KB

@Yogesh Your patch applied successfully and working fine

joachim’s picture

Status: Needs review » Needs work

> Add the Uses section

I don't see this in the patch.

(BTW @amietpatial there is no need to take screenshots of a patch applying correctly to the code.)

ifrik’s picture

@lomars, @prash_98, @shubhangi1995, @yogeshmpawar,

It looks likes none of you looked at the Help Text Standards linked in the issue description or the list of remaining tasks.
I fail to understand why you think that the issue is done, or why you think that the patch works.

Instead of somebody actually fixing this issue, this is just creating work for others who repeatedly can only point to the same issue description. I would like to be able to give some constructive feedback, but this is really too frustrating.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

manish.upadhyay’s picture

Hi,

I have created a new patch with Uses and one liner short description on extend page.

Thanks,

manish.upadhyay’s picture

Status: Needs work » Needs review
ifrik’s picture

Status: Needs review » Needs work

Sorry, but you did not add any Uses. You simply reworded the existing text a bit.

mradcliffe’s picture

Issue tags: +DrupalEurope, +Novice

I added the DrupalEurope and Novice tag. The patch needs work to address the helpful reviews by @ifrik and @joachim in #33, #34 and #38.

ifrik’s picture

Title: Edit hook_help text and module description for Workflows module » Edit hook_help text for Workflows module
Issue summary: View changes
ifrik’s picture

The module description is now in a separate issue #2999423: Update the Workflows module description.

wengerk’s picture

Status: Needs work » Needs review
StatusFileSize
new2.71 KB
new467 bytes

As suggested by #41, remove the module description & only keep the hook_help in this issue.

ifrik’s picture

Status: Needs review » Needs work

Wengrek,
Are you around at the DrupalEurope sprint? Then I could talk to you about what needs to be done with this description. I'm in the sprintroom with the big windows on the Admin UI table.

volkswagenchick’s picture

Issue tags: +fldc19, +sfdug, +dcnj19

Tagging for upcoming contribution days.

vermauv’s picture

Assigned: Unassigned » vermauv
volkswagenchick’s picture

Issue tags: +midcamp2019

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

alfredofonseca’s picture

Alfredo and Jason, user jayzee we are trying to work on this at DrupalCon 2019 Seattle

(Our mentor mentioned this may not be the best issue to start working with, as Novice, so I will do no further work on this one)

volkswagenchick’s picture

Issue tags: +drupalnorth2019

Tagging for DrupalNorth 2019

ifrik’s picture

Assigned: vermauv » Unassigned

Vermauv, I asigned you so that somebody else can take this up.

ifrik’s picture

Issue tags: +DevDaysTransylvania

Working on it during DevDaysTransylvania

ifrik’s picture

Removed the tags for the camps during which there was no work done on this.

ifrik’s picture

Issue summary: View changes
Status: Needs work » Needs review
Issue tags: -Novice
StatusFileSize
new4.97 KB

I've written a documentation for the Worksflow module, based on my understanding of it because there's no additional documentation to refer to.
This help text therefore needs to be reviewed by somebody who knows what the Worksflow module can or can't do. Checking whether the patch applies or whether the text reads nicely is not sufficient in this case.

Status: Needs review » Needs work

The last submitted patch, 53: 2861849-workflows-help-text-53.patch, failed testing. View results
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.

ifrik’s picture

Reviewed by alexpott, and needs more work to emphasize that the module on its own doesn't do anything. But when there is a plugin to leverage its API then it provides a consistent UI.

yogeshmpawar’s picture

Status: Needs work » Needs review

Setting back to Needs Review & above test fails are not related.

ifrik’s picture

Status: Needs review » Needs work

@yogeshmpawar
Please see comment #55.

ifrik’s picture

Status: Needs work » Needs review
StatusFileSize
new4.14 KB

I've tightened up the text, and made it clearer that the user can't do anything with this module unless there is another module installed.

The slight duplication at the end of "Adding states" and "Adding transitions" is inline with other help texts, linking directly to the relevant admin pages for each use.

There's no interdiff because all the text is changed.

Empty lines that caused a Coding Standard Message are removed.

alexpott’s picture

  1. Thanks for working on this. This one is super tricky because on it's own the module does nothing.
  2. +++ b/core/modules/workflows/workflows.module
    @@ -15,13 +16,18 @@ function workflows_help($route_name, RouteMatchInterface $route_match) {
    +      $output .= '<dd>' . t('A workflow requires at least two states. For a content workflow, this could for example be an additional <em>Draft</em> state in addition to the default publication states. States can be added when you add or edit a workflow on the <a href=":worksflows">Worksflows page</a>.', [':worksflows' => Url::fromRoute('entity.workflow.collection')->toString()]) . '</dd>';
    

    I think we can remove For a content workflow, this could for example be an additional <em>Draft</em> state in addition to the default publication states. entirely. It's wordy and feels like it is in the weeds.

  3. +++ b/core/modules/workflows/workflows.module
    @@ -15,13 +16,18 @@ function workflows_help($route_name, RouteMatchInterface $route_match) {
    +      $output .= '<dd>' . t('A transitions defines which in which state a config or content item can be save as next. It has one destination state, but can have several states <em>from</em> which the transition can be applied. Transitionss can be added when you add or edit a workflow on the <a href=":worksflows">Worksflows page</a>.', [':worksflows' => Url::fromRoute('entity.workflow.collection')->toString()]) . '</dd>';
    

    I think we should remove a config or content item that's an assumption the Workflows module doesn't make.

    A transitions should be A transition.

    Later on there's a Transitionss

  4. +++ b/core/modules/workflows/workflows.module
    @@ -15,13 +16,18 @@ function workflows_help($route_name, RouteMatchInterface $route_match) {
    +      $output .= '<dt>' . t('Configuring workflows further') . '</dt>';
    +      $output .= '<dd>' . t('Depending on the installed workflow type, you can also configure to which entities the workflow applies, and what its default state is.') . '</dd>';
    

    This is totally dependent on the module that implements the workflow type. I think all we can say is that particular workflow types might have additional options on here. But I feel it is the responsibility of the module that provides the workflow type to document this.

pguillard’s picture

There is also a typo in the ":moderiation" link, which is broken,
and here "A transitions defines which in which state"

ifrik’s picture

Thanks, I'm now still trying to find why the Workflows link "Adding workflows" is broken...

pguillard’s picture

This one took into account suggestions #59 2,3,4

ifrik’s picture

StatusFileSize
new3.96 KB
new3.42 KB

Thanks again pguillard for pointing out the broken link, and for coming and talking to me.

This patch takes the text changes into account, and fixes the broken links in "Add workflows". The interdiff is based on #58 because there was some confusion on pguillard's side on whether to review it or just patch it straight away, which overlapped with me working on it as well.

pguillard’s picture

Status: Needs review » Reviewed & tested by the community

As #59 2,3,4 and #60 suggesstions were taken into account, and the broken link has been removed, I guess I can push it to RTBC !

ifrik’s picture

Status: Reviewed & tested by the community » Needs review

pguillard: Do you also want to review #2999423: Update the Workflows module description ? That's the shorted description of the module on the Extend page.

ifrik’s picture

Status: Needs review » Reviewed & tested by the community

Sorry, I don't know why my comment reset the status.

alexpott’s picture

One thing I've been pondering is if we should have any of this. Looking at content_moderation_help() that's the useful documentation. And maybe should be expanded to its specific case.

ifrik’s picture

How about keeping this since it describes the functionality of the Worksflow interface - because this still should be of some use if a contrib module doesn't bother with documentation.
And then I have a look to see whether I can improve on the Conttent Moderation help?

ifrik’s picture

Status: Reviewed & tested by the community » Needs work

The last submitted patch, 63: 2861849-workflows-help-text-62.patch, failed testing. View results

yogeshmpawar’s picture

Status: Needs work » Reviewed & tested by the community

Setting back to RTBC because above test fails are unrelated.

Status: Reviewed & tested by the community » Needs work

The last submitted patch, 63: 2861849-workflows-help-text-62.patch, failed testing. View results

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

kunalgautam’s picture

StatusFileSize
new3.98 KB
new3.77 KB
_utsavsharma’s picture

StatusFileSize
new1.04 KB
new4.01 KB

Tried to fix CCF for #80.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone made their first commit to this issue’s fork.

quietone’s picture

Status: Needs work » Needs review

Converted to an MR and made some tweaks.

smustgrave’s picture

Status: Needs review » Reviewed & tested by the community
StatusFileSize
new3.67 KB

Had to apply locally to fully read it but addition adding a check for content_moderation seems like a great idea.

Attaching a diff of the last patch with the MR.

  • nod_ committed 564afc4e on 10.4.x
    Issue #2861849 by ifrik, lomasr, prash_98, quietone, pguillard,...

  • nod_ committed ae308e40 on 11.x
    Issue #2861849 by ifrik, lomasr, prash_98, quietone, pguillard,...
nod_’s picture

Version: 11.x-dev » 10.4.x-dev
Status: Reviewed & tested by the community » Fixed

Committed and pushed ae308e40f0 to 11.x and 564afc4ea5 to 10.4.x. Thanks!

amietpatial’s picture

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.