Lasso 8.5 issue with field names which contains period

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

Lasso 8.5 issue with field names which contains period

neocodemohammad
Hi,

We just upgrade a client to FM9 and Lasso 8.5. Some of their field names contain period, for example 'JobNo.' or 'ChargeNo.' Now none of the queries that are searching on any of those feild are returning any data. I dont even get an error message. Just a blank page. Here is a sample:

<?LassoScript
        Inline: -Search, -MaxRecords='all', -Database='db', -Layout='lo', 'JobNo.'='452';
                If: (Found_Count) == '0';
                        Output: 'No Records Found';
                Else;
                        Records;
                                Output: (Field: 'JobNo.');
                        /Records;
                /If;
        /Inline;
?>

It works fine in their old environment or if I search in another field. I also tried it in another database and the same result. I can't get any result if I search in a field with period in the name! I tried to escape it with \\. but no luck!

PLEASE HELP! It's a really big issue for us...

Thanks,
Mohammad
Reply | Threaded
Open this post in threaded view
|

Re: Lasso 8.5 issue with field names which contains period

Marc Pope
Field names with a period, is that even legal? why?

-marc

On Mar 5, 2009, at 9:08 PM, neocodemohammad wrote:

>
> Hi,
>
> We just upgrade a client to FM9 and Lasso 8.5. Some of their field  
> names
> contain period, for example 'JobNo.' or 'ChargeNo.' Now none of the  
> queries
> that are searching on any of those feild are returning any data. I  
> dont even
> get an error message. Just a blank page. Here is a sample:
>
> <?LassoScript
> Inline: -Search, -MaxRecords='all', -Database='db', -Layout='lo',
> 'JobNo.'='452';
> If: (Found_Count) == '0';
> Output: 'No Records Found';
> Else;
> Records;
> Output: (Field: 'JobNo.');
> /Records;
> /If;
> /Inline;
> ?>
>
> It works fine in their old environment or if I search in another  
> field. I
> also tried it in another database and the same result. I can't get any
> result if I search in a field with period in the name! I tried to  
> escape it
> with \\. but no luck!
>
> PLEASE HELP! It's a really big issue for us...
>
> Thanks,
> Mohammad
> --
> View this message in context: http://www.nabble.com/Lasso-8.5-issue-with-field-names-which-contains-period-tp22364902p22364902.html
> Sent from the Lasso - Talk mailing list archive at Nabble.com.
>
>
>
> --
> This list is a free service of LassoSoft: http://www.LassoSoft.com/
> Search the list archives: http://www.ListSearch.com/Lasso/Browse/
> Manage your subscription: http://www.ListSearch.com/Lasso/
>
>



--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/


Reply | Threaded
Open this post in threaded view
|

Re: Lasso 8.5 issue with field names which contains period

stevepiercy
In reply to this post by neocodemohammad
Is the output "No Records Found" or nothing?

I never name my fields with periods, so I don't know whether that is an actual problem.  I know if you name fields with spaces in FM that the search still works, so why not a period or other questionable character, too?

--steve


On Thursday, March 5, 2009, [hidden email] (neocodemohammad) pronounced:

>
>Hi,
>
>We just upgrade a client to FM9 and Lasso 8.5. Some of their field names
>contain period, for example 'JobNo.' or 'ChargeNo.' Now none of the queries
>that are searching on any of those feild are returning any data. I dont even
>get an error message. Just a blank page. Here is a sample:
>
><?LassoScript
>   Inline: -Search, -MaxRecords='all', -Database='db', -Layout='lo',
>'JobNo.'='452';
>       If: (Found_Count) == '0';
>           Output: 'No Records Found';
>       Else;
>           Records;
>               Output: (Field: 'JobNo.');
>           /Records;
>       /If;
>   /Inline;
>?>
>
>It works fine in their old environment or if I search in another field. I
>also tried it in another database and the same result. I can't get any
>result if I search in a field with period in the name! I tried to escape it
>with \\. but no luck!
>
>PLEASE HELP! It's a really big issue for us...
>
>Thanks,
>Mohammad

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Steve Piercy               Web Site Builder               Soquel, CA
<[hidden email]>                  <http://www.StevePiercy.com/>


--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/


Reply | Threaded
Open this post in threaded view
|

Re: Lasso 8.5 issue with field names which contains period

stevepiercy
I just performed a test on a field name with a period in FM, and it displayed.  Therefore you should test whether you have set up the database permissions correctly.

Put error_currenterror in your inline to return a specific error message.

    Inline: -Search, -MaxRecords='all', -Database='db', -Layout='lo',
    'JobNo.'='452';
        error_currenterror;
    /Inline;

I notice that you did not include a username or password in the inline.  So I am inclined to think you did not set up Lasso Security properly.  For a complete step-by-step procedure, refer to the Filemaker Quick Start Guide in your documentation folder or available from the following link.

http://lassosoft.com/Solutions/FileMaker/FMS9_Quick_Start.pdf

Also you don't mention what you upgraded *from*.  It might not matter, but it could help us understand where you started.

--steve


On Thursday, March 5, 2009, [hidden email] (Steve Piercy - Web Site Builder) pronounced:

