Error on saving in Page Display

Submitted by kidder on Tue, 05/07/2013 - 10:00
Hello

I've imported a Webmaker 3.1.2 project into Webmaker 5. I'm having a problem after inserting a pop-up dialogue onto a partial page. I was unable to save the changes ("Unable to save details, please try again."), but wasn't able to identify any problems. I removed the pop-up, but was still unable to save the form (though the changes were actually saved which makes me wonder if there is a generation error somewhere). Oddly enough, if I close the Page Details tab, I am able to successfully save from the Application Map tab. Any ideas as to how to find the problem?

Hi There

Do you see any script errors when it fails to save?

You can try using the Verify and Save Application action, located under Advanced Options on the left hand panel within the Application Map tab. This might provide a few more clues.

Regards
Abdul

Hello

I've just used this - the project seems fine here ("Page and controller generation completed successfully").

Is there any way to see what the save is doing on the page, as there are no script errors either?


Hi There

Do you see any script errors when it fails to save?

You can try using the Verify and Save Application action, located under Advanced Options on the left hand panel within the Application Map tab. This might provide a few more clues.

Regards
Abdul

[hr][/hr]
I've been looking at the page again. Now, when I click on the bindings tab, there is an error being generated (there definaitely wasn't prior to putting the pop-up on there). Error is below:

Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E; InfoPath.3)
Timestamp: Tue, 7 May 2013 09:37:06 UTC


Message: 'DB.window' is null or not an object
Line: 4581
Char: 29
Code: 0
URI: http://localhost:7070/formmaker/js/formStructureScripts.js?v=5-0-WM_HSG_5-0-0-0001

Sounds like an issue with the way the bindings have been generated maybe. If possible, try removing the control that caused the issue and see if your save operation works. You can also try restarting the studio, just in case the window manager has lost track of one of the frames.

I've also sent you a PM.

Abdul.
[hr][/hr]
Okay, just realised you don't have PM enabled. Depending on the size and sensitivity of your project, we'd be happy to have a look at it for you.

Hi Abdul - I didn't realise that I'd set the settings to no PM's; I've changed it now.

I checked the bindings xml for that page, but noticed no problems. I did note that I couldn't save in any page details tabs anymore, so I assumed it was more basic than a problem with the page. I logged out of WM and went back in and the problem persisted.

Having previously said that there were no script errors, I used the IE Developer tools and noticed an error being generated (but not shown on screen/in the status bar...) when going into a page in xpathBindingScripts.js. Opening this in Visual Studio there was an error highlighted on line 15. There seemed to be an extra comma in the var bindingInstructions - removing this comma, saving the file and then restarting Webmaker has resolved the problem. I don't know if this actually is the cause or not, or whether closing WM again cleared something, but at present the problem is cleared.

Thanks for your help.


Sounds like an issue with the way the bindings have been generated maybe. If possible, try removing the control that caused the issue and see if your save operation works. You can also try restarting the studio, just in case the window manager has lost track of one of the frames.

I've also sent you a PM.

Abdul.
[hr][/hr]
Okay, just realised you don't have PM enabled. Depending on the size and sensitivity of your project, we'd be happy to have a look at it for you.

That's great. It would be good to learn whether the XPath was the default generation for this control or whether it's one that you modified. If possible, let us know the XPath or similar variation to enable us to investigate further.

Kind Regards
Abdul
[hr][/hr]
Okay, I had assumed the extra comma in the generated page files. xpathBindingScripts.js is common, therefore an error. You did mention it was working initially and then it stopped working. Were you using different browsers? Also, did you switch IE between compatibility modes? I guess this error was ignored by one of the browsers or browser modes.

Abdul.

Sorry for the delay in replying Abdul. FYI, I was using my own bindings for the controls in IE8 (generally in Compatability mode).


That's great. It would be good to learn whether the XPath was the default generation for this control or whether it's one that you modified. If possible, let us know the XPath or similar variation to enable us to investigate further.

Kind Regards
Abdul
[hr][/hr]
Okay, I had assumed the extra comma in the generated page files. xpathBindingScripts.js is common, therefore an error. You did mention it was working initially and then it stopped working. Were you using different browsers? Also, did you switch IE between compatibility modes? I guess this error was ignored by one of the browsers or browser modes.

Abdul.

We use cookies and analytics on our website to support technical features that enhance your user experience.

-