Field setting input->required relation context as name, desc, width

[*Most Powerful Pony!*]

I think that is very useful to set mandatory fields depending on the selected template.

Now, the same field can be used in different templates, ask them different postural signature, and in fact it would be nice and labeled in different templates which of these fields are required!

[kongondo]

I don't get this request. In PW, same fields can already be reused in different templates and can be set as required. And, if you want a field to be always required on every page, you can set it as global + required. Maybe I am missing the point

[*Most Powerful Pony!*]

update screenshots

I mean, unique settings for the template fields, such as description, name, width.

I would like to be there, including field and required. That there was an opportunity, on certain pages content manager say that this field must be filled! 

[Craig]

Maybe an example would help? Is this right?

1. Field "description" is used on templates "architect" and "basic-page".

2. On the "architect" template, this should be a required field. On the "basic-page" template, it is NOT required.

So a field can be required on only certain templates where it is used?

If that's correct, then this is possible with the development version of ProcessWire (not on the demo site in your screenshots). My attached screenshot shows this option - when editing a field from the template.

[kongondo]

...please ignore, I don't know what I was thinking ;-) hehe...I logged into the "wrong" install...

Edited December 30, 2013 by kongondo

[Soma]

lalalala

[*Most Powerful Pony!*]

If that's correct, then this is possible with the development version of ProcessWire

Good! Where can try?

[kongondo]

Good! Where can try?

https://github.com/ryancramerdesign/ProcessWire/tree/dev