>Is the output "No Records Found" or nothing?
>
>I never name my fields with periods, so I don't know whether that is an actual
>problem.  I know if you name fields with spaces in FM that the search still works,
>so why not a period or other questionable character, too?
>
>--steve
>
>
>On Thursday, March 5, 2009, [hidden email] (neocodemohammad)
>pronounced:
>
>>
>>Hi,
>>
>>We just upgrade a client to FM9 and Lasso 8.5. Some of their field names
>>contain period, for example 'JobNo.' or 'ChargeNo.' Now none of the queries
>>that are searching on any of those feild are returning any data. I dont even
>>get an error message. Just a blank page. Here is a sample:
>>
>><?LassoScript
>>   Inline: -Search, -MaxRecords='all', -Database='db', -Layout='lo',
>>'JobNo.'='452';
>>       If: (Found_Count) == '0';
>>           Output: 'No Records Found';
>>       Else;
>>           Records;
>>               Output: (Field: 'JobNo.');
>>           /Records;
>>       /If;
>>   /Inline;
>>?>
>>
>>It works fine in their old environment or if I search in another field. I
>>also tried it in another database and the same result. I can't get any
>>result if I search in a field with period in the name! I tried to escape it
>>with \\. but no luck!
>>
>>PLEASE HELP! It's a really big issue for us...
>>
>>Thanks,
>>Mohammad
>
>-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>Steve Piercy               Web Site Builder               Soquel, CA
><[hidden email]>                  <http://www.StevePiercy.com/>
>
>
>--
>This list is a free service of LassoSoft: http://www.LassoSoft.com/
>Search the list archives: http://www.ListSearch.com/Lasso/Browse/
>Manage your subscription: http://www.ListSearch.com/Lasso/
>
>

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Steve Piercy               Web Site Builder               Soquel, CA
<[hidden email]>                  <http://www.StevePiercy.com/>


--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/


Reply | Threaded
Open this post in threaded view
|

Re: Lasso 8.5 issue with field names which contains period

Johan Solve
In reply to this post by neocodemohammad
This is most likely not a Lasso issue but a FileMaker issue.

Periods in field names is covered on page 95 in the "FileMaker Server
9 Custom Web Publishing with XML and XSLT" manual
http://www.filemaker.com/downloads/pdf/fms9_cwp_xslt_en.pdf

Field names can contain periods, with the following exceptions:
- The period cannot be followed by a number. For example, myfield.9 is
an invalid field name.
- The period cannot be followed by the text string op (the two letters
“op”). For example, myfield.op is
an invalid field name.
- The period cannot be followed by the text string global (the word
“global”). For example, myfield.global is an invalid field name.

Also see page 89 "About the syntax for a fully qualified field name".

Anyway, your field names look like they should be ok. But we've also
had problems with periods in field names even if they meet the
requirements listed above. So far we've resorted to renaming the
fields or creating shadow calculation fields with a better name.

Maybe Lasso is involved in the problem after all? I haven't examined
the FMI query to see how it comes out, but if you want to look deeper
into this you can look at [action_statement] inside of the inline, you
can also try the output of [action_statement] directly against the FM
server.

On Fri, Mar 6, 2009 at 3:08 AM, neocodemohammad
<[hidden email]> wrote:

>
> Hi,
>
> We just upgrade a client to FM9 and Lasso 8.5. Some of their field names
> contain period, for example 'JobNo.' or 'ChargeNo.' Now none of the queries
> that are searching on any of those feild are returning any data. I dont even
> get an error message. Just a blank page. Here is a sample:
>
> <?LassoScript
>        Inline: -Search, -MaxRecords='all', -Database='db', -Layout='lo',
> 'JobNo.'='452';
>                If: (Found_Count) == '0';
>                        Output: 'No Records Found';
>                Else;
>                        Records;
>                                Output: (Field: 'JobNo.');
>                        /Records;
>                /If;
>        /Inline;
> ?>
>
> It works fine in their old environment or if I search in another field. I
> also tried it in another database and the same result. I can't get any
> result if I search in a field with period in the name! I tried to escape it
> with \\. but no luck!
>
> PLEASE HELP! It's a really big issue for us...
>
> Thanks,
> Mohammad
> --
> View this message in context: http://www.nabble.com/Lasso-8.5-issue-with-field-names-which-contains-period-tp22364902p22364902.html
> Sent from the Lasso - Talk mailing list archive at Nabble.com.
>
>
>
> --
> This list is a free service of LassoSoft: http://www.LassoSoft.com/
> Search the list archives: http://www.ListSearch.com/Lasso/Browse/
> Manage your subscription: http://www.ListSearch.com/Lasso/
>
>
>



--
Mvh
Johan Sölve
____________________________________
Montania System AB
Halmstad   Stockholm   Malmö
http://www.montania.se

Johan Sölve
Mobil +46 709-51 55 70
[hidden email]

Kristinebergsvägen 17, S-302 41 Halmstad, Sweden
Telefon +46 35-136800 |  Fax +46 35-136801


--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/


Reply | Threaded
Open this post in threaded view
|

Re: Lasso 8.5 issue with field names which contains period

neocodemohammad

Johan Solve wrote
This is most likely not a Lasso issue but a FileMaker issue.

Periods in field names is covered on page 95 in the "FileMaker Server
9 Custom Web Publishing with XML and XSLT" manual
http://www.filemaker.com/downloads/pdf/fms9_cwp_xslt_en.pdf

Field names can contain periods, with the following exceptions:
- The period cannot be followed by a number. For example, myfield.9 is
an invalid field name.
- The period cannot be followed by the text string op (the two letters
“op”). For example, myfield.op is
an invalid field name.
- The period cannot be followed by the text string global (the word
“global”). For example, myfield.global is an invalid field name.

Also see page 89 "About the syntax for a fully qualified field name".

Anyway, your field names look like they should be ok. But we've also
had problems with periods in field names even if they meet the
requirements listed above. So far we've resorted to renaming the
fields or creating shadow calculation fields with a better name.

Maybe Lasso is involved in the problem after all? I haven't examined
the FMI query to see how it comes out, but if you want to look deeper
into this you can look at [action_statement] inside of the inline, you
can also try the output of [action_statement] directly against the FM
server.

