[tracker 243] Field Labels/Names - Show in frontEnd

This is a very common problem that we find in every website we have, please consider improve this.

I will try to 1st explain the problem and 2nd give you an idea how could this be done.

For the matter of the example I have 2 types on content:
1- Job opportunities
2- Events
Both the them have the by default the CORE fields.
1- Title
2- Description
3- ...(+12)
So the TITLE is a required field and a DEFAULT ONE because we use the core com_content, correct?

In the front end or ether the back end the TITILE FIELD LABEL is always "TITLE".

When we are creating an ARTICLE or a blog post the label "TITLE" makes sense, but in the JOB OPPORTUNITY and EVENTS example the label "TITLE" is not 100% correct.

We would prefer YOU NAME for job opportunity and EVENT TITLE for events.

In the job opportunity this is what we had to came up with:
[attachment=2:1thkg9he]<!-- ia2 -->name.PNG<!-- ia2 -->[/attachment:1thkg9he]
In this example we had to create NAME and use TITLE it does not make sense.
If we could CUSTOMIZE the labels per item could be enough.

The other thing bothering us is this title:
[attachment=1:1thkg9he]<!-- ia1 -->name-2.PNG<!-- ia1 -->[/attachment:1thkg9he]
In the Job opportunity should be NEW JOB OPPORTUNITY and in the Events should be NEW EVENT, if not this can confuse the users.

Also, some TEXT FIELD we use them for Querys or for Estatic text, this one we don't want them to show in the FRONTEND, consider a YES/NO option for display in the fronend item submission.

This is our proposal. NOTICE THE CHANGES ARE ON THE RIGTH SITE OF THE IMAGE
[attachment=0:1thkg9he]<!-- ia0 -->name3.jpg<!-- ia0 -->[/attachment:1thkg9he]

The changes:
1- Change the LABEL for DEFAULT LABEL
2- Divide the drop down per ITEM TYPE
3- Select if you want to assign this filed to THIS TYPE
4- Select if you want to show in the item submission form in the front end
5- Custom label for user friendly purposes
6- Select if it is required or it is not required or if this FIELD is associated with another one so FC validate ONE or ANOTHER.

What you guys think?

-- Yes customizing CORE fields per type makes sense since they are obligatory, some parameters like the label, makes sense to be customizable per type.

Of course if we customized per type the CUSTOM fields too, it would result in fewer fields.

But custom fields maybe, we should create a different field if we want different configuration, thus to avoid adding further complexity to the fields and templates.

Will examine this regards

That is exactly it. Reduce the number of fields if possible.

One main issue was considering the TITLE that is mandatory.

Exactly this was my thought: we have (core) mandatory fields that are shared among types and we cannot defined different labels per type, which makes a lot of sense.

I registered this as an enhancement.

Regards

There are 4 parameters for the main text field in the type configuration:

to hide it , use or not the html editor, set a custom label for it and a custom tooltip description,

are you using them?

I havnt seem custom Label. So No, but we Will take a look.

The problem was per/ menu item.

Here the Title is supose to be Curse Title:
academia.ruiromano.com/workshops
but here is supose to be Name:
academia.ruiromano.com/formadores-academia

So in the translation file I called it:
Title or Name