Jump to content

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


Recommended Posts

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 :-)

Link to comment
Share on other sites

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.

post-1537-0-79952200-1388408904_thumb.pn

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...