Login
Email:
Password:

Bug Stats
Pending Review:1
Unconfirmed:0
Open:1
Resolved:1
Closed:641

Our main site is...
https://mid.as

Also find us on...

MIDAS | Bug Tracker

Bugs Tagged "error"

Bug ID: #1935

Reloading frame post import caused an Internal Server Error, instead of bouncing back to initial import screen

Status:Closed
(Updated 2017-06-30 @ 19:00)
Impact Matrix:
High
Likely
Low
*
LowImpactHigh
Category:Functionality (Server Side)
MIDAS Versions Affected:4.00 - 4.15
Browsers Affected:Microsoft Internet Explorer Microsoft Edge Mozilla Firefox Google Chrome Apple Safari Opera
Details:Reloading frame post import caused an Internal Server Error, instead of bouncing back to initial import screen
Resolution:Fixed for v4.16
Comments (0):
Please login or register to add comments

Bug ID: #1903

JS error when selecting date range in advanced print options window

Status:Closed
(Updated 2017-05-04 @ 17:58)
Impact Matrix:
High
Likely
Low
*
LowImpactHigh
Category:Functionality (Client Side)
MIDAS Versions Affected:4.00 - 4.15
Browsers Affected:Microsoft Internet Explorer Microsoft Edge Mozilla Firefox Google Chrome Apple Safari Opera
Details:A Javascript error is produced when initially selecting a date range in the Advanced Print options window
Resolution:Fixed for v4.15 if installed/updated after 4th May 2017
Comments (0):
Please login or register to add comments

Bug ID: #1900

Unable to import bookings with speech marks in notes/custom

