Problem/Motivation

The help text of the Content Moderation module does not follow the Help text standards as described in https://www.drupal.org/help-text-standards.
The descriptions should be so generic that they work for example for different admin themes where links are not displayed as blue buttons, and they should contain the relevant links.

Proposed resolution

Editing the text according to the standard.

Remaining tasks

  • Edit the headers in the Uses section
  • Edit the Uses descriptions
  • Add the relevant links is the Uses descriptions

User interface changes

This is a UI text change

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

ifrik created an issue. See original summary.

ifrik’s picture

Component: content_moderation.module » documentation
Issue tags: +user interface text
chanderbhushan’s picture

Status: Active » Needs review
FileSize
2.37 KB

Hi,

I have added patch for links.

kiwimind’s picture

Status: Needs review » Needs work
+++ b/core/modules/content_moderation/content_moderation.module
@@ -35,11 +35,11 @@ function content_moderation_help($route_name, RouteMatchInterface $route_match)
+      $output .= '<dd>' . t('Each state is exposed as a <a href=":permission">permissions</a>. If a user has the permission for a transition, then they can move that node from the start state to the end state', array(':permissions' => \Drupal::url('user.admin_permissions'))) . '</p>';

:permission vs :permissions.

Otherwise, looks good and reads fine.

th_tushar’s picture

Status: Needs work » Needs review
FileSize
2.38 KB

Updated the patch. Looks good now.

Status: Needs review » Needs work

The last submitted patch, 5: edit_hook_help_2830832_5.patch, failed testing.

timmillwood’s picture

Issue tags: +Needs reroll, +Novice

Patch fails to apply, so needs rerolling.

Keenegan’s picture

Status: Needs work » Needs review
Issue tags: -Needs reroll
FileSize
2.42 KB

I tried to reroll #5 with https://www.drupal.org/patch/reroll.

Indicate whether it was an auto merge, if there were conflicts or if the file sizes were very different. If there were conflicts, describe what you did to resolve them. This will make it easier for the person reviewing the patch to know how carefully they need to review.

I had a conflict,

<<<<<<< 2d4af397bc894e59e84178a74b0ef3b02e632a3e
      $output .= '<dt>' . t('Configuring workflows') . '</dt>';
      $output .= '<dd>' . t('Enable the Workflow UI module to create, edit and delete content moderation workflows.') . '</p>';
      $output .= '<dt>' . t('Configure Content Moderation permissions') . '</dt>';
      $output .= '<dd>' . t('Each transition is exposed as a permission. If a user has the permission for a transition, then they can move that node from the start state to the end state') . '</p>';
=======
      $output .= '<dt>' . t('Moderation states') . '</dt>';
      $output .= '<dd>' . t('Moderation <a href =":states">states</a> provide the <em>Draft</em> and <em>Archived</em> states as additions to the basic <em>Published</em> option. You can click the blue <em>Add Moderation state</em> button and create new states.', array(':states' => \Drupal::url('entity.moderation_state.collection'))) . '</dd>';
      $output .= '<dt>' . t('Moderation state transitions') . '</dt>';
      $output .= '<dd>' . t('Using the <a href=":transitions">"Moderation state transitions"</a> screen, you can create the actual workflow. You decide the direction in which content moves from state to state, and which user roles are allowed to make that move.', array(':transitions' => \Drupal::url('entity.moderation_state_transition.collection'))) . '</dd>';
      $output .= '<dt>' . t('Configure Content Moderation permissions') . '</dt>';
      $output .= '<dd>' . t('Each state is exposed as a <a href=":permissions">permissions</a>. If a user has the permission for a transition, then they can move that node from the start state to the end state', array(':permissions' => \Drupal::url('user.admin_permissions'))) . '</p>';
>>>>>>> Applying patch from issue 2830832 comment #5

I removed the "first" part and kept the "second" one, I hope it was the right thing to do. It's my first contribution, so if I did something wrong tell me what please :)

Status: Needs review » Needs work

The last submitted patch, 8: reroll_edit_hook_help_2830832_6.patch, failed testing.

timmillwood’s picture

@Keenegan - I think we needed to keep a mixture of the "first" and "second" sections. The failing tests are because the help text is now missing some expected components.

th_tushar’s picture

