LassoApp problems on 8.5.6 / 8.6

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

LassoApp problems on 8.5.6 / 8.6

Eric Knibbe
Here's one for all the Lasso greybeards out there…

Our CMS works on any version of Lasso 8 up to 8.5.5, but as of 8.5.6, something changed in how LassoApps are processed, and it simply doesn't work. Here's what I know:

- Running the system as "open", with all the modules as plain-text .lasso files, runs fine (albeit without any of the LassoApp_Link references working).

- Running as compiled LassoApps, even if they've been compiled with 8.5.6, results in "-9995 Not enough memory for request" errors.

- If I try to narrow down the source of the problem by trimming down the source of a module and/or adding an [abort] call to stop execution, things start getting VERY strange. For example, running this code as a LassoApp:

[output_none]

[var:
        'AUTHENTICATED' = 'NO',
        'Users'=(Map),
        'DipArray' = (array)]


[/output_none]

results in 'No tag, type or constant was defined under the name "ç".'

Remove a line break, change the line endings, etc. and something totally different is thrown, e.g.: "Unterminated { block "OÉ0«flM¸_LÜ&{ì’&ì›H¿WR°A¥M{êÕOoÀ∂l^¢¡ór.ˇfl9•=ıÔ6M̺1•+¡'ÓÕË⁄uÓà_S≠ï“·�... at: /MODULES/LEAP_Core_Authentication.LassoApp on line 1 at position 0."

Anyone out there seen this before? (I'm on a Mac, b.t.w.)
‐‐‐‐‐‐‐‐‐‐✂‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐
Eric3
 


#############################################################
This message is sent to you because you are subscribed to
  the mailing list <[hidden email]>.
To unsubscribe, E-mail to: <[hidden email]>
To switch to the DIGEST mode, E-mail to <[hidden email]>
To switch to the INDEX mode, E-mail to <[hidden email]>
Send administrative queries to  <[hidden email]>

Reply | Threaded
Open this post in threaded view
|

Re: LassoApp problems on 8.5.6 / 8.6

Adam de Zoete-2
Have you removed all the BOMs from your code beforehand? I run the
source through this before compiling LassoApps:

// IMPORTANT FOR LINUX: Removeall BOMs
#file_data -> removeleading(bom_utf8);
#file_data -> removeleading(BOM_UTF16BE);
#file_data -> removeleading(BOM_UTF16LE);
#file_data -> removeleading(BOM_UTF32BE);
#file_data -> removeleading(BOM_UTF32LE);

Adam


On 15/06/2011 16:15, Eric Knibbe wrote:

> Here's one for all the Lasso greybeards out there…
>
> Our CMS works on any version of Lasso 8 up to 8.5.5, but as of 8.5.6, something changed in how LassoApps are processed, and it simply doesn't work. Here's what I know:
>
> - Running the system as "open", with all the modules as plain-text .lasso files, runs fine (albeit without any of the LassoApp_Link references working).
>
> - Running as compiled LassoApps, even if they've been compiled with 8.5.6, results in "-9995 Not enough memory for request" errors.
>
> - If I try to narrow down the source of the problem by trimming down the source of a module and/or adding an [abort] call to stop execution, things start getting VERY strange. For example, running this code as a LassoApp:
>
> [output_none]
>
> [var:
> 'AUTHENTICATED' = 'NO',
> 'Users'=(Map),
> 'DipArray' = (array)]
>
>
> [/output_none]
>
> results in 'No tag, type or constant was defined under the name "ç".'
>
> Remove a line break, change the line endings, etc. and something totally different is thrown, e.g.: "Unterminated { block "OÉ0«flM¸_LÜ&{ì’&ì›H¿WR°A¥M{êÕOoÀ∂l^¢¡ór.ˇfl9•=ıÔ6M̺1•+¡'ÓÕË⁄uÓà_S≠ï“·�... at: /MODULES/LEAP_Core_Authentication.LassoApp on line 1 at position 0."
>
> Anyone out there seen this before? (I'm on a Mac, b.t.w.)
> ‐‐‐‐‐‐‐‐‐‐✂‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐
> Eric3
>
>
>
> #############################################################
> This message is sent to you because you are subscribed to
>    the mailing list<[hidden email]>.
> To unsubscribe, E-mail to:<[hidden email]>
> To switch to the DIGEST mode, E-mail to<[hidden email]>
> To switch to the INDEX mode, E-mail to<[hidden email]>
> Send administrative queries to<[hidden email]>
>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list <[hidden email]>.
To unsubscribe, E-mail to: <[hidden email]>
To switch to the DIGEST mode, E-mail to <[hidden email]>
To switch to the INDEX mode, E-mail to <[hidden email]>
Send administrative queries to  <[hidden email]>

Reply | Threaded
Open this post in threaded view
|

Re: LassoApp problems on 8.5.6 / 8.6

Adam de Zoete-2
Sorry my code example was only a portion of the process.

local('file_data' = include_raw($path_to_source_file));

#file_data -> removeleading(bom_utf8);
#file_data -> removeleading(BOM_UTF16BE);
#file_data -> removeleading(BOM_UTF16LE);
#file_data -> removeleading(BOM_UTF32BE);
#file_data -> removeleading(BOM_UTF32LE);

file_write($path_to_source_file, #file_data, -fileoverwrite);

LassoApp_Create(
        -Root=$directory_of_source_file,
        -Entry=$source_file_name,
        -Result=$lasso_app_file_name);

As a preventative measure that removes the BOMs from the file before
running LassoApp_Create.

Adam



On 15/06/2011 16:22, Adam de Zoete wrote:

> Have you removed all the BOMs from your code beforehand? I run the
> source through this before compiling LassoApps:
>
> // IMPORTANT FOR LINUX: Removeall BOMs
> #file_data -> removeleading(bom_utf8);
> #file_data -> removeleading(BOM_UTF16BE);
> #file_data -> removeleading(BOM_UTF16LE);
> #file_data -> removeleading(BOM_UTF32BE);
> #file_data -> removeleading(BOM_UTF32LE);
>
> Adam


#############################################################
This message is sent to you because you are subscribed to
  the mailing list <[hidden email]>.
To unsubscribe, E-mail to: <[hidden email]>
To switch to the DIGEST mode, E-mail to <[hidden email]>
To switch to the INDEX mode, E-mail to <[hidden email]>
Send administrative queries to  <[hidden email]>

Reply | Threaded
Open this post in threaded view
|

Re: LassoApp problems on 8.5.6 / 8.6

Mark Palmer
In reply to this post by Adam de Zoete-2
You can also use a BBEdit text factory to batch change text encoding on multiple file.

On 15 Jun 2011, at 16:22, Adam de Zoete wrote:

> Have you removed all the BOMs from your code beforehand? I run the source through this before compiling LassoApps:
>
> // IMPORTANT FOR LINUX: Removeall BOMs
> #file_data -> removeleading(bom_utf8);
> #file_data -> removeleading(BOM_UTF16BE);
> #file_data -> removeleading(BOM_UTF16LE);
> #file_data -> removeleading(BOM_UTF32BE);
> #file_data -> removeleading(BOM_UTF32LE);
>
> Adam



Regards

Mark Palmer
E: [hidden email]
T: 01902 620500
W: www.pageworks.co.uk




#############################################################
This message is sent to you because you are subscribed to
  the mailing list <[hidden email]>.
To unsubscribe, E-mail to: <[hidden email]>
To switch to the DIGEST mode, E-mail to <[hidden email]>
To switch to the INDEX mode, E-mail to <[hidden email]>
Send administrative queries to  <[hidden email]>

Reply | Threaded
Open this post in threaded view
|

Re: LassoApp problems on 8.5.6 / 8.6

Eric Knibbe
In reply to this post by Adam de Zoete-2
It's not a BOM issue - I have the file open in TextWrangler, and it acts strangely whether the BOM is there or not.
‐‐‐‐‐‐‐‐‐‐✂‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐
Eric3
 

On 2011-06-15, at 11:38 AM, Adam de Zoete wrote:

> Sorry my code example was only a portion of the process.
>
> local('file_data' = include_raw($path_to_source_file));
>
> #file_data -> removeleading(bom_utf8);
> #file_data -> removeleading(BOM_UTF16BE);
> #file_data -> removeleading(BOM_UTF16LE);
> #file_data -> removeleading(BOM_UTF32BE);
> #file_data -> removeleading(BOM_UTF32LE);
>
> file_write($path_to_source_file, #file_data, -fileoverwrite);
>
> LassoApp_Create(
> -Root=$directory_of_source_file,
> -Entry=$source_file_name,
> -Result=$lasso_app_file_name);
>
> As a preventative measure that removes the BOMs from the file before running LassoApp_Create.
>
> Adam
>
>
>
> On 15/06/2011 16:22, Adam de Zoete wrote:
>> Have you removed all the BOMs from your code beforehand? I run the
>> source through this before compiling LassoApps:
>>
>> // IMPORTANT FOR LINUX: Removeall BOMs
>> #file_data -> removeleading(bom_utf8);
>> #file_data -> removeleading(BOM_UTF16BE);
>> #file_data -> removeleading(BOM_UTF16LE);
>> #file_data -> removeleading(BOM_UTF32BE);
>> #file_data -> removeleading(BOM_UTF32LE);
>>
>> Adam
>


#############################################################
This message is sent to you because you are subscribed to
  the mailing list <[hidden email]>.
To unsubscribe, E-mail to: <[hidden email]>
To switch to the DIGEST mode, E-mail to <[hidden email]>
To switch to the INDEX mode, E-mail to <[hidden email]>
Send administrative queries to  <[hidden email]>

Reply | Threaded
Open this post in threaded view
|

Re: LassoApp problems on 8.5.6 / 8.6

Mark Palmer
Have you got any invisible gremlin characters in the files anywhere?

On 15 Jun 2011, at 17:22, Eric Knibbe wrote:

> It's not a BOM issue - I have the file open in TextWrangler, and it acts strangely whether the BOM is there or not.



Regards

Mark Palmer
E: [hidden email]
T: 01902 620500
W: www.pageworks.co.uk




#############################################################
This message is sent to you because you are subscribed to
  the mailing list <[hidden email]>.
To unsubscribe, E-mail to: <[hidden email]>
To switch to the DIGEST mode, E-mail to <[hidden email]>
To switch to the INDEX mode, E-mail to <[hidden email]>
Send administrative queries to  <[hidden email]>

Reply | Threaded
Open this post in threaded view
|

Re: LassoApp problems on 8.5.6 / 8.6

Brian Loomis-4
I identified an issue with Kyle and Jono last week where lasso will
display a BOM if there is an include file with no content or using
process() on a null value.

Check all your includes and if you have any blank files that are being
included, put a [] in them or a <?LassoScript ?> in the blank files.

On Wed, Jun 15, 2011 at 10:45 AM, Mark Palmer <[hidden email]> wrote:

> Have you got any invisible gremlin characters in the files anywhere?
>
> On 15 Jun 2011, at 17:22, Eric Knibbe wrote:
>
>> It's not a BOM issue - I have the file open in TextWrangler, and it acts strangely whether the BOM is there or not.
>
>
>
> Regards
>
> Mark Palmer
> E: [hidden email]
> T: 01902 620500
> W: www.pageworks.co.uk
>
>
>
>
> #############################################################
> This message is sent to you because you are subscribed to
>  the mailing list <[hidden email]>.
> To unsubscribe, E-mail to: <[hidden email]>
> To switch to the DIGEST mode, E-mail to <[hidden email]>
> To switch to the INDEX mode, E-mail to <[hidden email]>
> Send administrative queries to  <[hidden email]>
>
>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list <[hidden email]>.
To unsubscribe, E-mail to: <[hidden email]>
To switch to the DIGEST mode, E-mail to <[hidden email]>
To switch to the INDEX mode, E-mail to <[hidden email]>
Send administrative queries to  <[hidden email]>

Reply | Threaded
Open this post in threaded view
|

Re: LassoApp problems on 8.5.6 / 8.6

Bil Corry-3
In reply to this post by Eric Knibbe
Looks to me like Lasso is processing it as a .lasso file instead of a .lassoapp file.  Try renaming it to .lasso and calling it - if same results then that's the issue.

- Bil

On Jun 15, 2011, at 8:15 AM, Eric Knibbe <[hidden email]> wrote:

> Here's one for all the Lasso greybeards out there…
>
> Our CMS works on any version of Lasso 8 up to 8.5.5, but as of 8.5.6, something changed in how LassoApps are processed, and it simply doesn't work. Here's what I know:
>
> - Running the system as "open", with all the modules as plain-text .lasso files, runs fine (albeit without any of the LassoApp_Link references working).
>
> - Running as compiled LassoApps, even if they've been compiled with 8.5.6, results in "-9995 Not enough memory for request" errors.
>
> - If I try to narrow down the source of the problem by trimming down the source of a module and/or adding an [abort] call to stop execution, things start getting VERY strange. For example, running this code as a LassoApp:
>
> [output_none]
>
> [var:
>    'AUTHENTICATED' = 'NO',
>    'Users'=(Map),
>    'DipArray' = (array)]
>
>
> [/output_none]
>
> results in 'No tag, type or constant was defined under the name "ç".'
>
> Remove a line break, change the line endings, etc. and something totally different is thrown, e.g.: "Unterminated { block "OÉ0«flM¸_LÜ&{ì’&ì›H¿WR°A¥M{êÕOoÀ∂l^¢¡ór.ˇfl9•=ıÔ6M̺1•+¡'ÓÕË⁄uÓà_S≠ï“·�... at: /MODULES/LEAP_Core_Authentication.LassoApp on line 1 at position 0."
>
> Anyone out there seen this before? (I'm on a Mac, b.t.w.)
> ‐‐‐‐‐‐‐‐‐‐✂‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐
> Eric3
>
>
>
> #############################################################
> This message is sent to you because you are subscribed to
>  the mailing list <[hidden email]>.
> To unsubscribe, E-mail to: <[hidden email]>
> To switch to the DIGEST mode, E-mail to <[hidden email]>
> To switch to the INDEX mode, E-mail to <[hidden email]>
> Send administrative queries to  <[hidden email]>
>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list <[hidden email]>.
To unsubscribe, E-mail to: <[hidden email]>
To switch to the DIGEST mode, E-mail to <[hidden email]>
To switch to the INDEX mode, E-mail to <[hidden email]>
Send administrative queries to  <[hidden email]>