Forums / Developer / How to add a graphic showing required fields on the entry screens?

"Please Note:

At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

How to add a graphic showing required fields on the entry screens?

Previous topic

Developer

Next topic

Author	Message
Stuart Fenton	Thursday 03 April 2003 3:15:59 am I am trying to include a graphic (just a * character) to illustrate the fields that are required. How do I do this? I have created a case statement but need to know the object to access. For example: {switch match=$ClassAttribute:item.classAttribute_IsRequired} {case match=0} {/case} {case match=1}*{/case} {case} Matched default {/case} {/switch} What is the correct object to access? -- Stuart stuart@grandmore.com http://www.grandmore.com
Jan Borsodi	Friday 11 April 2003 7:26:27 am Do you mean in the content edit fields? How you access the attributes depends on whether you want a general implementations (ie. looping the attributes) or specific (using attribute names). The first is simply to look at the code in design/standard/templates/content/edit_attribute.tpl, create an override by placing it in design/mydesign/override/templates/content/. For example: {section name=ContentObjectAttribute loop=$content_attributes sequence=array(bglight,bgdark)} <div class="block"> <label>{$ContentObjectAttribute:item.contentclass_attribute.name}{section show=$ContentObjectAttribute:item.contentclass_attribute.is_required}{/section}</label><div class="labelbreak"></div> <input type="hidden" name="ContentObjectAttribute_id[]" value="{$ContentObjectAttribute:item.id}" /> {attribute_edit_gui attribute=$ContentObjectAttribute:item} </div> {/section} The code that matches is: {section show=$ContentObjectAttribute:item.contentclass_attribute.is_required}{/section} The second way is to access the attribute trough the data_map array, for instance to get the attribute named name. {section show=$object.data_map.name.contentclass_attribute.is_required}*{/section} -- Amos Documentation: http://ez.no/ez_publish/documentation FAQ: http://ez.no/ez_publish/documentation/faq

Author

Message

Stuart Fenton

Thursday 03 April 2003 3:15:59 am

I am trying to include a graphic (just a * character) to illustrate the fields that are required. How do I do this?

I have created a case statement but need to know the object to access. For example:

{switch match=$ClassAttribute:item.classAttribute_IsRequired}
{case match=0} {/case}
{case match=1}*{/case}
{case}
Matched default
{/case}
{/switch}

What is the correct object to access?

-- Stuart

stuart@grandmore.com
http://www.grandmore.com

Jan Borsodi

Friday 11 April 2003 7:26:27 am

Do you mean in the content edit fields?

How you access the attributes depends on whether you want a general implementations (ie. looping the attributes) or specific (using attribute names).

The first is simply to look at the code in design/standard/templates/content/edit_attribute.tpl, create an override by placing it in design/mydesign/override/templates/content/. For example:

{section name=ContentObjectAttribute loop=$content_attributes sequence=array(bglight,bgdark)}
<div class="block">
<label>{$ContentObjectAttribute:item.contentclass_attribute.name}{section show=$ContentObjectAttribute:item.contentclass_attribute.is_required}*{/section}</label><div class="labelbreak"></div>
<input type="hidden" name="ContentObjectAttribute_id[]" value="{$ContentObjectAttribute:item.id}" />
{attribute_edit_gui attribute=$ContentObjectAttribute:item}
</div>
{/section}

The code that matches is:
{section show=$ContentObjectAttribute:item.contentclass_attribute.is_required}*{/section}

The second way is to access the attribute trough the data_map array, for instance to get the attribute named name.
{section show=$object.data_map.name.contentclass_attribute.is_required}*{/section}

--
Amos

Documentation: http://ez.no/ez_publish/documentation
FAQ: http://ez.no/ez_publish/documentation/faq