Skip to Content

Changes for page Changelog

Last modified by Treyfane Dingo on 2025/04/14 17:12
From version 132.2
edited by Treyfane Dingo
on 2025/03/30 14:42
Change comment: There is no comment for this version
To version 88.1
edited by Treyfane Dingo
on 2024/06/17 17:14
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -3,126 +3,10 @@
3 3  All user relevant changes to L.A.S.S.I.E. will also be explained in our L.A.S.S.I.E. Developer News Channel [[https:~~/~~/t.me/+DouU4F1US69mYzhk>>https://t.me/+DouU4F1US69mYzhk]]
4 4  )))
5 5  
6 -=== 1.8.40 (30.03.2025) ===
7 -
8 -* Bugfix: Fixed Permissions for Location Database entries
9 -* Updated Schedule Duty List, secured and updated POSTVAR / SQL statements
10 -
11 -=== 1.8.39 (20.03.2025) ===
12 -
13 -* Bugfix: Alerting of Dispatch for Status 9 and 5 works correctly again
14 -
15 -=== 1.8.38 (02.03.2025) ===
16 -
17 -* Added a Radio Log function for DMR calls, which can be used with a FurCom Radio Logger
18 -* Bugfix: Fixing many bugs in CSS, surely building in more
19 -
20 -=== 1.8.37 (25.02.2025) ===
21 -
22 -* Added a whole new location mapping system to Incident Management which makes use of OpenStreetMap and can make use of a C3Nav compatible navigation system, e.g. EFnav.
23 -* Added a function to L.A.S.S.I.E. Bot to enable Operatives to send their current geo-location which then can be used by Dispatch to find them on OpenStreetMap.
24 -
25 -=== 1.8.36 (24.02.2025) ===
26 -
27 -* Bugfix: debugged about a thousand bugs from Operations Status.
28 -* Changed the whole pager system connector in Operations Status to better show the status of connections, auto-reconnect on connection failure, and have a pager status symbol just below the L.A.S.S.I.E. menu.
29 -* Changed the context menus in Operations Status to not show pager sending options when the pager system is down or unavailable.
30 -
31 -=== 1.8.35 (21.02.2025) ===
32 -
33 -* Bugfix: Made the clock not display 24:57:57 any more, but instead 00:57:57 when not in UTC ... I hate UTC.
34 -
35 -=== 1.8.34 (20.02.2025) ===
36 -
37 -* Changed the complete JavaScript in Operations Status so the page is about 500% faster.
38 -* Changed the stale counter for Incidents which now takes recent log entries into account, so a long-sunning incident with a recent log entry isn't shown as red blinking stale for half the day any more.
39 -
40 -=== 1.8.33 (11.02.2025) ===
41 -
42 -* Bugfix: Removed some bugs from Qualification Management and Event Management that occured while adding stuff in Operatives Management
43 -
44 -=== 1.8.32 (31.01.2025) ===
45 -
46 -* Added external alerts to Incident Archive list
47 -* Bugfix: Lost & Found and Item Database now also accepts photos via L.A.S.S.I.E. Bot if they are of rather low resolution.
48 -* Bugfix: Files are now also accepted if the extension of an allowed file type is in UPPER CASE.
49 -
50 -=== 1.8.31 (06.01.2025) ===
51 -
52 -* Changed Briefing module to not have access levels any more, since they necessarily have been "W" for everybody anyways
53 -* Bugfix: Operative Collar IDs of C-Units in Operations Status now are correctly shown if > 999
54 -* Bugfix: Incident Archive table now does not reset scrolling position every 15 seconds any more
55 -* Bugfix: Operatives Duty Stats table (and others) now also scrolls header horizontally, not just content
56 -* Changed location of several files and scripts (backend)
57 -
58 -=== 1.8.30 (27.12.2024) ===
59 -
60 -* Added direct Telegram link to most of the Telegram Handles in Operatives Management and Operatives Lists
61 -* Added an upload function for training certificates to Qualification & Training in Operatives Management; the qualification types First Aider, EMT / Paramedic, 34a, SiA, Firefighter and M.D. will require a certificate to be uploaded upon adding or changing them
62 -* (((
63 -Changed the add and change form for the qualification types First Aider, EMT / Paramedic and Firefighter in Qualification & Training in Operatives Management to account for standard training levels
64 -)))
65 -
66 -=== 1.8.29 (21.12.2024) ===
67 -
68 -* Added autocomplete for the Item Type in Lost & Found Database – it will display the types from all lost or found items, but not the returned ones
69 -* Updated search field in Lost & Found Database to also search inside the Log Comments
70 -* Updated table scrolling behaviour to be more mobile friendly and coherent
71 -
72 -=== 1.8.28 (17.12.2024) ===
73 -
74 -* Added an option to change all duties / events with the same title in the Schedule at the same time
75 -
76 -=== 1.8.27 (16.12.2024) ===
77 -
78 -* Added options to only show one particular status to Lost & Found Database which should make it more easy to display items reported as lost only
79 -* Added a delete option for Lost & Found images (click item to edit, then trash can next to image upload)
80 -* Added Log comment field to Add Lost & Found item
81 -
82 -=== 1.8.26 (16.11.2024) ===
83 -
84 -* Updated ConOps Incident Management, secured and updated POSTVAR / SQL statements, added error codes and error log
85 -* Added most of the recent features from Incident Management to ConOps Incident Management
86 -
87 -=== 1.8.25 (20.10.2024) ===
88 -
89 -* Added a module for changing Item Clearance Levels to System Settings
90 -* Changed the Log Reports printable from Incidents to a more readable format
91 -* Added an Incident Report to print out the whole Incident
92 -
93 -=== 1.8.24 (05.09.2024) ===
94 -
95 -* Added a System Setting to prevent Operatives un-registering from a duty in an otherwise writeable Self-Scheduler
96 -
97 -=== 1.8.23 (30.08.2024) ===
98 -
99 -* Added a FAQ system for L.A.S.S.I.E. Bot  to answer questions in a non-PM Telegram chat with the word "tell" as trigger if directly addressed (e.g.: "@LassieBot tell me about Tuesday"). Answer keywords and answers can be set in System Settings → Bot FAQ Answers. The Telegram chat IDs, which the bot shall answer questions for any convention in, have to be set as comma separated list in System Settings → Settings → Group IDs of L.A.S.S.I.E. Bot FAQ System.
100 -
101 -=== 1.8.22 (29.08.2024) ===
102 -
103 -* Updated Self-Scheduler to include duty stats for the respective Operative
104 -
105 -=== 1.8.21 (27.08.2024) ===
106 -
107 -* Updated Schedule to also send information about //what// has changed to scheduled Operatives on change of the content of a schedule item via L.A.S.S.I.E. Bot
108 -
109 -=== 1.8.20 (21.08.2024) ===
110 -
111 -* Added a direct link to the Schedule of respective Operatives (click on the collar ID) to the Scheduler event popup
112 -
113 -=== 1.8.19 (11.08.2024) ===
114 -
115 -* Updated Operatives Duty Stats to make the table more readable. Also added EVAC as shift type.
116 -
117 -=== 1.8.18 (10.08.2024) ===
118 -
119 -* Updated the Self-Scheduler so that the buttons are better readable; also got rid of the "Save" button
120 -
121 121  === 1.8.17 (17.06.2024) ===
122 122  
123 123  * Bugfix: All language characters can now be used for searches in Schedule and Self-Scheduler
124 -* Bugfix: Special unicode language characters like the ꝥ which is a þat (þ) wið a stroke, and dating back to Old Engliſh, can now also be used in Schedule titles. One can alſo uſe emojis 😸 now ... why are you torturing me so much?
125 -* Added a searchable field for Car License Plate to Attendee DB. This can be imported from a REG DB via API or CSV.
9 +* Bugfix: Special Language characters like the ꝥ which is a þat (þ) wið a stroke, representing þat and dating back to Old Engliſh can now also be used in Schedule titles. One can alſo uſe emojis now ... why are you torturing me so much?
126 126  
127 127  === 1.8.16 (14.05.2024) ===
128 128