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 firstname.lastname@example.org, and if in reference to a known issue please state the issue number and title.
Filemaker error do not display in error_msg
Incorrect mail header enoding for subjects containing UTF-8 text.
Tags need to be updated and rolled into Lasso.
Windows Installers for newer versions of Windows and IIS need to be updated and released.
Updates and release are needed for iText, ImageMagick, etc.
Inlines -host & double byte characters issues need to be resolved.
IIS will periodically return IIS Malformed Header error if the content length of a page is a certain size.
The email queue grows exceedingly large, without notification.
Generic (cause unknown) site crashing error message.
Lasso uses up all available memory on the server and never releases it.
Lasso crashes and fails to automatically restart on Cent OS 5.
This can prevent emails from being sent from Lasso, which might not immediately be noticed.
When Lasso consumes a lot of memory (like a runaway thread) it can't make more sessions.
SQL Queries do not release fast enough.
Error_currentError used in the conditional of a handle block injects output into the HTML response.
When using action_statement, Lasso will sometimes show the correct characters, and other times will show the wrong characters.
An error is given when Lasso is allowed to build the SQL statement.
The [Server_Port] is always reported as 80 on Linux, even when pages are served through HTTPS.
LJAX.lassoApp does not properly handle radio, checkbox, or button input types.
Lasso throws an error or sends an incomplete page when the file length is too long or contains an Appearance object.
If the Postgres maintenance table name is changed from the default 'postgres', Lasso returns an error.
When using loop_continue in a certain context, Lasso crashes.
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.
The SMTP queue fails with an error when a recipient mistakenly contains an extended character.
Contrary to event queue settings, scheduled events continue to run repeatedly until .lasso file is renamed or deleted.