can't add XML/XSLT records in FMSA9, worked in FMSA8

[wplate]

Today I moved our database files to the new server running FMSA 9, our files were previously on a FMSA 8 system.

We have a few scripts in a few places that create records in the database via XML/XSLT/Custom Web Publishing/Whatever and they don't seem to work.

Here's an example:

http://OLD.IPA.DDR.ESS/fmi/xml/fmresultset.xml?-db=CartSales&-lay=Orders&BillingFirstName=Wes&BillingLastName=Plate&BillingCompany=Duck&BillingAddress1=TEST&BillingAddress2=TEST&BillingCity=TEST&BillingState=TEST&BillingZip=TEST&BillingCountry=TEST&BillingPhone=TEST&BillingEmail=TEST&ShippingFirstName=TEST&ShippingLastName=TEST&ShippingCompany=TEST&ShippingAddress1=TEST&ShippingAddress2=TEST&ShippingCity=TEST&ShippingState=TEST&ShippingZip=TEST&ShippingCountry=TEST&ShippingPhone=TEST&ShippingCharge=TEST&CreditCard=TEST&CCExpire=TEST&Comments=TEST&CartOrderID=TEST&-new

This does not work...

http://NEW.IPA.DDR.ESS/fmi/xml/fmresultset.xml?-db=CartSales&-lay=Orders&BillingFirstName=Wes&BillingLastName=Plate&BillingCompany=Duck&BillingAddress1=TEST&BillingAddress2=TEST&BillingCity=TEST&BillingState=TEST&BillingZip=TEST&BillingCountry=TEST&BillingPhone=TEST&BillingEmail=TEST&ShippingFirstName=TEST&ShippingLastName=TEST&ShippingCompany=TEST&ShippingAddress1=TEST&ShippingAddress2=TEST&ShippingCity=TEST&ShippingState=TEST&ShippingZip=TEST&ShippingCountry=TEST&ShippingPhone=TEST&ShippingCharge=TEST&CreditCard=TEST&CCExpire=TEST&Comments=TEST&CartOrderID=TEST&-new

The only difference is the IP address.

Safari gives this error...

And Firefox this error...

I'm not sure what I need to do on the new server side, the system is essentially in its default setup, everything is enabled.

Help! -)

[wplate]

Unfortunately calling FileMaker did no good. I guess once you start down the road of Custom Web Publishing, you're officially unsupported.

"But can you tell me why something that worked in FMSA8 doesn't in FMSA9?"

"Sorry, No."

Sorry, I'm venting. I hope someone here can help me.

[wplate]

I've paired back my URL to one field, and it comes in, so I'm now going through and adding another field then another to my URL so I see when it finally breaks.

[wplate]

Could it be that FMSA9 is now limiting the number of characters in the URL?

This URL works, it is 503 characters

http://XXX.XXX.XXX.XXX/fmi/xml/fmresultset.xml?-db=CartSales&-lay=Orders&BillingFirstName=44555555555511111111112222222222333333333344444444445555555555111111111122222222223333333333444444444455555555551111111111222222222233333333334444444444555555555511111111112222222222333333333344444444445555555555111111111122222222223333333333444444444455555555551111111111222222222233333333334444444444555555555511111111112222222222333333333344444444445555555555111111111122222222223333333333444444444455555555&-new

But if I add one more character to the URL and make it 504 characters, I get XML Parsing Error: no element found

http://XXX.XXX.XXX.XXX/fmi/xml/fmresultset.xml?-db=CartSales&-lay=Orders&BillingFirstName=445555555555111111111122222222223333333333444444444455555555551111111111222222222233333333334444444444555555555511111111112222222222333333333344444444445555555555111111111122222222223333333333444444444455555555551111111111222222222233333333334444444444555555555511111111112222222222333333333344444444445555555555111111111122222222223333333333444444444455555555551111111111222222222233333333334444444444555555555&-new

Does this make sense to anyone?

[wplate]

SUCCESS!

I called FileMaker back. This new support guy was a bit more helpful. He asked if I'd turned off Performance Cache in the web server. No I'd not. See page 88 of the Getting Started Guide...

Ok, so I disabled it, uninstalled FMSA then reinstalled, now I'm happy. HOORAY!

[Steven H. Blackwell]

This is what happens when we all go off to Devcon. Sorry I did not see your messages until today. Performance cache causes known issues with the WPE. It should be disabled.

Steven