In the project node created by case_tracker.module, there is a add Case link; the link should be renamed add case, to follow the way Drupal uses to name the links showed under the node body.

Comments

jmiccolis’s picture

jmiccolis commented
Status: Active » Closed (works as designed)

That link is auto generated based on the name of the node - which here is "Case". If you'd like to alter how the name is presented you could consider using the css "text-transform" property in your stylesheet, or you may prefer to change the name of the node type to 'case'.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

The module could simply pass the content type name to drupal_strtolower().

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Closed (works as designed) » Active

The module uses for the Operations links two different, and inconsistent strings.
If one link is open Case (where Case is the content type name used for the reports), the other link is view all project cases. This means that if I would use a content type named Ticket for the reports, the links I see would be open Ticket, and view all project cases.

It would be better if the module would use case (and cases) in the links, or it would use the content type name in lower characters (but this would mean the module should also use the plural of the content type name in the second link).

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

Is there any progress in this?

shas3n’s picture

shas3n commented

+ 1 for this feature.
I am using Casetracker in a non-software context and it does not make sense to create a 'Case'. So I have named the node to 'task' so that the node creation form says 'Create Task' but the project summary page has a hard coded link 'See all project cases'.
It would be great to have all the links get their name from node name rather than the current hard-coded way.

jmiccolis’s picture

jmiccolis commented
Component: Code » User interface
Status: Active » Needs work

Hi, I'm open to better language and/or markup here but I'm not ok with adding extra code like a call to drupal_strtolower() as suggested in #2 as I don't want to make assumptions about usage - we should move away from such assumptions.

Patches or detailed ideas are very welcome here.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Issue summary: View changes
Status: Needs work » Closed (outdated)

I am closing this issue, which is for a not supported Drupal version.