Search the Community
Showing results for tags 'fields fieldtypes'.
Found 1 result
-
Hi there, For one of my templates I have a start date and an end date. Both fields are effectively the same type of input and output. Rather than create two fields can I add the field twice and customise the label in the template? I thought this might be possible using field-template context but realised the problem is that a fieldtype is unique and can only be added once. This example stems to a bigger concern. When I create the fields needed for my template, each of my fields effectively serve the same purpose regardless of what template they are on, the only difference is they have different contexts depending on the template. The field-template context option allows me to avoid creating fields like book_title and book_price. As I can just create one field called price. Which means that if I create a new template of movie, I can re-utilise the same field for give different descriptions based on the template. Unfortunately this model stops working when the same fieldtype is needed inside the same template. For example lets say I need two more fields one might be for a featured image and another for generic images I must create a field called featured_image and another one called images. This example might be debatable because you could say that this should be controlled by creating a custom fieldtype module with a checkbox for featured images. So what are you thoughts on using fields and their modularity? Lets say you had a site with a shop and a blog. How would create and name your fields? Would you have fields like: blog_title blog_body blog_author product_title product_body product_price or would you have... title body author price ps. I've really enjoyed developing with ProcessWire, for a designer at heart it has been super easy for me to build a site with my own markup without sacrificing the back end. Thank you to everyone who's been involved in it's development.
