AjaxControlToolkit version

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

Please do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.

This forum is for discussing mojoPortal development

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

You can monitor commits to the repository from this page. We also recommend developers to subscribe to email notifications in the developer forum as occasionally important things are announced.

Before posting questions here you might want to review the developer documentation.

Do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.
This thread is closed to new posts. You must sign in to post in the forums.
2/21/2010 8:25:03 AM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: AjaxControlToolkit version

Hi Ian,

Sorry to have tell you this, but I had to revert back to the older version of AjaxControl toolkit because the new version created a bug in my Form Wizard Pro product due to a bug in the ReorderList control in the newer versions of AjaxControlToolkit. I found it is a known bug but it is not fixed.

http://www.codeplex.com/AjaxControlToolkit/WorkItem/View.aspx?WorkItemId=17574

I will have to revisit this later.

Best,

Joe

2/27/2010 9:15:33 AM
Ian Rogerson
Gravatar
Total Posts 60
View Posts

Re: AjaxControlToolkit version

Ah - OK - fair enough - thanks for letting me know.  Hopefully they'll sort out the reorderlist bug soon.

In fact I've discovered that as part of my fiddlings I'd commented-out the SiteUtils.SetupEditor(edDescription);  line and this was causing the errors. 

Re-instating it has fixed my immediate problem, although the new Ajax bits would still be useful at some point!

All the best,

Ian

You must sign in to post in the forums. This thread is closed to new posts.