CDML and XSLT?

[fm-bonehead]

Hi Everyone,

Brought a filemaker v. 6 database up to version 7. The v6 file had been served on the web using Custom web publishing with some CDML code. The CDML conversion tool barfed up lots of errors, and it's output wasn't useful. Wondering if anyone can help me with the following CDML form code that I had inside an html file (see attached)

This code was contained inside a file called 'index.html.' When a browser requested this page, the form would load in the client browser, then the user would fill it out and click 'submit', which would add a new record to our FM database.

I cannot get this to work under CWP in FMP server 7. I have everything installed and working right, but when I click 'submit' I get an error that the server cannot find "FMPro". I assume that this is because the server no longer understands CDML, but I cannot get the XSLT syntax right.

Can anyone shed some light on what this XSLT code might look like?

cdml_code.txt

[Martin Brändle]

This is still the old query valid for FM4-6.

Just take your index.html, convert it with the CDML2XSLT tool, and stuff the resulting form in index.xsl back into index.html.

Then it should work, hopefully.

[fm-bonehead]

As I mentioned, I already tried the converter tool, and it didn't work (not even close). Any thoughts?

[Martin Brändle]

Really? I was able to convert your little form fragment, see attachment.

You should check the log file of your conversion and see where the problem was.

Normally you also get a XSl file, even if the conversion is not complete. Then you get some comments within the XSL file where a problem might have occured.

Or try to figure out the correct query from Appendix A of the FMS7A Custom Web Publishing Guide. And read also Appendix C.

cdml2xsl.zip

[Steve St-Laurent]

Really? I've been unsuccessful at any attempt to use the CDML2XSL tool. Doesn't matter

[Martin Brändle]

Of course the CDML2XSLT tool can't be perfect and match all the imagination of the web designers.

I had also such cases where conversion stopped. These were especially those files which had nested fmp-inlineactions.

What I did in this case: remove the html file in question (i.e. place in another folder), then start the conversion again with the remaining files.

At the end then commented out some parts in the html files that could not be converted (with or even remove the parts in question) and did the conversion again.

Out of my >>100 files, 10 did convert with errors and had to be adjusted manually.

See also this thread for handling fmp-includes

P.S. Steve, can you post your HTML example?