On Fri, Mar 6, 2009 at 3:08 AM, neocodemohammad
<mohammad@neocodesoftware.com> wrote:
>
> Hi,
>
> We just upgrade a client to FM9 and Lasso 8.5. Some of their field names
> contain period, for example 'JobNo.' or 'ChargeNo.' Now none of the queries
> that are searching on any of those feild are returning any data. I dont even
> get an error message. Just a blank page. Here is a sample:
>
> <?LassoScript
>        Inline: -Search, -MaxRecords='all', -Database='db', -Layout='lo',
> 'JobNo.'='452';
>                If: (Found_Count) == '0';
>                        Output: 'No Records Found';
>                Else;
>                        Records;
>                                Output: (Field: 'JobNo.');
>                        /Records;
>                /If;
>        /Inline;
> ?>
>
> It works fine in their old environment or if I search in another field. I
> also tried it in another database and the same result. I can't get any
> result if I search in a field with period in the name! I tried to escape it
> with \\. but no luck!
>
> PLEASE HELP! It's a really big issue for us...
>
> Thanks,
> Mohammad
> --
> View this message in context: http://www.nabble.com/Lasso-8.5-issue-with-field-names-which-contains-period-tp22364902p22364902.html
> Sent from the Lasso - Talk mailing list archive at Nabble.com.
>
>
>
> --
> This list is a free service of LassoSoft: http://www.LassoSoft.com/
> Search the list archives: http://www.ListSearch.com/Lasso/Browse/
> Manage your subscription: http://www.ListSearch.com/Lasso/
>
>
>



--
Mvh
Johan Sölve
____________________________________
Montania System AB
Halmstad   Stockholm   Malmö
http://www.montania.se

Johan Sölve
Mobil +46 709-51 55 70
johan@montania.se

Kristinebergsvägen 17, S-302 41 Halmstad, Sweden
Telefon +46 35-136800 |  Fax +46 35-136801


--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/

Thanks Johan and everyone else:

- It's not a security issue as I add Username and password and i still get the same result.

- I added error_currenterror and action_statement to the inline and here is the result:

Error: 102, Error while performing FileMaker database -search action. Field is missing.
/fmi/xml/FMPXMLRESULT.xml?-db=ORDER&lay=NewOrder&-lop=and&JobNo..op=eq&JobNo.=491153&-max=20&skip=0&-find

I guess the problem is in 'JobNo..op=eq' part. I tried to escape it with \ and \\  but couldnt find any thing to work.
I'm going to start renaming all the fields :( It's a real pain in the ass.
Reply | Threaded
Open this post in threaded view
|

Re: Lasso 8.5 issue with field names which contains period

stevepiercy
In reply to this post by neocodemohammad
On Friday, March 6, 2009, [hidden email] (neocodemohammad) pronounced:

>>> We just upgrade a client to FM9 and Lasso 8.5. Some of their field names
>>> contain period, for example 'JobNo.' or 'ChargeNo.' Now none of the
>>> queries
>>> that are searching on any of those feild are returning any data. I dont
>>> even
>>> get an error message. Just a blank page. Here is a sample:
>>>
>>> <?LassoScript
>>>        Inline: -Search, -MaxRecords='all', -Database='db', -Layout='lo',
>>> 'JobNo.'='452';
>>>                If: (Found_Count) == '0';
>>>                        Output: 'No Records Found';
>>>                Else;
>>>                        Records;
>>>                                Output: (Field: 'JobNo.');
>>>                        /Records;
>>>                /If;
>>>        /Inline;
>>> ?>
>>>
>- I added error_currenterror and action_statement to the inline and here is
>the result:
>
>Error: 102, Error while performing FileMaker database -search action. Field
>is missing.
>/fmi/xml/FMPXMLRESULT.xml?-db=ORDER&lay=NewOrder&-lop=and&JobNo..op=eq&JobNo.=491153
>&-max=20&skip=0&-find
>
>I guess the problem is in 'JobNo..op=eq' part. I tried to escape it with \
>and \\  but couldnt find any thing to work.
>I'm going to start renaming all the fields :( It's a real pain in the ass.

That action_statement is not consistent with the inline you provided previously.  Your inline has the following parameters (reformatted for readability).

inline(
    -database   = 'ORDER',
    -layout     = 'NewOrder',
    'JobNo.'    = '452',
* some mysterious syntactically incorrect stuff *
    -maxrecords = '20',
    -search,
);

So provide the actual inline, sanitized of any db, table, username and password, and then we can identify the problem.

In my testing, fields that ended with a period could be searched, so I doubt there is any need to rename those fields.  In fact if you go about renaming your fields, you will likely still have the syntax issue in your inline.

--steve

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Steve Piercy               Web Site Builder               Soquel, CA
<[hidden email]>                  <http://www.StevePiercy.com/>


--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/


Reply | Threaded
Open this post in threaded view
|

Re: Lasso 8.5 issue with field names which contains period

EOwen
Apologies, I have only skimmed the full thread, but I wanted to report that I have had the same issue with FM Server 9 trying to use Custom Web Publishing XML/XSLT.

I had a field named -- per good FileMaker Inc.'s own recommended conventions, I might add -- "kp.Project_No.num".

Was getting a similar problem as the original poster -- no data back, with an error message "Field does not exist on that layout". I verified again and again that the field existed.

When I created a "shadow" field with no periods in the name as suggested by another poster, it worked, with the same exact code/XSLT. So clearly the problem was the periods.

I am testing now to see if maybe one period works and two doesn't, though really it's still a problem if two periods won't work.

Is there something to do with "escaping" periods as part of a URL? Periods wouldn't need to be escaped, I wouldn't think. Has anyone contacted FileMaker about this, since it clearly contradicts the docs cited here (which I also read over and over again for hidden meanings).
Reply | Threaded
Open this post in threaded view
|

Filemaker WPE crashes - XSLT culprit apparently

Mikael Sundström
In reply to this post by Johan Solve
Dear all,

