The dreaded Error Initializing UI...

I think this may be akin to blue screen of death. Anyway, I after doing lots of work on my form, I was in the Edit Form mode when editing something rather small. I clicked Finish and got an error part of the way through FB saving the code. The error showed up as a DW error (see the attached file). Once this occurred, anytime I attempted to use Edit Form and clicked the edit icon, it would attempt to start but then I'd see the Error Initializing UI, Type Error: groupObj has no properties.

I got a prompt to show the errors and I took a snapshot so you can see them.

I tried deleting the WinDat cache file, uninstalling the extension, then reinstalling it, then firing up DW again and when trying to edit the form, I get the same error. I can click on Edit Design and make a small change and save everything and that works fine. The problem is when I go to Edit the form. Note that I'm using a preset I created that was working fine until all of a sudden it stopped.

I tried creating a new file and using the same preset. After the form was inserted I clicked on edit form and it showed the contents of the form just fine. Then when I clicked Finish, the same error message popped up about a spry widget no longer being present and might not work OK. It seems to have something to do with this:

var Security_info_group_Security_code_Spry = new Spry.Widget.ValidationTextField("Security_info_group_Security_code_Spry", "none",{validateOn:["blur"]});
var Security_info_group_nbsp_Spry = new Spry.Widget.ValidationTextField("Security_info_group_nbsp_Spry", "none",{validateOn:["blur"]});

These are the last two lines of var definitions at the end of the javascript at the end of the page.

Any idea what's causing this? Am I going to have to build my form from scratch to get around this? anything I could edit on my own to fix the problem with the preset?

Note that if I don't use this preset that must have become corrupted somehow, and use a standard FB form type such as simple registration, I can use the Edit form mode just fine without causing the above problems.

steve

It appears there are some orphaned spry elements on the page, clicking OK to the alert will remove the problem code.

If you export your preset and attach it to your reply, i can try to recreate the problem and see what the cause is.

I had completely cleared everything out of the page including all the javascript at the end of the file when the code got reinserted. I gave up and rebuilt the preset from scratch so I won't be able to send you the errant preset. maybe next time (hopefully not).

out of curiosity, is it in the preset's xml file where these orphaned spry elements were being placed in the page or somewhere else?

thanks for your help,

steve

Yes, it would have been in the XML file.

When this error first happened and I posted the results, I had seen an alert box come up before the problem manifested itself. I saw this same alert box come up again last night but instead of clicking OK on the alert and then clicking Finish, I decided to cancel all the work I had done so I wouldn't have the problem repeated that was associated with this original post.

The alert that I saw before the problem I described in this original post is shown in the attachment.


Any idea of what may have caused this?


steve

honestly, I'm not sure what would have caused the error.

I am starting a ticket so we can look into the issue with you to find the cause. To view and edit your ticket, log into your support history:
supporthistory.php