Dev: About Conditional Elements

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 a LLIR Webmaster is likely to encounter. Kadence supports four types of conditional elements and sometimes refers to them as hooked elements because they provide a way to add programming-style logic to a website. So far, the LLIR website uses only one type: Content Sections . The conditional elements defined at the time of this writing are described below.

To learn how too add more conditional elements, start by following a tutorial from the Kadence knowledge base.
For instructions on modifying or deleting these elements, see Working with Conditional Elements.

Conditional Elements Currently Defined

Expand an element name below to see the the element’s content, followed by an explanation of its purpose and a description of where and when it appears.

Developer Notes — For administrator Eyes Only

Description

This element gives WordPress administrators convenient access to these Developer Notes. The brown bar above appears before the footer on the Member Home page only when a WordPress administrator is logged in on a large-screen device.

Note: In the LLIR colour palette, a brown background indicates content that end users should never see.

Description

When active, this element appears at the top of the Welcome to LLIR and Member Home pages to warn members of situations at Glendon Campus that may affect their experience attending lectures. When the page opens, a WordPress plug-in replaces the characters “current_date” with the current date.
Switch it on shortly before a lecture day. For instructions, including how to customize the text for specific situations and set the automatic turn-off time, see How to Display a Facilities Notice.

Description

When active, this element appears at the top of the Welcome to LLIR and Member Home pages to inform members that lectures are cancelled due to snow or other weather events. When the page opens, a WordPress plug-in replaces the characters “current_date” with the current date.
Switch it on in the morning of (or evening before) the affected lecture day. For instructions, including how to set the automatic turn-off time, see How to Display the Lectures Cancelled.

Please Log In

Description

This message above appears whenever a user who is not logged in tries to open a member-only page. Its white background is displayed as light grey above. How the conditional element works and how to adjust it after adding a new page to the website is explained in the page How to Suppress the Please Log In Message.
For related information, see Public and Member Only Pages and Security Matters.

Note: This element does not ensure complete login security. Users can scroll down to see the page contents but cannot access the Member Menu without logging in.

The Waitlist is Open

We are now adding names to our waitlist. The size of the waitlist is limited to attempt to keep the time that applicants can expect to wait for membership to under two years.

When your name rises to the top of the waitlist, we send an email inviting you to become a member of LLIR and to register for courses.

Note: Applications carry forward from year to year. Please do not apply again if you did so within the last few years.

Ready to Apply?

Be sure to review the considerations listed above so we can process your form successfully. Then complete the form that opens when you click the button below.

Description

When this element is active, the message that the waitlist is open and the button that links to the waitlist application form appears on the Waitlist Process page. Its white background is displayed as light grey here. The instructions How to Open or Close the Waitlist describe how a WordPress administrator can open and close the waitlist as directed by the Registrar.
For an explanation why this element is no longer in use, see How Menus Can Change During LLIR Processes.

The actual element and its associated pages in the Developer Notes have not been deleted in case they they may serve as an example of building dynamic content into the website in the future.