Filemaker WPE (FMSA 10) often crashes and burns taking down my site.  
Hours of googling lead me to this thread...

http://forum-en.filemaker.com/t5/Report-a-bug/Filemaker-publishing-engine-crashes-randomly/td-p/2417

...which seems to indicate sloppy XSLT-handling in or by WPE. My  
question to knowledgeable listers is then and where I really need to  
have XSLT enabled in WPE for lasso solutions (and IWP which I use  
elsewhere) to work? Any input much appreciated, because these random  
crashes are driving me nuts.

/Mike



--------------------------------------------------
Mikael Sundström
Ph D | Senior Lecturer
Department of Political Science
Lund University
Lund
Sweden

tel. +46 46 2224993 | +46 705 811703
fax. +46 46 2224006
e-mail: [hidden email]
--------------------------------------------------





--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/


Reply | Threaded
Open this post in threaded view
|

Re: Filemaker WPE crashes - XSLT culprit apparently

stevepiercy
Lasso uses XML, not XSLT.  If you do not need XSLT for other
things, then you can safely disable it.

Nonetheless, frequent crashes of the WPE are not uncommon.  The
number one way to avoid crashes is to optimize your FM layouts
to return only the data you need for the inline.

Also check the LassoTalk archive and other resources for tips on
how to troubleshoot frequent crashes.  Here are few:

FMS Quick Start Guide:
http://www.lassosoft.com/Downloads/?product=Documentation_and_Guides&platform=&version=FileMaker%20Server%209%20Quick%20Start.pdf

http://old.nabble.com/Optimizing-Lasso-FileMaker-9-deployment-td14902876.html#a14911279

Don't store files in FM dbs:
http://old.nabble.com/Re%3A-Filemaker-vs-MySQL-%3A-Retrieve-Data-and-Images---A-question-of-Speed--p27644966.html

Make sure you have plenty of turkeys on hand.

--steve


On 4/1/10 at 11:40 AM, [hidden email] (Mikael
Sundström) pronounced:

>Dear all,
>
>Filemaker WPE (FMSA 10) often crashes and burns taking down my
>site. Hours of googling lead me to this thread...
>
>http://forum-en.filemaker.com/t5/Report-a-bug/Filemaker-publishing-engine-crashes-randomly
>/td-p/2417
>
>...which seems to indicate sloppy XSLT-handling in or by WPE.
>My question to knowledgeable listers is then and where I really
>need to have XSLT enabled in WPE for lasso solutions (and IWP
>which I use elsewhere) to work? Any input much appreciated,
>because these random crashes are driving me nuts.
>
>/Mike
>
>
>
>--------------------------------------------------
>Mikael Sundström
>Ph D | Senior Lecturer
>Department of Political Science
>Lund University
>Lund
>Sweden
>
>tel. +46 46 2224993 | +46 705 811703
>fax. +46 46 2224006
>e-mail: [hidden email]
>--------------------------------------------------
>
>
>
>
>
>--
>This list is a free service of LassoSoft: http://www.LassoSoft.com/
>Search the list archives: http://www.ListSearch.com/Lasso/Browse/
>Manage your subscription: http://www.ListSearch.com/Lasso/
>
>

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-- --
Steve Piercy               Web Site Builder              
Soquel, CA
<[hidden email]>                  <http://www.StevePiercy.com/>


--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/


Reply | Threaded
Open this post in threaded view
|

Re: Filemaker WPE crashes - XSLT culprit apparently

CryoGen
In reply to this post by Mikael Sundström
Mikael, I won't be much help with your immediate problem, but I did
have a recent conversation with a FileMaker technical lead who said
that XSLT support was likely to be deprecated when FileMaker 12 is
released.  We have several XSLT solutions that we are planning to
migrate as a result.

Rik

2010/4/1 Mikael Sundström <[hidden email]>:

> Dear all,
>
> Filemaker WPE (FMSA 10) often crashes and burns taking down my site. Hours
> of googling lead me to this thread...
>
> http://forum-en.filemaker.com/t5/Report-a-bug/Filemaker-publishing-engine-crashes-randomly/td-p/2417
>
> ...which seems to indicate sloppy XSLT-handling in or by WPE. My question to
> knowledgeable listers is then and where I really need to have XSLT enabled
> in WPE for lasso solutions (and IWP which I use elsewhere) to work? Any
> input much appreciated, because these random crashes are driving me nuts.
>
> /Mike
>
>
>
> --------------------------------------------------
> Mikael Sundström
> Ph D | Senior Lecturer
> Department of Political Science
> Lund University
> Lund
> Sweden
>
> tel. +46 46 2224993 | +46 705 811703
> fax. +46 46 2224006
> e-mail: [hidden email]
> --------------------------------------------------
>
>
>
>
>
> --
> This list is a free service of LassoSoft: http://www.LassoSoft.com/
> Search the list archives: http://www.ListSearch.com/Lasso/Browse/
> Manage your subscription: http://www.ListSearch.com/Lasso/
>
>
>

--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/


Reply | Threaded
Open this post in threaded view
|

Re: Filemaker WPE crashes - XSLT culprit apparently

maxwellk2
In reply to this post by Mikael Sundström
Hi Mike,

That's an interesting thread, can't believe I haven't found it before - certainly wouldn't want TSGal's job! I was recently having this problem as well, here's the thread:

        http://www.listsearch.com/Lasso/Thread/index.lasso?23495#255377

As soon as I rolled those WPE logs everything went back to normal, hope it's that easy of a fix for you. I've been running FMS10 under Mac Server 10.5 with Lasso-based solutions for over a year with only two major events, both of which I believe are related to the same bloated log issue. I only have XML enabled - PHP, XSLT, and especially Instant Web Publishing, are all disabled. I second Steve's recommendations, also, if you try a full reinstall, backup your database files and make sure to move the /Library/FileMaker Server folder. The uninstall process doesn't remove this entirely and will *not* give you a clean reinstall.

