Lasso 8.6 Issues List
The list of known open and resolved issues in 8.6 are shown below. This list will be changing dynamically as new ones are opened and old ones are quashed. Looking for 9.x issues? - see here.
Use the Comment button to see details and contribute your knowledge or experience about a given issue. Voting on issue prioritization is available to Certified Lasso Developers (CLD's), and members of the Lasso Professional Association and the Lasso Development Partners.
If you know of issues not outlined below or if you have any detail you'd like to add please contact bugs@lassosoft.com, and if in reference to a known issue please state the issue number and title.
Showing 1 - 25 of 37
- 1
- 2
Filemaker Error
Filemaker error do not display in error_msg
Mail subject encoding, UTF-8
Incorrect mail header enoding for subjects containing UTF-8 text.
[Cache] Tags
Tags need to be updated and rolled into Lasso.
Windows Installers
Windows Installers for newer versions of Windows and IIS need to be updated and released.
Update iText and ImageMagick
Updates and release are needed for iText, ImageMagick, etc.
Inlines -host & Characters
Inlines -host & double byte characters issues need to be resolved.
IIS Malformed Header
IIS will periodically return IIS Malformed Header error if the content length of a page is a certain size.
Email Queue Growth
The email queue grows exceedingly large, without notification.
Unidentified Broken Pipe
Generic (cause unknown) site crashing error message.
Lasso Memory Hog
Lasso uses up all available memory on the server and never releases it.
Lasso Restart Fail
Lasso crashes and fails to automatically restart on Cent OS 5.
DNS Deafness
This can prevent emails from being sent from Lasso, which might not immediately be noticed.
Session Memory
When Lasso consumes a lot of memory (like a runaway thread) it can't make more sessions.
Queries Release Speed
SQL Queries do not release fast enough.
Error_CurrentError Output
Error_currentError used in the conditional of a handle block injects output into the HTML response.
Action_statement Extended Characters
When using action_statement, Lasso will sometimes show the correct characters, and other times will show the wrong characters.
MS Access ODBC NULL Search
An error is given when Lasso is allowed to build the SQL statement.
Server_Port Registration Failure
The [Server_Port] is always reported as 80 on Linux, even when pages are served through HTTPS.
LJAX Buttons & Checkboxes
LJAX.lassoApp does not properly handle radio, checkbox, or button input types.
Libxml Error
Lasso throws an error or sends an incomplete page when the file length is too long or contains an Appearance object.
Postgres Maintenance Table Name
If the Postgres maintenance table name is changed from the default 'postgres', Lasso returns an error.
Loop_continue Crash
When using loop_continue in a certain context, Lasso crashes.
Memory Issue
Memory bug in versions 8.5.6b1 and 8.5.6 final, where the lasso8 service process is taking 1.15 GB of RAM, as found in the console log.
SMTP Error With Extended Characters
The SMTP queue fails with an error when a recipient mistakenly contains an extended character.
Lasso Events
Contrary to event queue settings, scheduled events continue to run repeatedly until .lasso file is renamed or deleted.
Showing 1 - 25 of 37
- 1
- 2
