Closed (fixed)
Project:
Pathauto
Version:
8.x-1.x-dev
Component:
Code
Priority:
Minor
Category:
Task
Assigned:
Reporter:
Created:
15 May 2016 at 02:19 UTC
Updated:
6 Jul 2016 at 18:24 UTC
Jump to comment: Most recent, Most recent file
The Help text page is present but is a little off the Help text standard (for core and contrib).
Make a few edits to the help text provided to bring it closer to the standard.
| Comment | File | Size | Author |
|---|---|---|---|
| #14 | tweak_pathauto_help-2725555-14.4.patch | 3.87 KB | Bambell |
| #8 | 2725555-Tweak_Pathauto_HELP-8.patch | 5.34 KB | dbt102 |
| #3 | 2725555-Tweak_Pathauto_HELP-3.patch | 6.05 KB | dbt102 |
Comments
Comment #2
dbt102 commentedComment #3
dbt102 commentedComment #4
dbt102 commentedComment #5
alexdmccabeWhy were the help messages for the other routes removed?
Comment #6
dbt102 commentedhmmm... good question ... that wasn't my intent ... I took them out temporarily because they all didn't seem to be working correctly. I mean't to figure out why and put them back in, but I forgot about them.
I've been working a lot of HELP text for several projects and this is the first one I remember where "3. Help text on administration pages" of the Help text standard (for core and contrib was actually implemented in hook_help .
I need to review function hook_help and see how to put the help messages back in for the other routes.
Comment #7
dbt102 commentedComment #8
dbt102 commentedI put the help messages back in for this #8 patch. I removved them to begin with because I was working with D8.2.x-dev and they did not seem to do anything. When I looked of the admin pages where the messages should be, there were no messages. So based on @alexdmccabe comment in #5 I looked closer. This time working with drupal 8.1.x-dev, the admin page help showed up ok.
So, I figure if this new patch #8 tests OK, then there is another issue with Drupal Core 8.2.x-dev that needs investigated, because the behavior noted applies to all core and contrib modules, ie admin page help does not work properly.
Comment #9
berdirThanks for working on this.
The part about the limit by database is no longer true. The limit is 255. @max is also actually broken and shows up on the page.
Comment #10
dbt102 commentedthanks for the review/feedback @Berdir.
imo ... the whole paragragh you refernece in comment #9 seems kind of out of place for the module's Drupal Help page.
It's a very detailed, specific kind of instruction that I would expect to find in something like an installation guide for developers. This module's help overview page points to https://www.drupal.org/documentation/modules/pathauto , so as a -dev , I'd expect to go there to find that info.
So, would it be ok with you I I just drop that paragraph?
Comment #11
rajeshwari10 commentedI ave replaced @max with 255 as said in #9.
Please review.
Thanks!!
Comment #12
berdirThanks, but the paragraph is stil lconfusing and too detailed, agreed with #10 on that. Fine with removing or shortening it. We could also check the descriptions of the relevant form fields and ensure we have enough explanation of it there.
Comment #13
Bambell commented@dbt102, this issue is currently assigned to you. Would you like to continue working on this issue or could someone else pick it up? Thanks.
Comment #14
Bambell commentedPatch wouldn't apply. Am I dyslexic or was it already committed? The current help page looks like what patch #8 was intended to produce. I shortened the paragraph in #9 to something just sufficient to warn the user that an incorrect value can be a problem and to indicate to developers what exactly is needed. I also quickly reviewed all forms fields and the help page looks sufficient to me. I added "An alias is generated for the first pattern that applies." to the "Creating Pathauto Patterns" section.
String replacement was missing..
Interdiff of #11 is fine, but the patch has 11 KB of non relevant changes.
Comment #15
berdirYes, I accidently committed the previous patch already as part of another issue, sorry about that.
Committed this now.
Comment #17
dbt102 commentedThanks for stepping up to help with this @bambell and @rajeshwari10 . I got distracted on some other issues. Glad to see this got worked out. Thanks for your efforts too @berdir.