HTH,
Max

On Apr 1, 2010, at 2:40 AM, Mikael Sundström wrote:

> Dear all,
>
> Filemaker WPE (FMSA 10) often crashes and burns taking down my site. Hours of googling lead me to this thread...
>
> http://forum-en.filemaker.com/t5/Report-a-bug/Filemaker-publishing-engine-crashes-randomly/td-p/2417
>
> ...which seems to indicate sloppy XSLT-handling in or by WPE. My question to knowledgeable listers is then and where I really need to have XSLT enabled in WPE for lasso solutions (and IWP which I use elsewhere) to work? Any input much appreciated, because these random crashes are driving me nuts.
>
> /Mike
>
>
>
> --------------------------------------------------
> Mikael Sundström
> Ph D | Senior Lecturer
> Department of Political Science
> Lund University
> Lund
> Sweden
>
> tel. +46 46 2224993 | +46 705 811703
> fax. +46 46 2224006
> e-mail: [hidden email]
> --------------------------------------------------

--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/


Reply | Threaded
Open this post in threaded view
|

Re: Filemaker WPE crashes - XSLT culprit apparently

maxwellk2
Oops, sorry Mike, I just remembered that both PHP and XML need to be enabled for Lasso to work. Bad idea posting to the list un-caffeinated.


On Apr 1, 2010, at 8:54 AM, Maxwell Klein wrote:

> Hi Mike,
>
> That's an interesting thread, can't believe I haven't found it before - certainly wouldn't want TSGal's job! I was recently having this problem as well, here's the thread:
>
> http://www.listsearch.com/Lasso/Thread/index.lasso?23495#255377
>
> As soon as I rolled those WPE logs everything went back to normal, hope it's that easy of a fix for you. I've been running FMS10 under Mac Server 10.5 with Lasso-based solutions for over a year with only two major events, both of which I believe are related to the same bloated log issue. I only have XML enabled - PHP, XSLT, and especially Instant Web Publishing, are all disabled. I second Steve's recommendations, also, if you try a full reinstall, backup your database files and make sure to move the /Library/FileMaker Server folder. The uninstall process doesn't remove this entirely and will *not* give you a clean reinstall.
>
> HTH,
> Max
>
> On Apr 1, 2010, at 2:40 AM, Mikael Sundström wrote:
>
>> Dear all,
>>
>> Filemaker WPE (FMSA 10) often crashes and burns taking down my site. Hours of googling lead me to this thread...
>>
>> http://forum-en.filemaker.com/t5/Report-a-bug/Filemaker-publishing-engine-crashes-randomly/td-p/2417
>>
>> ...which seems to indicate sloppy XSLT-handling in or by WPE. My question to knowledgeable listers is then and where I really need to have XSLT enabled in WPE for lasso solutions (and IWP which I use elsewhere) to work? Any input much appreciated, because these random crashes are driving me nuts.
>>
>> /Mike
>>
>>
>>
>> --------------------------------------------------
>> Mikael Sundström
>> Ph D | Senior Lecturer
>> Department of Political Science
>> Lund University
>> Lund
>> Sweden
>>
>> tel. +46 46 2224993 | +46 705 811703
>> fax. +46 46 2224006
>> e-mail: [hidden email]
>> --------------------------------------------------

--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/


Reply | Threaded
Open this post in threaded view
|

Re: Filemaker WPE crashes - XSLT culprit apparently

Mikael Sundström
No worries, although I didn't realise that PHP was in fact required.  
Will check your tip abour bloated logs. I just turned off XSLT and no  
aspect of the site seems in any way affected. I also banned a  
SiteSeeker robot which seemed to trigger the problem in the first  
place (odd, really, but there you are).

Happy Easter all!

/Mike


1 apr 2010 kl. 18.22 skrev Maxwell Klein:

> Oops, sorry Mike, I just remembered that both PHP and XML need to be  
> enabled for Lasso to work. Bad idea posting to the list un-
> caffeinated.
>
>
> On Apr 1, 2010, at 8:54 AM, Maxwell Klein wrote:
>
>> Hi Mike,
>>
>> That's an interesting thread, can't believe I haven't found it  
>> before - certainly wouldn't want TSGal's job! I was recently having  
>> this problem as well, here's the thread:
>>
>> http://www.listsearch.com/Lasso/Thread/index.lasso?23495#255377
>>
>> As soon as I rolled those WPE logs everything went back to normal,  
>> hope it's that easy of a fix for you. I've been running FMS10 under  
>> Mac Server 10.5 with Lasso-based solutions for over a year with  
>> only two major events, both of which I believe are related to the  
>> same bloated log issue. I only have XML enabled - PHP, XSLT, and  
>> especially Instant Web Publishing, are all disabled. I second  
>> Steve's recommendations, also, if you try a full reinstall, backup  
>> your database files and make sure to move the /Library/FileMaker  
>> Server folder. The uninstall process doesn't remove this entirely  
>> and will *not* give you a clean reinstall.
>>
>> HTH,
>> Max
>>
>> On Apr 1, 2010, at 2:40 AM, Mikael Sundström wrote:
>>
>>> Dear all,
>>>
>>> Filemaker WPE (FMSA 10) often crashes and burns taking down my  
>>> site. Hours of googling lead me to this thread...
>>>
>>> http://forum-en.filemaker.com/t5/Report-a-bug/Filemaker-publishing-engine-crashes-randomly/td-p/2417
>>>
>>> ...which seems to indicate sloppy XSLT-handling in or by WPE. My  
>>> question to knowledgeable listers is then and where I really need  
>>> to have XSLT enabled in WPE for lasso solutions (and IWP which I  
>>> use elsewhere) to work? Any input much appreciated, because these  
>>> random crashes are driving me nuts.
>>>
>>> /Mike
>>>
>>>
>>>
>>> --------------------------------------------------
>>> Mikael Sundström
>>> Ph D | Senior Lecturer
>>> Department of Political Science
>>> Lund University
>>> Lund
>>> Sweden
>>>
>>> tel. +46 46 2224993 | +46 705 811703
>>> fax. +46 46 2224006
>>> e-mail: [hidden email]
>>> --------------------------------------------------
>
> --
> This list is a free service of LassoSoft: http://www.LassoSoft.com/
> Search the list archives: http://www.ListSearch.com/Lasso/Browse/
> Manage your subscription: http://www.ListSearch.com/Lasso/
>
>

