Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Putting in the 7.x-3.x queue for now, can backport to 6.x-2.x later.
Putting in the 7.x-3.x queue for now, can backport to 6.x-2.x later.
Comments
Comment #1
TR CreditAttribution: TR commentedSee #629620: Ubercart: Add basic documentation to Cart admin and #996946: Wrap help text in ubercart and #1012594: Catalog settings not working for some things that should go into hook_help().
Comment #2
TR CreditAttribution: TR commentedHelp text standards: http://drupal.org/node/632280
If you want to help out and learn how to contribute patches, this would be a good simple task to get started!
Comment #3
TR CreditAttribution: TR commentedComment #4
longwaveAs well as hook_help, is it worth bringing the documentation from ubercart.org and drupal.org into the download via http://drupal.org/project/advanced_help in a similar way to Views?
Comment #5
TR CreditAttribution: TR commentedI'm not a big fan of putting everything into advanced help. In order to use that documentation, you not only have to set up a website but you have to install the module you want help on and install advanced help, all just to read the documentation. Then maybe you find out you don't want to use that module because it doesn't do what you thought it did. Big waste of time and effort. I understand the limitations of the current hook_help() mechanism, but Drupal is not moving to advanced help as the solution. There has been a lot of progress in the community documentation on drupal.org recently, and I favor improving the Ubercart documentation at http://drupal.org/documentation/modules/ubercart, which is where the community is pushing to have this sort of thing. That way the documentation gets indexed by search engines and the information is not only more accessible but also more findable than it would be in advanced help. Likewise, having the documentation on drupal.org gives us permanent URLs to point people to when they have questions, and allows the community to participate in improving the documentation, and allows us to keep the documentation up-to-date without pushing out a new release. We could even link to the drupal.org documentation from within our hook_help() methods, rather than inlining and distributing all the documentation along with the module.
Comment #6
TR CreditAttribution: TR commentedComment #7
Shashwat Purav CreditAttribution: Shashwat Purav commentedComment #8
Shashwat Purav CreditAttribution: Shashwat Purav at Iksula commentedComment #9
TR CreditAttribution: TR commented@Shashwat Purav - You assigned this issue to yourself more than a month ago - are you still planning on working on this and submitting a patch?
Comment #10
TR CreditAttribution: TR commentedComment #11
gfcamilo CreditAttribution: gfcamilo at CI&T commentedComment #12
gfcamilo CreditAttribution: gfcamilo at CI&T commentedComment #13
JayKandariI think Issue description should be updated corresponding to version : 8.x-4.x-dev. Kindly Confirm. Thanks
Comment #14
JayKandariThis might help anyone who picks up this issue.
Following sub modules have already implemented
hook_help()
. Some of them needs fix.Ubercart Submodules.
It'd be great if maintainer can give help by providing exact texts to use as help description for each of the above modules those do not have hook_help() implemented.
Thanks!
Comment #15
TR CreditAttribution: TR commentedYou're not helping me if you need me to provide all the text.
I think this task is self-explanatory - all the modules in Ubercart need review to update/enhance/create the information in hook_help() in order to make the help mechanism more useful to Ubercart users and to take advantage of changes that Drupal core has made to the help system (e.g. https://www.drupal.org/node/2669966 and https://www.drupal.org/node/2669988). I would also like to see some links pointing to the more detailed help documents under http://drupal.org/documentation/modules/ubercart, and improvement of that documentation as needed.
If you don't know enough about the modules, then this is a great way to learn more about Ubercart - do the research and come up with a help implementation that is useful to you as a new Ubercart user. That's why this is marked as a Novice issue. A review of Drupal core to see what sort of information is typical would be a good start, but be aware that a lot of Drupal core also needs some work on hook_help().
Comment #16
JayKandariPicking this.
Comment #17
JayKandariHi,
Please find changes done in attached patch.
All modules reviewed and updated/added their
hook_help()
implementations.Help texts standards as per Drupal Template (https://www.drupal.org/node/632280).
Help pages contain links to specific pages of Ubercart documentation.
Kindly Review. Thanks :)
Comment #19
JayKandariTest failed because of :
uc_cart_links/src/Tests/CartLinksTest.php:97:
Help here !! What todo next?
Comment #20
TR CreditAttribution: TR commentedThis looks like a good start.
uc_cart_links has a better help implementation than any other module in Ubercart, so it should be used as an example. Specifically, any help text other than trivial one-liners should probably be put into a Controller class like uc_cart_links does - this way the help text is only loaded when needed, not on every single page view, and the help text can be maintained separately from the code in .module.
uc_cart_links also has a test case which tests to make sure the help text shows up where expected. The reason that test fails is because you redefined help.page.uc_cart_links, so that page no longer contains the text that the test is looking for. If you want to modify the help text at help.page.uc_cart_links then you need to modify CartLinksHelpController.
Comment #21
JayKandariComment #22
JayKandariReverted defining help.page.uc_cart_links case in
uc_cart_links.module
file.Added, section headers to
uc_cart_links/src/Controller/CartLinksHelp.php
file.Local tests passed successfully. Changing status.
Kindly Review :) Thanks !
Comment #23
JayKandariComment #24
sumitmadan CreditAttribution: sumitmadan at QED42 commentedComment #25
JayKandariComment #26
TR CreditAttribution: TR commented@sumitmadan: It would help if you would detail what you looked for when you reviewed the patch, that way we would know that your review added value and was not simply a favor for a co-worker... As it stands, your RTBC isn't saving me any effort because I don't know what has been examined already ...
I noticed several unneeded "use" statements added in, as well as at least one line that was apparently accidentally modified - "affiliate' sales". I would also like to examine the provided links before this goes in - most appear to point to the top-level ubercart documentation page, but I think there are probably more specific places to link to. Or if not, then those more-specific pages should be created because this points out gaps in our documentation. Also a style note: we prefer [] instead of array() in most places, especially for the second parameter passed to t(). And trailing "," for array elements are only appropriate if the array elements are each on separate lines, like you might do in a form definition, not when the elements are inline.
Comment #27
JayKandariComment #28
JayKandariUpdated previous patch
* Unnecessary use statements removed.
* changed array() to [].
* corrected existing texts.
* trailing commas in inline arrays removed.
* help linked with Main ubercart online document, specific settings documentation pages and to internal links.
Kindly Review, Thanks !!
Comment #29
Yago Elias CreditAttribution: Yago Elias as a volunteer and at CI&T commentedSome minor code standards issues in last @jayKandari patch
Comment #30
gmaltoni CreditAttribution: gmaltoni at CI&T commentedHi @yago-elias,
It's good for me.
Congrats.