Bug in Debug Mode

Easy steps:

1. Export your title to XML.

2. Look in the export folder -- there are two new files, yourtitle.xml and lectora.dtd.

3. Go to http://www.w3schools.com/xml/xml_validator.asp and validate your XML against DTD (all instructions are there), it can take long time for large files or you might need to find another XML validator online.

4. See what it says. It might find a forbidden tag or forbidden value on a tag or something.

In-depth:

An XML format does not restrict use of any tags as long as they are formatted correctly. E.g. an XML can contain tags , or and it'll be a correct XML. So if you want to check whether an XML corresponds to a certain purpose (e.g. being a Lectora project), you need a list of correct tags and other conventions. The lectora.dtd file basically explains what XML tags are allowed, what attributes are allowed on each tag and so on.

Let me know how it went.

Got this message from support for anyone who's interested:

This is a known issue in Lectora v11. This should be corrected in the first service pack for v11. It is expected to be released some time this month. We apologize for the inconvenience and if you experience any additional issues, certainly let us know.

Thanks for the info ssneg! Do you have any tips on what to look for to identify the broken variable? I'm scanning through the variable data in the awt and am not finding anything that sticks out.

I know that one. Happenned to me when I used mute/unmute action, which resulted in a broken variable being added to the title. I cut it out with notepad and everything went back to normal. You have to validate your AWT against Trivantis DTD schema to see what went wrong and fix it. Nothing should be lost.

Alternatively, if your problem is exactly the same as my problem, you can skip the identification process and try your luck by searching for the TriMuteAllFLV variable in your title and remove it completely (backup your title first!!!)

So open your .awt in e.g. Notepad++ and look for trimuteallflv. This is your improper variable, go ahead and delete the whole piece of code (nothing more, nothing less), that looks (almost) like this:

TriMuteAllFLV

0

1

[/CODE]

P.S. It's late night in Europe, so I'll check back tomorrow.[CODE]

TriMuteAllFLV

0

1

[/CODE]

P.S. It's late night in Europe, so I'll check back tomorrow.

Thanks for all the help! I was able to run the code through and it found a couple errors, though nothing that was related to variables... I ended up creating a new title and copying over what was already developed (luckily I wasn't too far in development) and the new title hasn't given the same error yet. Still baffled about what causes Lectora to do this, but at least I can proceed with the course!