--------------------------------------------------
Mikael Sundström
Ph D | Senior Lecturer
Department of Political Science
Lund University
Lund
Sweden

tel. +46 46 2224993 | +46 705 811703
fax. +46 46 2224006
e-mail: [hidden email]
--------------------------------------------------





--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/


Reply | Threaded
Open this post in threaded view
|

Re: Filemaker WPE crashes - XSLT culprit apparently

Mikael Sundström
Maxwell,

Is your suggested thread really the right one? Seems strange to me,  
but maybe it's just too late in the evening for me...

/Mike




1 apr 2010 kl. 18.30 skrev Mikael Sundström:

> No worries, although I didn't realise that PHP was in fact required.
> Will check your tip abour bloated logs. I just turned off XSLT and no
> aspect of the site seems in any way affected. I also banned a
> SiteSeeker robot which seemed to trigger the problem in the first
> place (odd, really, but there you are).
>
> Happy Easter all!
>
> /Mike
>
>
> 1 apr 2010 kl. 18.22 skrev Maxwell Klein:
>
>> Oops, sorry Mike, I just remembered that both PHP and XML need to be
>> enabled for Lasso to work. Bad idea posting to the list un-
>> caffeinated.
>>
>>
>> On Apr 1, 2010, at 8:54 AM, Maxwell Klein wrote:
>>
>>> Hi Mike,
>>>
>>> That's an interesting thread, can't believe I haven't found it
>>> before - certainly wouldn't want TSGal's job! I was recently having
>>> this problem as well, here's the thread:
>>>
>>> http://www.listsearch.com/Lasso/Thread/index.lasso?23495#255377
>>>
>>> As soon as I rolled those WPE logs everything went back to normal,
>>> hope it's that easy of a fix for you. I've been running FMS10 under
>>> Mac Server 10.5 with Lasso-based solutions for over a year with
>>> only two major events, both of which I believe are related to the
>>> same bloated log issue. I only have XML enabled - PHP, XSLT, and
>>> especially Instant Web Publishing, are all disabled. I second
>>> Steve's recommendations, also, if you try a full reinstall, backup
>>> your database files and make sure to move the /Library/FileMaker
>>> Server folder. The uninstall process doesn't remove this entirely
>>> and will *not* give you a clean reinstall.
>>>
>>> HTH,
>>> Max
>>>
>>> On Apr 1, 2010, at 2:40 AM, Mikael Sundström wrote:
>>>
>>>> Dear all,
>>>>
>>>> Filemaker WPE (FMSA 10) often crashes and burns taking down my
>>>> site. Hours of googling lead me to this thread...
>>>>
>>>> http://forum-en.filemaker.com/t5/Report-a-bug/Filemaker-publishing-engine-crashes-randomly/td-p/2417
>>>>
>>>> ...which seems to indicate sloppy XSLT-handling in or by WPE. My
>>>> question to knowledgeable listers is then and where I really need
>>>> to have XSLT enabled in WPE for lasso solutions (and IWP which I
>>>> use elsewhere) to work? Any input much appreciated, because these
>>>> random crashes are driving me nuts.
>>>>
>>>> /Mike
>>>>
>>>>
>>>>
>>>> --------------------------------------------------
>>>> Mikael Sundström
>>>> Ph D | Senior Lecturer
>>>> Department of Political Science
>>>> Lund University
>>>> Lund
>>>> Sweden
>>>>
>>>> tel. +46 46 2224993 | +46 705 811703
>>>> fax. +46 46 2224006
>>>> e-mail: [hidden email]
>>>> --------------------------------------------------
>>
>> --
>> This list is a free service of LassoSoft: http://www.LassoSoft.com/
>> Search the list archives: http://www.ListSearch.com/Lasso/Browse/
>> Manage your subscription: http://www.ListSearch.com/Lasso/
>>
>>
>
> --------------------------------------------------
> Mikael Sundström
> Ph D | Senior Lecturer
> Department of Political Science
> Lund University
> Lund
> Sweden
>
> tel. +46 46 2224993 | +46 705 811703
> fax. +46 46 2224006
> e-mail: [hidden email]
> --------------------------------------------------
>
>
>
>
>
> --
> This list is a free service of LassoSoft: http://www.LassoSoft.com/
> Search the list archives: http://www.ListSearch.com/Lasso/Browse/
> Manage your subscription: http://www.ListSearch.com/Lasso/
>
>

--------------------------------------------------
Mikael Sundström
Ph D | Senior Lecturer
Department of Political Science
Lund University
Lund
Sweden

tel. +46 46 2224993 | +46 705 811703
fax. +46 46 2224006
e-mail: [hidden email]
--------------------------------------------------





--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/


Reply | Threaded
Open this post in threaded view
|

Re: Filemaker WPE crashes - XSLT culprit apparently

maxwellk2
Oh, sorry, the thread did kind of get long in the tooth, here's the [SOLVED] portion:

        http://www.listsearch.com/Lasso/Thread/index.lasso?23582#255836



On Apr 1, 2010, at 9:34 AM, Mikael Sundström wrote:

> Maxwell,
>
> Is your suggested thread really the right one? Seems strange to me, but maybe it's just too late in the evening for me...
>
> /Mike
>
>
>
>
> 1 apr 2010 kl. 18.30 skrev Mikael Sundström:
>
>> No worries, although I didn't realise that PHP was in fact required.
>> Will check your tip abour bloated logs. I just turned off XSLT and no
>> aspect of the site seems in any way affected. I also banned a
>> SiteSeeker robot which seemed to trigger the problem in the first
>> place (odd, really, but there you are).
>>
>> Happy Easter all!
>>
>> /Mike
>>
>>
>> 1 apr 2010 kl. 18.22 skrev Maxwell Klein:
>>
>>> Oops, sorry Mike, I just remembered that both PHP and XML need to be
>>> enabled for Lasso to work. Bad idea posting to the list un-
>>> caffeinated.
>>>
>>>
>>> On Apr 1, 2010, at 8:54 AM, Maxwell Klein wrote:
>>>
>>>> Hi Mike,
>>>>
>>>> That's an interesting thread, can't believe I haven't found it
>>>> before - certainly wouldn't want TSGal's job! I was recently having
>>>> this problem as well, here's the thread:
>>>>
>>>> http://www.listsearch.com/Lasso/Thread/index.lasso?23495#255377
>>>>
>>>> As soon as I rolled those WPE logs everything went back to normal,
>>>> hope it's that easy of a fix for you. I've been running FMS10 under
>>>> Mac Server 10.5 with Lasso-based solutions for over a year with
>>>> only two major events, both of which I believe are related to the
>>>> same bloated log issue. I only have XML enabled - PHP, XSLT, and
>>>> especially Instant Web Publishing, are all disabled. I second
>>>> Steve's recommendations, also, if you try a full reinstall, backup
>>>> your database files and make sure to move the /Library/FileMaker
>>>> Server folder. The uninstall process doesn't remove this entirely
>>>> and will *not* give you a clean reinstall.
>>>>
>>>> HTH,
>>>> Max
>>>>
>>>> On Apr 1, 2010, at 2:40 AM, Mikael Sundström wrote:
>>>>
>>>>> Dear all,
>>>>>
>>>>> Filemaker WPE (FMSA 10) often crashes and burns taking down my
>>>>> site. Hours of googling lead me to this thread...
>>>>>
>>>>> http://forum-en.filemaker.com/t5/Report-a-bug/Filemaker-publishing-engine-crashes-randomly/td-p/2417
>>>>>
>>>>> ...which seems to indicate sloppy XSLT-handling in or by WPE. My
>>>>> question to knowledgeable listers is then and where I really need
>>>>> to have XSLT enabled in WPE for lasso solutions (and IWP which I
>>>>> use elsewhere) to work? Any input much appreciated, because these
>>>>> random crashes are driving me nuts.
>>>>>
>>>>> /Mike
>>>>>
>>>>>
>>>>>
>>>>> --------------------------------------------------
>>>>> Mikael Sundström
>>>>> Ph D | Senior Lecturer
>>>>> Department of Political Science
>>>>> Lund University
>>>>> Lund
>>>>> Sweden
>>>>>
>>>>> tel. +46 46 2224993 | +46 705 811703
>>>>> fax. +46 46 2224006
>>>>> e-mail: [hidden email]
>>>>> --------------------------------------------------
>>>
>>> --
>>> This list is a free service of LassoSoft: http://www.LassoSoft.com/
>>> Search the list archives: http://www.ListSearch.com/Lasso/Browse/
>>> Manage your subscription: http://www.ListSearch.com/Lasso/
>>>
>>>
>>
>> --------------------------------------------------
>> Mikael Sundström
>> Ph D | Senior Lecturer
>> Department of Political Science
>> Lund University
>> Lund
>> Sweden
>>
>> tel. +46 46 2224993 | +46 705 811703
>> fax. +46 46 2224006
>> e-mail: [hidden email]
>> --------------------------------------------------
>>
>>
>>
>>
>>
>> --
>> This list is a free service of LassoSoft: http://www.LassoSoft.com/
>> Search the list archives: http://www.ListSearch.com/Lasso/Browse/
>> Manage your subscription: http://www.ListSearch.com/Lasso/
>>
>>
>
> --------------------------------------------------
> Mikael Sundström
> Ph D | Senior Lecturer
> Department of Political Science
> Lund University
> Lund
> Sweden
>
> tel. +46 46 2224993 | +46 705 811703
> fax. +46 46 2224006
> e-mail: [hidden email]
> --------------------------------------------------
>
>
>
>
>
> --
> This list is a free service of LassoSoft: http://www.LassoSoft.com/
> Search the list archives: http://www.ListSearch.com/Lasso/Browse/
> Manage your subscription: http://www.ListSearch.com/Lasso/
>
>


--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/


Reply | Threaded
Open this post in threaded view
|

Re: Filemaker WPE crashes - XSLT culprit apparently

stevepiercy
In reply to this post by maxwellk2
Lasso does not need PHP (or IWP or any other TLA than XML)
enabled in FMS.

More caffeine, or April Fools?  ;)

--steve


On 4/1/10 at 9:22 AM, [hidden email] (Maxwell Klein) pronounced:

