Is there a Product XML DTD, Schema, or guidelines document?

[ckbcowboy]

Dismounted, I will try debug mode, and see if that helps. Thanks!

Opserty: the reason I want to edit my XML files manually is that I already use svn for version control, and I prefer to keep track of revisions to all of my files there, whether they are going to be imported into vBulletin or not (this minor vBulletin mod is just one of my projects).

vBulletin seems to lack the ability to export a product XML file to a path on the webserver, and I find the export-download/import-upload process rather cumbersome.

Besides, I've already looked at the source of the vBulletin .php files to see exactly how the hooks system works, and how I need to code my product. It's only a natural next step for me to understand how the product XML format works. Documentation on that XML format would definitely be helpful.. but if I can make the changes in debug mode, and then export my product to an .xml file, I should be able to analyze those results and learn more.

- Cowboy

[Adrian Schneider]

Cowboy,

What I have done in the past is created a tool that creates all product data as separate files, so each phrase, template, plugin, etc. is a file that is controlled through SVN. The system would also read and save these files to the DB at runtime on my development server. This avoids the need for XML for but exporting to production servers.

At first we used XML, but it was such a major PITA I came up with another solution for my team.

Really, this is something Jelsoft needs to address if they want to encourage any serious development from the community.