Some features of the LLIR website depend upon conditional elements. Creating and maintaining conditional elements requires no knowledge of coding or HTML, but working with them is one of the more advanced topics in these Developer Notes. Kadence supports four types of elements and sometimes refers to them as hooked elements because they provide a way to add programming-style logic to a website. This page describes only one type — Content Sections — because they are the simplest type of element.

You can find the description of elements currently defined in the LLIR website further down this page.

The Content and Conditions of Elements

Building and editing the content of a conditional element is similar to authoring any ordinary page. The power of conditional elements comes from the flexibility in where you can place them within pages throughout the website and the conditions that control whether they appear or not. These conditions are the element settings that control the behaviour of the element. Read what goes into an element in the Kadence Knowledge base for an overview of the element settings.

Working with an Element

The following list gives brief instructions.

1. Open the Element panel:
   From the WordPress Dashboard, open the Appearance menu and select Elements.
2. Select or create an element to work on:
   • To create a new element, click the Add New button at the top of the Element panel.
     1. Enter a title (give the element a name).
     2. Select type Content Section.
   • To modify an existing element, locate it in the Element panel and click Edit below the element’s name.
3. When you edit an element’s contents, the Document Overview, Editing and Settings panels are the same as for editing pages.
4. Open the Element Settings panel by clicking the Element Settings icon (immediately to the right of the Update button).
5. Set the conditions for your element using the settings listed in the table of element settings below this list.
6. When you are done, click Update to publish the element.
7. Test thoroughly by visiting pages in the website. Make sure you test under different conditions to check the following:
   • The element appears when and where you want it to.
   • The element does not appear anywhere else.

Table of Element Settings

These settings give you the power to add conditional behaviour to a website without writing code.

Setting Name	Description	Example/Comment
Element type	Should be Content Section	All existing elements are Content Sections.
Preview settings	The default is usually appropriate for pages. These settings usually apply to websites composed of posts rather than pages.
Place- ment	This dropdown list shows where you can position the element within a pages. The most common placements are below the page header or before the footer.	The Developer Notes element appears above the page footer.
Priority	The default is usually adequate. If elements and their settings produce conflicts, element priorities determine which element’s conditions apply first.
Display Settings	This expandable set of options controls which pages the element appears on. You can specify pages by category or select pages individually, You can also exclude specific pages.	The Waitlist Open element can appears only on the Waitlist Process page.
User Settings	Expand this option to see a dropdown list from which you can select the category of user who can see this element (typically by user role or whether logged in).	Only users in the administrator role can the Developer Notes element.
Device Settings	Expand this option to see a dropdown list from which you can select that element appears only on Desktop (relatively large) screens or Mobile (smartphones and small) screens.	The Developer Notes element appears only on relatively large screens.
Expiration	Expand this option and set Enable Expires for elements that appear only at specific times. Then you can set the expiry date and time (in the Toronto time-zone).	Whether the WaitList Open element is visible at any specific time depends on its expiry date.

Warning

The power and flexibility of conditional elements comes with the potential of complicating the logic required to combine elements and element settings to get the intended results. If you add more conditional elements, think carefully through all possible combinations that may apply to the same pages.

The Elements Currently Defined

The rest of this page lists and briefly describes the three conditional elements defined so far. All are Content Sections, the most common and useful type of conditional element. If you want to add more conditional elements, start by following a tutorial from the Kadence knowledge base.

Element: Developer Notes

The purpose of this element give administrators convenience access to these Developer Notes. Its contents are shown below and have a brown background. This element appears above the footer on the Member Home page. It is displayed only when the current user is an administrator and and is using large screen device.

Developer Notes — For administrator Eyes Only

---

Element: Member-Only Page

This element appears on all pages in the member-only area of the website, including the Developer Notes, whenever a user who is not logged in tries to open a page without logging in. Its white background is displayed as light grey here. Pages in the public area of the website are exempted from this element, as explained in the Developer Note How to Suppress the Please Log In Message.

Please Log In

---

Element: Waitlist Open

Warning: This Element is not in use

For an explanation see the How to Open and Close the Waitlist page.

This purpose of this element is to display some text followed by the link to waitlist application form on the Waitlist Process page only when the waitlist is open. The contents of this element are shown below displayed on light grey background. Refer to How to Open or Close the Waitlist for instructions for using this element.