Looking at `image_26bcba.jpg` and `image_26bc62.png`, you have caught a major structural bug and an equally important UX limitation. ### 1. The Troubleshooting Diagnosis (Why it reads Jan 1, 1970) In `image_26bcba.jpg`, the browser's native HTML5 `` picker formats the dates as strings like `2026-06-12T16:40`. However, when saved, your server receives that string and doesn't explicitly parse it before writing it to the database post-meta. When the frontend grid loads in `image_26bc62.png`, the rendering engine runs `strtotime()` on a raw unparsed string. Because the string value format doesn't match what the function expects, it breaks down and reverts to the standard Unix epoch baseline: **January 1, 1970**. ### 2. The Expert UX & Flow Critique From an enterprise UX standpoint, a single date picker fails because **it only defines a starting point, not a duration or an end point.** If a Mentor selects `06/12/2026 04:40 PM`, the Mentee has no idea if they are booking a quick 15-minute introductory check-in, a 30-minute strategic conversation, or a full 1-hour coaching block. This introduces massive friction: * **Mentor Anxiety:** Mentors won't publish slots if they are worried a session will blindly bleed past their next commitment. * **Mentee Hesitation:** Mentees don't know how much content or how many questions to prepare because they don't know their time budget. ### 3. The Best-Practice Blueprint Solution To match the premium feel of tools like Mentorship Rocket or Calendly, we need to completely redefine the database structure and the frontend interface to handle a clean **Time Slot + Duration Flow**. Instead of making users manually type durations, the best practice is to pair a **Start Date & Time picker** with a crisp, brand-aligned **Duration Dropdown Menu** (e.g., 30 Minutes, 45 Minutes, 1 Hour). --- ### Rebuilding the Engine: Plugin Version 1.5.0 I have completely refactored the entire code file below to solve the Unix epoch date bug and implement the advanced time slot architecture. #### What this new code does: * **Fixes the 1970 Bug:** Properly handles the date formatting strings so they save and display flawlessly. * **Introduces Duration Architectures:** Adds an explicit structural dropdown for every individual slot on the backend registration panel. * **Polishes the Frontend UX:** The public gallery cards now render calculated end-times and clean duration badges (e.g., `Jun 12, 2026 @ 4:40 PM - 5:40 PM (60 Mins)`), removing all guesswork for the mentee. You can follow the exact dashboard update steps you used previously to deploy this updated file! ### File: `law-society-mentorship-poc.php` ```php
Qualifies for 1.0 CPD hour, all of which qualify for Ethics
Lawyers are often contacted after a cybersecurity incident is believed to be finished. Systems may be back online, and the organization may believe the issue is contained. In many cases, however, communications have not yet gone out or have been sent before the organization has fully considered its legal, regulatory, insurance, or contractual obligations. This stage is where gaps can frequently surface and where legal exposure may increase.
This session focuses on what lawyers commonly encounter once the urgency of the initial incident has quieted. Timelines may be incomplete, documentation may be missing, and early decisions, particularly around communications, may not be clearly recorded or may have been made without full advice. Clients may be unaware that regulatory obligations, insurance conditions, or contractual duties remain outstanding, or that earlier actions may narrow their options going forward.
In some cases, the root cause has not been addressed, and the organization may still be vulnerable. Participants will learn how to recognize these signals of trouble early, how to ask practical and targeted questions, and how to guide clients toward steps that may help reduce further risk. The session emphasizes legal awareness rather than technical expertise and supports lawyers in identifying the issues that tend to matter most at this stage of an incident.
Participants will leave with:
Presenters:
David Krebs, Miller Thomson LLP
Brennen Schmidt, ALEUS Consulting Group
__________
For virtual activities, registration closes one hour before the program start time. Materials’ links are typically available two business days in advance of the program date (subject to availability and where applicable). Registrations received within two business days of the date of the program may result in not receiving materials’ links until the program date.
Program formats and dates are subject to change. Prices are subject to GST. This program is being recorded and will be available to registrants and on-demand subject to any issues with the recording. We reserve the right to change speakers, modify the program schedule, and/or revise content if necessary. In the unlikely event that the Law Society of Saskatchewan is forced to modify its program schedule, registrants will be notified.