parsing error on XML import

[tomp]

The attached XML file works fine as a 'file' import. But when importing via http (using the same XSLT file), the import gets a parsing error. The xml file and the parsing error description are attached.

What's different when importing via http vs. a file import? Where/what is the expected 'white space' when doing the http import?

RM5currentRelease.xml

[comment]

Please allow us to reproduce the problem by providing the XSLT stylesheet and the URL. 

FWIW, I had no problems importing the attached file from here:
https://fmforums.com/applications/core/interface/file/attachment.php?id=27768
using my own stylesheet.

[tomp]

I apologize for missing your October 15 post. I still have the problem.

The style sheet (RM5currentRelease.xslt) has been uploaded for reference here. I have compared it to and it matches the style sheet available from the 'Technical Resources', XML example files, on the Filemaker support/downloads screen

This style sheet and  procedure for retrieving the data from the xml data source on my web-site has been functioning literally for more than a decade but for some reason has recently ceased to function. I have been using BBedit to update the XML file on my computer and then uploading the new version to my web-site.  It hasn't been an issue before.

Again, when I use the 'file' option to import the file from my computer using this style sheet, I do not get the error. Only when, after uploading the same xml file to my web-site and using the 'http request' option in the import records script step, do I get the above error.

This is the 'http request' source that gives the 718 parsing error for the Import Records script step:

http://www.tcpms.com/RM5currentRelease.xml

Here's the import script step:

 

RM5currentRelease.xslt

[comment]

i have tried to reproduce the issue using the URL and the stylesheet provided in your latest post: 

 

 

It imports perfectly fine, with no errors whatsoever. To be sure, I tried it again using version 15, as shown in your profile. Again, no problems. The problem must be elsewhere. Or it could be intermittent.

 

 

Edited November 3, 2018 by comment

[tomp]

It's not intermittent. It started about a month ago and has continued ever since.  I have 2 different applications deployed (via runtimes) and all my users (that I have heard from) are experiencing the issue

Did you import from the file on my web-site without incident?

I did some more testing using the xml example files from the Filemaker support/downloads site. 

I ran a test on my computer, using the attribute import as supplied. All was ok.

I ftp'ed the xml file - mdso_attrib.xml - to my web-site, modified the import records script step for the http option, and got the same parsing error experienced with my software.

I downloaded the xml file back to the examples folder, took the import records script step back to its original state and tested. All was OK

Since the xml file continued to work after the upload/download sequence, it doesn't appear the ftp modified the file.

Since my users in both mac and windows environments (they pull the file from my web-site to see if there is an update available for  my system) are all experiencing the parsing error I have been describing, I'm concluding the following:

1- if you were able to import using the xml file on my web-site, the problem is not on the web-site.

2- If you were not, perhaps the issue in some way or manner is on the web-site (please confirm whether you used the file on my web-site)

3- Since both my applications and the Filemaker xml example application experience the same issue, the problem is not in my application but lies elsewhere.

4- Maybe in my FM15 installation? Except I have the issue both from the mac and the windows sides.

What really has me scratching my head is why this process that has reliably given my users a way to check for a new release of my software for years and years suddenly stopped working.

[comment]

As I said, I imported (several times) from the web address you have provided, using the stylesheet you have provided (see my screenshot above showing both).

Since I cannot reproduce the problem, any speculation regarding the cause would be just that.

FWIW, I am attaching the files I used for testing - you can use them to eliminate your own files as the suspects.

 

 

Archive.zip

[tomp]

Well, that does it. Using your code I finally got the import without the parsing error.

With kid gloves I'm going to integrate this script, or if I have to, this file, into my applications.

I have no idea what's different here from the way I was doing it in my applications, but at this point I'm not going to lose any more sleep!

Thanks for sticking with me and promptly replying to my notes!

 

I'll add a note when I've got it deployed

[tomp]

I integrated this into my applications and deployed them. Again, I have no idea what the issue was that caused this procedure to stop working, but the case is now closed!

Thanks again to 'Comment' for all the attention and help.

[comment]

 Ah, good. I wasn't really expecting this to succeed, but it was worth checking. Only goes to show that the old tried-and-true methods of troubleshooting are still valid.