Status: Needs work » Needs review
FileSize
2.02 KB

Rerolled the patch.

Status: Needs review » Needs work

The last submitted patch, 11: edit_hook_help_2830832_11.patch, failed testing.

Keenegan’s picture

Status: Needs work » Needs review
FileSize
2.03 KB

Re-rolling again

Status: Needs review » Needs work

The last submitted patch, 13: edit_hook_help_2830832_13.patch, failed testing.

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

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

Jeff Cardwell’s picture

The original help page was changed greatly in another commit (Add a workflow component, ui module, and implement it in content moderation) since this issue was opened. This is why the patches are failing. Because of the extensive nature of those changes, It appears that the changes in this issue may no longer be applicable. However, there are two places where <dd> elements are closed with </p> tags in the new file as well. I have corrected these tags and created a new patch reflecting only this change.

rocketeerbkw’s picture

Status: Needs work » Needs review
kiwimind’s picture

Status: Needs review » Reviewed & tested by the community

This patch got a bit simpler! Even more straightforward.

All seems to make sense, especially in light of some of the other changes being made as mentioned by @rocketeerbkw.

Thanks.

ifrik’s picture

Status: Reviewed & tested by the community » Needs work

Thanks a lot,
but this text doesn't quite follow the UI text standards for it and still misses the links, as lined out in the description of this issue.

I'll come back with more detailed comment later today.

kiwimind’s picture

Apologies, I thought that this ticket was heading towards the simpler end of the scale, rather than just reproducing what had already been done in #13.

Jeff Cardwell’s picture

I added back in a link to the permissions page in the uses section, but it seems strange to do so since it is listed as an administration page immediately after. Additionally, the state of the module seems to be a bit in flux. Perhaps it is settling down now. The link to the documentation is live, but the documentation does not reflect the current design of the module.

rakesh.gectcr’s picture

Status: Needs work » Needs review

Ones you worked the issue and uploaded patch, please change the status to 'Needs review';

prash_98’s picture

Status: Needs review » Reviewed & tested by the community

The patch of #21 applies well and I guess the status can be changed to RTBC.

ifrik’s picture

Status: Reviewed & tested by the community » Needs work

The help text is not available to users if the module is not enabled, so the point about enabling the module needs to be removed.

There are some uses missing: such as that workflows need to be added to entity types to become available, or that users can their own states. These need explaining.
It's also worth mentioning that the module overwrites the default "Edit" tab and "Save" button with custom values.

I only had an initial look at the module, so I don't know what other functionality is there, but what ever there is needs to be described in the help text.

xjm’s picture

@prash_98, keep in mind again that the automated testing infrastructure tells us whether the patch applies, so we do not need people to review that. What we do need people to review is whether the issue has a correct scope, whether it passes the core gates, whether the solution completely fixes the problem without introducing other problems, and whether it's the best solution we can come up with. See the patch review guide for more information. Thanks for your contributions!

Thanks @ifrik, agreed. For contributors on this issue, the best way to decide what to put in the help text is to test the module and see what it does, considering what features should be explained, if there are any gotchas, etc.

prash_98’s picture

@xjm will surely keep in mind for the other issues.

prash_98’s picture

@xjm,

The module is failing to get installed. The site crashes on enabling the module.

timmillwood’s picture

@prash_98 - Can you open a new issue with the issues you are getting when enabling the module?

prash_98’s picture

@timmillwood -Yes would open one.

kimble’s picture

Issue tags: +Baltimore2017

Working on this @Baltimore2017.

Roya-Rateshtari’s picture

Assigned: Unassigned » Roya-Rateshtari
Issue summary: View changes
Status: Needs work » Needs review
FileSize
2.72 KB

I applied the patch #21 and it fixed the Uses description tags, and I noticed the links to workflow was missing. I just added the link to workflow.

rakesh.gectcr’s picture

Status: Needs review » Needs work
pritish.kumar’s picture

Status: Needs work » Needs review
FileSize
1.48 KB
2.87 KB

Corrected the coding standards errors.

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.

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

Assigned: Roya-Rateshtari » Unassigned
Status: Needs review » Closed (outdated)

The help text has been updated as part of another commit and doesn't need changing anymore.

dmkelner’s picture

@ifrik, can you point to where this was done?