Changes for page Changelog

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -3,113 +3,11 @@
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.53 (28.08.2025) ===
7		-
8		-* Changed Column names in PNG Database to better reflect the placeholders for letters
9		-
10		-=== 1.8.52 (19.08.2025) ===
11		-
12		-* Changed Self-Scheduler to not show §C: shifts to Operatives, even if they are scheduled in them – this prevents “double-shifts” like §R: ODS Team 1 and §C: ODS at the same time shown
13		-* Changed Schedule to enable keyword filtering if a specific Operative is selected
14		-* Bugfix: counter in Schedule counted events over daybreak twice – no not more
15		-* Added Operative duty hours count to counter in Schedule if Operative is selected
16		-
17		-=== 1.8.51 (16.08.2025) ===
18		-
19		-* Added counter in Schedule to calculate the hours shown in the current search / display.
20		-* Added Chinese language options and changed the “unknown” flag from EU to translingual to Operatives Management
21		-
22		-=== 1.8.50 (14.08.2025) ===
23		-
24		-* Added handling of internal location URLs to L.A.S.S.I.E. Bot and Operations Status
25		-* Added Open Location to context menu for Security Operatives
26		-
27		-=== 1.8.49 (11.08.2025) ===
28		-
29		-* Changed the Self-Scheduler to not show the red warning stripes for understaffed shifts if “show unassigned” is selected
30		-
31		-=== 1.8.48 (12.07.2025) ===
32		-
33		-* Changed errors / warnings / messages in Operations Status about adding / removing / informing units to and from Incidents to give a clearer picture if more than one Dispatch are at work
34		-* Changed FTC client to not display warning message about pager system as it'll nearly never be there anyway
35		-
36		-=== 1.8.47 (05.07.2025) ===
37		-
38		-* Bugfix: added timezone consideration to the Briefings, Items DB and Assets DB modules and the Bigscreen
39		-* Bugfix: Changed maximum field length for floor in Incident Management to 6 and changed form field to reflect maximum length
40		-
41		-=== 1.8.46 (18.06.2025) ===
42		-
43		-* Changed Show Incident to include a better functionality to search for attendees in Involved and Witnesses
44		-
45		-=== 1.8.45 (14.06.2025) ===
46		-
47		-* Bugfix: the .ics will now also work in Thunderbird (which is way more strict than everything else if it comes to slight formatting errors in an .ics …)
48		-
49		-=== 1.8.44 (06.06.2025) ===
50		-
51		-* Bugfix: Various smaller spelling corrections
52		-* Changed standard Attendee CSV importer to make it more robust
53		-* Added standard Event (Schedule) CSV importer
54		-* Changed Autofill ODS-C script to accommodate for multiple parallel ODS
55		-
56		-=== 1.8.43 (14.04.2025) ===
57		-
58		-* Bugfix: Correctly displaying error messages for missing Lat/Long in Location Management
59		-* Bugfix: Correctly displaying missing Nationality in Operatives Lists
60		-
61		-=== 1.8.42 (09.04.2025) ===
62		-
63		-* Bugfix: Setting an Operative to INACTIVE now also sets the Access Level “No Access”
64		-
65		-=== 1.8.41 (02.04.2025) ===
66		-
67		-* Added standard CSV importer to Attendee Database for all clients without individual JSON API importer
68		-
69		-=== 1.8.40 (30.03.2025) ===
70		-
71		-* Bugfix: Fixed Permissions for Location Database entries
72		-* Updated Schedule and Self-Scheduler, secured and updated POSTVAR / SQL statements
73		-* Changed Operations Status and enabled COMBIUNITS with no scheduled Operatives
74		-
75		-=== 1.8.39 (20.03.2025) ===
76		-
77		-* Bugfix: Alerting of Dispatch for Status 9 and 5 works correctly again
78		-
79		-=== 1.8.38 (02.03.2025) ===
80		-
81		-* Added a Radio Log function for DMR calls, which can be used with a FurCom Radio Logger
82		-* Bugfix: Fixing many bugs in CSS, surely building in more
83		-
84		-=== 1.8.37 (25.02.2025) ===
85		-
86		-* 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
87		-* 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
88		-
89		-=== 1.8.36 (24.02.2025) ===
90		-
91		-* Bugfix: debugged about a thousand bugs from Operations Status
92		-* 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
93		-* Changed the context menus in Operations Status to not show pager sending options when the pager system is down or unavailable
94		-
95		-=== 1.8.35 (21.02.2025) ===
96		-
97		-* Bugfix: Made the clock not display 24:57:57 any more, but instead 00:57:57 when not in UTC ... I hate UTC
98		-
99		-=== 1.8.34 (20.02.2025) ===
100		-
101		-* Changed the complete JavaScript in Operations Status so the page is about 500% faster
102		-* 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
103		-
104		-=== 1.8.33 (11.02.2025) ===
105		-
106		-* Bugfix: Removed some bugs from Qualification Management and Event Management that occured while adding stuff in Operatives Management
107		-
108	108	=== 1.8.32 (31.01.2025) ===
109	109
110	110	* Added external alerts to Incident Archive list
111	111	* 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.
112		-* Bugfix: Files are now also accepted if the extension of an allowed file type is in UPPER CASE.
	10	+* Bugfix: Files are now also accepted if the allowed file type (and thus extension) is in UPPER CASE.
113	113
114	114	=== 1.8.31 (06.01.2025) ===
115	115