Password Creation Tool

To manually change a role password by calculating a new password encryption code:
Enter a password in the 'Input' field, then click 'Calculate'. Copy the 'Result' and paste it between the 1st & 2nd '#' characters on the appropriate line in the Roles file. Click 'Publish'. That Role now has a new password.
Passwords themselves are not stored anywhere, not on user's device, not on the server. Only the 'Result' is stored, on the server. Users can change their own passwords once they have logged in with their old one. A forgotten password can only be reset here by a Board member. The encrypted 'Result' cannot be reverse-engineered to give a hacker the password itself.

Input:

Result:

Note: Using the Enter key and moving lines with Copy/Paste will create blank lines that you can't delete. No problem, the Publish action will remove them. 'Role' lines -- and no others -- must have exactly four # characters to be seen as 'roles'.

This must be a PLAINTEXT-ONLY file. No WYSIWYG formatting and no '<' or '>' characters to confuse the editor.
================================ Edit this file with EXTRA CARE ===============================

• This file (roles.html) holds roles, password encrypted values, role title and email for the pulldown list in 'Contact Us' on main page.
• Comment lines starting with "*" are skipped
• Role lines MUST have 4 "#" characters seperating role, crypt, title, email and end.
• Line format: role#crypt#title#email# all (including last line) MUST end with CRLF
• Optgroup lines and title are to build role-select element on login page.

Note: Using the Enter key and moving lines with Copy/Paste will create blank lines that you can't delete. No problem, the Publish action will remove them.

This must be a PLAINTEXT-ONLY file. No WYSIWYG formatting and no '<' or '>' characters to confuse the editor.
================================ Edit this file with EXTRA CARE ===============================

• This file (rolesaccess.html) controls which roles have edit rights to various pages. Each line
includes a page name, in lower case as shown, followed by a colon (:), followed by a
semicolon(;)-seperated list of role names (Proper Case) as shown.
• Comment lines starting with "*" are skipped
• Line format: page:Role1;Role2;Role3;etc. All (including last line) MUST end with CRLF

This must be a PLAINTEXT-ONLY file. No WYSIWYG formatting and no '<' or '>' characters to confuse the editor.
============================= Edit this file with EXTRA CARE ============================

These two files, tgt-sched...vars.php and tgt-sched...vars.js --- hold JavaScript and PHP values
that are inserted by code into tgt-sched....php (the working Schedule webpage) at each load.

• Javascript variables Title, Dates, and Description for each of FOUR UNITS, and Heading and Date
variables for each of EIGHT DATES per UNIT and TWO TIMES per DATE within each UNIT are entered here
as they become available on the MPC.org website. ie the system will work with only one UNIT filled in.
• The UNITS are numbered 1 thru 4; DATES within UNITS are numbered 1 thru 8; TIMES within DATES
are numbered 1 thru 2.
• Thus there are 4 UNITS -- each needing a Title, Dates, and Description --
and 4 x 8 x 2 = 64 CLASS LECTURES per semester -- each needing a Heading and Date.
• The 1st 5 values in each UNIT (total of 4x5=20 values) can be entered when the MPC catalog comes
online. This usually happens weeks before a semester.
• For each class date there is a date value in the form yymmdd, and two lecture title values.
These are usually provided at the beginning of each Unit via email by the Director.

• PHP variables $u1d1t1FName, etc define the date and time of each of a semester's class
lectures, in the form _yymmdd-t ... yy=year mm=month dd=day t=time(1 or 2)
ex: 210817-1 is Aug 17, 2021 1st (9:00) class.
• PHP variables start with _ or a letter .. not a number. you must include "_" before the
yymmdd-t in strings below.

This Wednesday Lecture content CAN include WYSIWYG formatting and images. It should describe a single date & time, not a series.
The first line date text must be left intact. The text "lecture title here" should be replaced with a brief title, to include the time if not 1:30 and presenter's name. Note that the first line appears bold and larger than succeeding lines.
The remaining content describes the lecture, plus bio information about the presenter. Text can be copied and pasted from text, Word, Google Docs, and PDF files, and even directly from other web pages.

This Special Event content CAN include WYSIWYG formatting and images. It should describe a single date & time, not a series.
The first line date text must be left intact; it can be extended to show an ending time. The text "event title here" should be replaced with a brief title.. Note that the first line appears bold and larger than succeeding lines.
The remaining content describes the event. Text can be copied and pasted from text, Word, Google Docs, and PDF files, and even directly from other web pages.

These are the Quotations that appear at the top of the website, cycling randomly every ten seconds. Bold, italic and other simple formatting will work, but nothing more complex.You must re-load the website before your editing changes will appear.

This is the Site Description that displays when a search-engine lists this website. Use NO FORMATTING, only plain text.You must re-load the website before your editing changes will appear.

Search Engine Optimization (SEO) -- These are the Keywords that tell Search Engines about this site. A comma-separated string of words and phrases. Use NO FORMATTING, only plain text.You must re-load the website before your editing changes will appear. Search engines will pick up your changes only after their spiders visit the site -- hours to weeks.

This is a simple What-You-See-Is-What-You-Get (WYSIWYG) editor. If you click 'Publish' the changes you made will show up immediately on the website. Be Careful.