http://our.umbraco.org/forum/developers/extending-umbraco/3930-Axendo-ultimate-picker looks similar

Is this solved in v1.0?

/Jesper

I don't know what is causing this to happen.
On the websites where I used this datatype I've never had a ScriptManager error.

The datatype is exactly the same as the ultimatepicker so I can't think of a reason that explains it. nor can I reproduce the error.

Ron

Hi Ron,

It works fine. I cant reproduce either. Great addition that gives super flexibility. Another thing I found. Validation does not work when rendering dropdown. I havent tried the other. It seems that the value is never valid.

Thanks

Jesper

I'm getting the same error now:

The control with ID '{property alias}' requires a ScriptManager on the page. The ScriptManager must appear before any controls that need it.

This is on an existing Umbraco v4 install.  I literally switched the doc-type from Ultimate Picker to Axendo Ultimate Picker XPath.

Any ideas?

Could it be if I am using other Ultimate Picker data-types in the same doc-type?

Should I try switching all data-types from the old Ultimate Picker to Axendo Ultimate Picker XPath?

I'm getting the missing ScriptManager error too. I'm using V4.0.3, has anyone got a solution?

I ended up recompiling the source-code against .NET 2.0 with AJAX.NET 1.0 Extensions, and it worked fine for that install.  I haven't had the same issue with it since, but most of my Umbraco installs have been .NET 3.5 / IIS7 recently.

is working on a reply...