Configuration:Shared:Spry:DesignTime:EditingUtils.js Error

I have completed my back-end pages for a project and applying restricted access to these pages using SecurityAssist. The process was largely successful excepting for two pages.

Two specific errors were displayed, then page in question would be opened and the whole process would be stopped. When I initially had a group of pages selected in the access pages manager, no further pages after the error page would be applied and the whole process would be frozen.

I'm using a MacPro and Dreamweaver CS6.

The two pages are attached as well as the two error messages that pop-up.

No idea how to resolve the issue.

What extensions including the version numbers are installed?

The extensions that are compatible with Dreamweaver CS^ and the latest versions are:
eCart 5.0.7
Free Tools 1.0.5
Design Extender 1.1.5
Data Bridge 1.1.4

I recommend installing them in the order listed above.

If you have an older version of one of the extensions installed, you should uninstall it before installing the newer one.

Thanks Jason,

The extentions I have installed are:
eCart 5.0.7
Design Extender 1.1.5
Data Bridge 1.1.4

I originally installed them in the same sequence as above on a clean installation of Mountain Lion.

Any further advive please

both of those pages have rather long forms on them, so that is probably the cause of the first error, it's just taking a while to inspect them form when the page opens.

does the Access Manager work for other pages? It only errors on these 2?

Can you try adding the Restrict Access Server behavior to those two pages rather then using the access manager.

open each of them and go to the server behaviors panel, click the plus button and select webassist -> Security Assist -> Secure Page.

The Access Manager works perfectly for all other pages.

The insert and update pages is where the errors occur.

When opening each of the above 2 pages to add the Restrict Access Server behaviour, I get the same first error as before. Eventually the page does display. When I add the Restrict Access Server behaviour, the same error occurs again, but after a couple of seconds the restrict access code is placed in the head region. When testing the page, access to the page is restricted and redirects to my login failed page.

To test, I completely shut down Dreamweaver, re-opened and opened each of the referred to pages again. The first error appears again.

Fortunately, the pages are working fine.

Thank you Jason for the advice.

Yeah, the first error is just because the forms on these pages is rather long and causing Dreamweaver to take a while to inspect.

glad to hear that adding the restriction manually worked.

Much appreciated Jason