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
Do you have any video of that? I’d like to find
out more details.
Hello,
Thanks for reaching out. We will follow up by email shortly.
Regards,
Alan
Alan Kilpatrick, CD, BA, MLIS | (he/him)
Co-Director & Librarian, Legal Resources
Law Society of Saskatchewan | 2425 Victoria Ave, Regina, SK S4P 4W6
Email: alan.kilpatrick@lawsociety.sk.ca | Phone: (306) 569-8020 | Fax: (306) 569-0155 | Website: http://www.lawsociety.sk.ca
Need a quick answer? Try the virtual chat on our website. Monday – Friday: 9AM – 4PM
The Law Society regulates lawyers and the practice of law in the public interest in Saskatchewan, which includes the shared lands of Treaties 2, 4, 5, 6, 8, 10, and the Homeland of the Métis/Michif Nation.
Confidentiality Notice: This email and any attachments are confidential and intended solely for the use of the individual to whom they are addressed. If you are not the named addressee or intended recipient, you should not disseminate, distribute, copy, retain, use or modify this email and taking any action in reliance on the content of this email is strictly prohibited. If you have received this email in error, please notify the sender immediately and delete this email from your system.