Mar 27, 2011 at 12:30 AM
Edited Mar 27, 2011 at 12:32 AM
An Orchard page is composed up of many small view fragments. You don't want to go overriding large sections of the UI; an individual module could get updated but your view would still be displaying the old version. This could mean you lose functionality
or even worse, things could break.
By using placements.info you can do a massive amount of customisation without having to change
any templates (you can even push stuff to different zones in the layout).
See the following thread regarding placement names for fields:
I was just searching for documentation regarding placement.info for parts and other bits, I found this:
Note: It's draft documentation for 1.1 but I think you'll have to be using that anyway for positioning fields.
If you need further help, what I've seen has been kind of scattered around various module authoring tutorials, but I can try and dig up some more. You can also search this forum for placement.info and see what comes up!
The only other problem is:
- EventStart (custom date time field) and EventEnd (custom date time field) - these should appear on the same line.
To handle this I guess you'd have to build a custom "DateRangeField", and supply your own field editor template which included both inputs. Have a read of the following tutorial from the Orchard documentation which details how the DateField is built:
Should be possible to extend that example for a two date range (with some creative thinking!)
Edit: Just one more note; if you want to override a specific part or field's views, you should be able to copy the corresponding file into the same path in your theme structure. So you can customise individual view fragments where needed - with the caveat
that if you ever update to a new version of that module, you should check for anything new in their templates.