Server 7 Advanced - Custom Web Publishing Issue

[Keith Kurzendoerfer]

Hi:

We've recently installed Server 7 Advanced on a machine running OS X 10.3.5, but we are having trouble getting the Custom Web Publishing to work correctly. When submitting an html form to a Server 7 database, we get an Apache error that says "Method Not Allowed: The requested method POST is not allowed for the URL /drick-new/index.xsl."

I've checked to make sure that the databas is showing up in the Web Publishing Administration Console and has a + mark by XSLT Publishing.

Any ideas are appreciated!

Thanks!

Keith

Keith Kurzendoerfer

Research and Instructional Technology

University of Kentucky

[Keith Kurzendoerfer]

Update:

I talked to a gentleman from filemaker who indicated that safari couldn't handle the .xsl files. So I opened my custom Web pages in IE, and dicovered that the Web Server isn't processing the pages correctly and is just displaying the code for the webpages. a.k.a looking at the page in IE shows the same results as if I was looking in the page in a text editor.

The gentleman from Filemaker said that this was a known issue with the Apache and that they couldn't help me, but I should look into support for Apache.

I'm really frustrated that Filemaker Server 7 Advanced isn't working correctly out of the box. Can anyone provide a solution to this problem.

I really appreciate your help!

Keith Kurzendoerfer

Research and Instructional Technologies

University of Kentucky

PS - Instant Web Publishing is working correctly.

[rfranco]

Kieth,

I had the same problem. To fix it delete method="post". Don't use the method attribute with FileMaker 7. Make sure the form action attribute has the correct URL.

[Martin Brändle]

Kieth,

To fix it delete method="post". Don't use the method attribute with FileMaker 7.

That's not correct. I have several stylesheets that work with method="post", on FMS7A on OS X server. However, make sure that the layout you reference with <input type="hidden" name="-lay" value="yourlayout"/> contains all fields that you want to search.

And for debugging, also check /Library/FileMaker Server 7/Web Publishing/logs/pe_application_log.txt

Martin

[ibiubu]

One thing I found...the layout you are trying to access on the web, if you have any related fields on that layout, make sure they are placed in portals. There have been many reports of FM not parsing the XML correctly if ALL related fields are not in portals.

Larry

[Martin Brändle]

One thing I found...the layout you are trying to access on the web, if you have any related fields on that layout, make sure they are placed in portals. There have been many reports of FM not parsing the XML correctly if ALL related fields are not in portals.

Larry

I noticed also the following behaviour: Portals are split up in various <relatedset> elements in the XML result tree if not all fields were added at the same time to the portal. The result tree might then be very difficult to handle with XSLT. If this occurs, it is best to delete the layout and to create it again. In general the order of fields in the result tree is the order one has added them in the layout. Therefore, one has to think a little bit first about all fields that shall be used in a layout.

For example: A layout has been created with a field "x" and a portal "y", with fields "y1","y2". Later a field "z" has been added, and a field "y3" has been added to the portal.

The XML result tree would then look like:

<fmresultset ...>

(...)

<resultset>

  <record ...>

    <field name="x"><data>...</data></field>

    <relatedset count="..." table="y">

       <record ...>

          <field name="y::y1"><data>...</data></field>

          <field name="y::y2"><data>...</data></field>

       </record>

    </relatedset>

    <field name="z"><data>...</data></field>

    <relatedset count="..." table="y">

      <record ...>

         <field name="y::y3"><data>...</data></field>

      </record>

    </relatedset>

  </record>

</resultset>

</fmresultset>

So, the fields, although grouped together in the portal on the layout, are not grouped together in the XML tree. I think, that would be something that FileMaker could correct in one of their next updates of FMS7A.

Martin