[SOLVED] Export XML generates bad file

[Bigge]

I´m developing the Dewplayer module and all is working if I install it from zip-file, but when I try to export a XML-file I get a file that gives errors at import: "Error parsing XML file..."
I have tried export from both my local WAMP and from a server based LAMP
What can I do to create a functional XML-file

Using CMSMS 1.5.4
(adding zip-file, just change txt to zip)

[NaN]

I have the same problem with my FEUMailer.
I already got bug reports that my XML file is broken.
I also exported from cmsms 1.5.4.
Will try an older version cause the last XML file i exported worked fine.

By the way does anyone know why the ModuleManager does not show the latest XML file to install?
It still shows a deprecated version of my module.
The funny thing is: there actually is no XML file of that version in the forge.

[Bigge]

I also have tried to export the file from CMSMS 1.2.4, same error on import.

[NaN]

Maybe just the IMPORT function of the latest CMSms release has changed?

[Ted]

It's probably a weird line endings issue.  Using a decent text editor (Notepad++, Textpad), do a save as and set Unix line endings.  See if it helps.  If not, try one of the other choices.

The 3 main issues I've found with using XML as a data format are:

1. Line endings are finicky
2. Encodings that aren't UTF-8 make for a nightmare
3. They're SO big

It's one of my goals down the road to get module packaging into a different format -- whatever that may be.

[NaN]

It's probably a weird line endings issue.  Using a decent text editor (Notepad++, Textpad), do a save as and set Unix line endings.  See if it helps.

Ah, good to know that.
Thanks.
This solved my problem.
(I used jEdit)

But in ModuleManager still shows up an XML file that I deleted from forge.
Actually there are no XML files available of my module but there still the XML file of the old (buggy) version 0.8 is shown.
Can anyone check if the XML files are really deleted or if there has been just removed some database entrys of the forge?

It is not that major thing to me to provide the module as XML file.
I always prefere the zip-files (since installing from XML files often causes weird file permission stuff).
But many people uses the ModuleManager or don't have FTP access.

Off topic:
how can i remove a release in forge? i can only edit them and add or remove files. but the releases still remains even if i deleted all files of that release.

[Ted]

But in ModuleManager still shows up an XML file that I deleted from forge.
Actually there are no XML files available of my module but there still the XML file of the old (buggy) version 0.8 is shown.
Can anyone check if the XML files are really deleted or if there has been just removed some database entrys of the forge?

Just found a bug in the module sync script.  It should correct itself by tomorrow.

how can i remove a release in forge? i can only edit them and add or remove files. but the releases still remains even if i deleted all files of that release.

I have no way to doing that yet.  There will probably be a way to inactivate a release, but not fully delete it.  It just makes a mess because of all the data associated with a release.

[Bigge]

It's probably a weird line endings issue.  Using a decent text editor (Notepad++, Textpad), do a save as and set Unix line endings.  See if it helps.  If not, try one of the other choices.

The 3 main issues I've found with using XML as a data format are:

1. Line endings are finicky
2. Encodings that aren't UTF-8 make for a nightmare
3. They're SO big

It's one of my goals down the road to get module packaging into a different format -- whatever that may be.

Thanks! I finally made it by using Linux and install CMSMS (and database) with UTF-8 instead of iso-8859-1. I think UTF-8 in the database was the final solution for me (I already had unix Line Feeds).
DewPlayer is updated