Requested by: Meghan Reid
Requires a new CMS Component?: No
Requires New Functionality?: No
On May 16, 2022, at 2:59 PM, Quilala, Steve <firstname.lastname@example.org> wrote:
Echoing Randy’s statements also. We strongly discourage tables on the CMS in general and they were intentionally left off the directory WYSIWYG fields because it would be overused and easily broken by novice users.
We do not support adding this ability back to the profile fields. Adding tables back in would simply result in more confusion and frustration than before.
Steve Quilala (He, Him, His)
Programmer Analyst 1 – Web Designer/Developer
UBC IT Okanagan | Web & Applications
The University of British Columbia | Okanagan Campus | Syilx Okanagan Nation Territory
1138 Alumni Avenue, ADM 024 | Kelowna BC | V1V 1V7 Canada
Phone 250 807 9918 Ext. 79918
From: “Lievers, Randy” <email@example.com>
Date: Tuesday, May 10, 2022 at 10:54 AM
To: UBCO-OKIT UBC Okanagan Web Services <firstname.lastname@example.org>, “Quilala, Steve” <email@example.com>, “Shaji, Jithin” <firstname.lastname@example.org>, “Edwards, Jamie” <email@example.com>
Subject: Re: CMS Enhancement Request Submission
I don’t think this is a good idea at this point in time because the content of really long tables cuts off unless there is code added to the individual table.
This is problem already for communicators; it will be even more problematic if we roll this out the faculty members within the Central Directory.
I’m open to discussion options and ideas.
Ticket Number: N/A
Media (Screenshots, etc.)
No media uploaded...