>Oops, sorry Mike, I just remembered that both PHP and XML need
>to be enabled for Lasso to work. Bad idea posting to the list un-caffeinated.
>
>
>On Apr 1, 2010, at 8:54 AM, Maxwell Klein wrote:
>
>>Hi Mike,
>>
>>That's an interesting thread, can't believe I haven't found it before - certainly
>wouldn't want TSGal's job! I was recently having this problem as well, here's the thread:
>>
>>http://www.listsearch.com/Lasso/Thread/index.lasso?23495#255377
>>
>>As soon as I rolled those WPE logs everything went back to normal, hope it's that easy
>of a fix for you. I've been running FMS10 under Mac Server 10.5
>with Lasso-based solutions for over a year with only two major
>events, both of which I believe are related to the same bloated
>log issue. I only have XML enabled - PHP, XSLT, and especially
>Instant Web Publishing, are all disabled. I second Steve's
>recommendations, also, if you try a full reinstall, backup your
>database files and make sure to move the /Library/FileMaker
>Server folder. The uninstall process doesn't remove this
>entirely and will *not* give you a clean reinstall.
>>
>>HTH,
>>Max
>>
>>On Apr 1, 2010, at 2:40 AM, Mikael Sundström wrote:
>>
>>> Dear all,
>>>   Filemaker WPE (FMSA 10) often crashes and burns taking
>>>down my site. Hours of googling
>lead me to this thread...
>>>  
>http://forum-en.filemaker.com/t5/Report-a-bug/Filemaker-publishing-engine-crashes-randomly
>/td-p/2417
>>>   ...which seems to indicate sloppy XSLT-handling in or by
>>>WPE. My question to
>knowledgeable listers is then and where I really need to have
>XSLT enabled in WPE for lasso solutions (and IWP which I use
>elsewhere) to work? Any input much appreciated, because these
>random crashes are driving me nuts.
>>>   /Mike
>>>     --------------------------------------------------
>>> Mikael Sundström
>>> Ph D | Senior Lecturer
>>> Department of Political Science
>>> Lund University
>>> Lund
>>> Sweden
>>>   tel. +46 46 2224993 | +46 705 811703
>>> fax. +46 46 2224006
>>> e-mail: [hidden email]
>>> --------------------------------------------------
>
>--
>This list is a free service of LassoSoft: http://www.LassoSoft.com/
>Search the list archives: http://www.ListSearch.com/Lasso/Browse/
>Manage your subscription: http://www.ListSearch.com/Lasso/
>
>

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-- --
Steve Piercy               Web Site Builder              
Soquel, CA
<[hidden email]>                  <http://www.StevePiercy.com/>


--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/


Reply | Threaded
Open this post in threaded view
|

Re: Filemaker WPE crashes - XSLT culprit apparently

maxwellk2
Huh, I tried turning it off just a few weeks ago and Lasso sites stopped working - still not caffeinated enough for April Fools ;-) Testing it now.....

....you are correct sir, PHP is NOT required. Awesome, one less security hole and one less thing to go wrong in FMS. Now backing away from the computer to get a double helping of Peet's house blend, that usually does the trick.

Thanks,
Max


On Apr 1, 2010, at 10:07 AM, Steve Piercy - Web Site Builder wrote:

> Lasso does not need PHP (or IWP or any other TLA than XML) enabled in FMS.
>
> More caffeine, or April Fools?  ;)
>
> --steve
>
>
> On 4/1/10 at 9:22 AM, [hidden email] (Maxwell Klein) pronounced:
>
>> Oops, sorry Mike, I just remembered that both PHP and XML need to be enabled for Lasso to work. Bad idea posting to the list un-caffeinated.
>>
>>
>> On Apr 1, 2010, at 8:54 AM, Maxwell Klein wrote:
>>
>>> Hi Mike,
>>>
>>> That's an interesting thread, can't believe I haven't found it before - certainly
>> wouldn't want TSGal's job! I was recently having this problem as well, here's the thread:
>>>
>>> http://www.listsearch.com/Lasso/Thread/index.lasso?23495#255377
>>>
>>> As soon as I rolled those WPE logs everything went back to normal, hope it's that easy
>> of a fix for you. I've been running FMS10 under Mac Server 10.5 with Lasso-based solutions for over a year with only two major events, both of which I believe are related to the same bloated log issue. I only have XML enabled - PHP, XSLT, and especially Instant Web Publishing, are all disabled. I second Steve's recommendations, also, if you try a full reinstall, backup your database files and make sure to move the /Library/FileMaker Server folder. The uninstall process doesn't remove this entirely and will *not* give you a clean reinstall.
>>>
>>> HTH,
>>> Max
>>>
>>> On Apr 1, 2010, at 2:40 AM, Mikael Sundström wrote:
>>>
>>>> Dear all,
>>>>  Filemaker WPE (FMSA 10) often crashes and burns taking down my site. Hours of googling
>> lead me to this thread...
>>>>
>> http://forum-en.filemaker.com/t5/Report-a-bug/Filemaker-publishing-engine-crashes-randomly
>> /td-p/2417
>>>>  ...which seems to indicate sloppy XSLT-handling in or by WPE. My question to
>> knowledgeable listers is then and where I really need to have XSLT enabled in WPE for lasso solutions (and IWP which I use elsewhere) to work? Any input much appreciated, because these random crashes are driving me nuts.
>>>>  /Mike
>>>>    --------------------------------------------------
>>>> Mikael Sundström
>>>> Ph D | Senior Lecturer
>>>> Department of Political Science
>>>> Lund University
>>>> Lund
>>>> Sweden
>>>>  tel. +46 46 2224993 | +46 705 811703
>>>> fax. +46 46 2224006
>>>> e-mail: [hidden email]
>>>> --------------------------------------------------
>>
>> --
>> This list is a free service of LassoSoft: http://www.LassoSoft.com/
>> Search the list archives: http://www.ListSearch.com/Lasso/Browse/
>> Manage your subscription: http://www.ListSearch.com/Lasso/
>>
>>
>
> -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> Steve Piercy               Web Site Builder               Soquel, CA
> <[hidden email]>                  <http://www.StevePiercy.com/>
>
>
> --
> This list is a free service of LassoSoft: http://www.LassoSoft.com/
> Search the list archives: http://www.ListSearch.com/Lasso/Browse/
> Manage your subscription: http://www.ListSearch.com/Lasso/
>
>


--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/