DEPRECATED
| Name | Internal name | Searchable | Information collector |
|---|---|---|---|
| Enum | ezenum | Yes. | No. |
This datatype should not be used any more because it is slow. It has been substituted by the "Selection" datatype.
This documentation stores what it needs to work: a session cookie when you sign in or keep a setting such as the help menu shown or hidden, the design you chose (Classic or Modern) and your language. Only if you agree, it also uses Google Analytics (through Google Tag Manager) to count visits; until then nothing is loaded from Google. Your choice is kept in a cookie for 6 months, and you can change it at any time under "Cookie settings" at the foot of every page. Details are in our Cookie Policy.
The session cookie for signing in and for forms, the cookies that keep your design and language, and the cookie that keeps this choice. They stay on because the website needs them; you can delete them in your browser settings at any time.
Google Analytics, loaded through Google Tag Manager (GTM-MPGWKTQV), counts visits and shows us which pages are read: the pages you open, the page you came from, your browser, device and screen size, and your approximate location derived from your IP address. Google processes the data for us and may transfer it to the USA. It sets the cookies _ga and _ga_* for up to 2 years. Off until you turn it on; when you turn it off again, Google is no longer loaded and these cookies are deleted.
Comments (3 historical)
Written by readers of the earlier documentation sites, kept as they were.
Deprecated Enum
Blue lue Boy ·
Although I understand Selection is faster than Enum, it doesn't exactly match usage of the latest. Using Selection forces us to store choices as an array from 0 to n rather than a hash widh any type of keys and values.
Should we expect the deprecated enum to be removed shortly or can we still keep using it until the Selection can handle pairs of key => value ?
Re: Deprecated Enum
Marco Zinn ·
I very much agree with that question.
In cases where you need a key, enum is the better (and only?) way for this at the moment.
docs
pike ·
the .content of an ezenum attribute returns a enum object, which has at least an .enumobject_list property that is a list of strings. from the datatype / view template:
{section var=Elements loop=$attribute.content.enumobject_list sequence=array( bglight, bgdark )} {$Elements.item.enumelement|wash( xhtml )}<br /> {/section}if anyone knows a link to legacy documentation of this object, let us know !
*-pike