Status:Closed
(Updated 2017-04-27 @ 19:32)
Impact Matrix:
High
Likely
Low
*
LowImpactHigh
Category:Functionality (Server Side)
MIDAS Versions Affected:4.00 - 4.15
Browsers Affected:Microsoft Internet Explorer Microsoft Edge Mozilla Firefox Google Chrome Apple Safari Opera
Details:In instances when a raw imported booking data record contained speech marks (") in the booking notes or in custom field columns, other than at the immediate start/end of the data entry, the data record would fail to import and would cause a silent MySQL error
Resolution:Fixed for v4.15 if installed/updated after 27th April 2017
Comments (0):
Please login or register to add comments

Bug ID: #1878

"Synchronous XMLHttpRequest on the main thread is deprecated" JS console warning when logging in

Status:Closed
(Updated 2017-03-17 @ 13:10)
Impact Matrix:
High
Likely
Low
*
LowImpactHigh
Category:Functionality (Client Side)
MIDAS Versions Affected:4.00 - 4.14
Browsers Affected:Microsoft Internet Explorer Microsoft Edge Mozilla Firefox Google Chrome Apple Safari Opera
Details:A silent "Synchronous XMLHttpRequest on the main thread is deprecated" Javascript warning is logged to the console in modern web browsers
Resolution:Fixed for v4.15
Comments (0):
Please login or register to add comments

Bug ID: #1859

Silent MySQL error when printing if user is limited to just "Clients" or "In User" view permissions

Status:Closed
(Updated 2016-11-21 @ 09:04)
Impact Matrix:
High
Likely
Low
*
LowImpactHigh
Category:Functionality (Server Side)
MIDAS Versions Affected:4.00 - 4.13
Browsers Affected:Microsoft Internet Explorer Microsoft Edge Mozilla Firefox Google Chrome Apple Safari Opera
Details:Silent MySQL error when printing if user is limited to just "Clients" or "In User" view permissions
Resolution:Fixed for v4.14
Comments (0):
Please login or register to add comments

Bug ID: #1681

"Times" shouldn't be an option for "Show on month cells"

Status:Closed
(Updated 2015-03-05 @ 12:22)
Impact Matrix:
High
Likely
Low
*
LowImpactHigh
Category:Appearance (GUI / Layout / Theme)
MIDAS Versions Affected:4.00 - 4.08
Browsers Affected:Microsoft Internet Explorer Microsoft Edge Mozilla Firefox Google Chrome Apple Safari Opera
Details:The "Times" field shouldn't be offered as an option for "Show on month cells" setting, as it results in a silent MySQL error when viewing the Monthly Overview
Workaround:Ensure that the "Show on month cells" (MIDAS Admin Options → Manage MIDAS → Appearance) setting isn't set to "Times"
Resolution:Fixed for v4.09
Comments (0):
Please login or register to add comments

Bug ID: #1667

Silent "Truncated incorrect DOUBLE value" MySQL error in some instances when saving venues

Status:Closed
(Updated 2015-01-17 @ 12:18)
Impact Matrix:
High
Likely
Low
*
LowImpactHigh
Category:Functionality (Server Side)
MIDAS Versions Affected:4.08
Browsers Affected:Microsoft Internet Explorer Microsoft Edge Mozilla Firefox Google Chrome Apple Safari Opera
Details:A harmless MySQL error may be produced when saving venues in early builds of MIDAS v4.08
Resolution:Fixed for v4.08 if installed/updated after 17th January 2015
Comments (0):
Please login or register to add comments

Bug ID: #1642

JS errors when modifying multiple bookings with attendees field disabled

Status:Closed
(Updated 2014-09-10 @ 14:52)
Impact Matrix:
High
Likely
Low
*
LowImpactHigh
Category:Functionality (Client Side)
MIDAS Versions Affected:4.06 - 4.07
Browsers Affected:Microsoft Internet Explorer Microsoft Edge Mozilla Firefox Google Chrome Apple Safari Opera
Details:Modifying multiple bookings may cause bookings to be removed/not be modified if the Attendees field has been disabled.
Symptoms:When modifying a number of similar bookings, the Modify Booking screen shows no calendar or selecting dates, and proceeding with the modification will remove all but one of the bookings you wish to modify
Workaround:Re-enable display of the Attendees field (via MIDAS Admin Options -> Manage MIDAS -> Fields)
Resolution:Fixed for v4.07 if installed/updated after 10th September 2014
Comments (0):
Please login or register to add comments

Bug ID: #1617

Additional databases created may not save correct venue rates

Status:Closed
(Updated 2014-05-29 @ 16:08)
Impact Matrix:
High
Likely
Low
*
LowImpactHigh
Category:Functionality (Server Side)
MIDAS Versions Affected:4.06
Browsers Affected:Microsoft Internet Explorer Microsoft Edge Mozilla Firefox Google Chrome Apple Safari Opera
Details:If your MIDAS is licensed for multiple databases, in any additional databases you create under v4.06, you may not be able to correctly save venue rate information for new venues
Workaround:In additionally created databases, set a single venue rate for all booking lengths.
Resolution:Fixed for v4.07
Comments (0):
Please login or register to add comments

Bug ID: #1616

Unable to save user's View Access settings when a large number of groups are selected

Status:Closed
(Updated 2014-05-29 @ 16:00)
Impact Matrix:
High
Likely
Low
*
LowImpactHigh
Category:Functionality (Server Side)
MIDAS Versions Affected:4.00 - 4.06
Browsers Affected:Microsoft Internet Explorer Microsoft Edge Mozilla Firefox Google Chrome Apple Safari Opera
Details:If you've setup a large number of Venue Groups and you try to assign a user's "View Access" permission to more than around 15 of these groups, the settings may not save correctly.
Workaround:Reduce the number of selected groups in the user's "View Access" setting (to no more than 15)
Resolution:Fixed for v4.07.
If you can't wait that long, please execute the following MySQL command on your MIDAS database to resolve:
ALTER TABLE `users` CHANGE `filter` `filter` VARCHAR(300)
Comments (0):
Please login or register to add comments

Bug ID: #1615

SQL error when adding new venue group

Status:Closed
(Updated 2014-05-28 @ 21:24)
Impact Matrix:
High
Likely
Low
*
LowImpactHigh
Category:Functionality (Server Side)
MIDAS Versions Affected:4.06
Browsers Affected:Microsoft Internet Explorer Microsoft Edge Mozilla Firefox Google Chrome Apple Safari Opera
Details:A silent MySQL error is produced when a new venue group is added. This doesn't prevent the group from being created and added, but may prevent the Manage Venues screen from being automatically updated with details of the newly added venue group.
Resolution:Fixed for v4.06 if installed/updated after 28th May 2014
Comments (0):
Please login or register to add comments

Bug ID: #1592

Javascript error in booking grid when user's hours are restricted

Status:Closed
(Updated 2014-04-29 @ 23:32)
Impact Matrix:
High
Likely
Low
*
LowImpactHigh
Category:Functionality (Client Side)
MIDAS Versions Affected:4.05
Browsers Affected:Microsoft Internet Explorer Microsoft Edge Mozilla Firefox Google Chrome Apple Safari Opera
Details:When a user's hours are restricted, a harmless Javascript error is produced each time a new date is navigated to in the booking grid.
Workaround:Set user permission's to "Day starts at 00:00 and runs for 24 hours"
Resolution:Fixed for v4.06
Comments (0):
Please login or register to add comments

← Back
Jump To Bug
#