Hello Lee and Joe,

Thank you for helping me with this issue I have resolved it finally this morning but need some advice from you guys. Apparently the answer was unticking the enable ajax undder the host>site setting>other settings. This cleared up all errors I was receiving and haven't seen that duplicate ID error pop up since. I also will note that under the asp.net forum it appears this duplicate id is indeed an ajax issue.

What I need to know from you guys is what kinds of consequences could I expect to have as a result of turning of the ajax support for my site. I was sure that my video module used ajax for its overlays but after turning the feature off I noted overlays were still occuring like usual.

Do you kow of any default modules that come with dotnetnuke that support ajax or should I say use it (i.e. text/html, event, iframe, user accounts, etc...) I haven't seen any problems in the short run but I guess I need to know if I can expect some problems as a result of this move and if those problems would be minor in comparison to the crippling of my site that this other error has caused.

So if you guys could give me some guidance on what kinds of things would use ajax or what ajax would be used for in a dotnetnuke site that would be extremely helpful so I can get an idea if the benefits of disabling ajax outweigh the reprocussions of disabling it or if disabling ajax could cause some major issue in terms of certain areas of a site.

What would be a good way to test to see what kinds of issues could stem from this move? Thank you so much for your help I think I may post a message on the dotnetnuke support forum concerning this and find out what they are doing to come up with a resolution for this problem with ajax as it relates to the newer dnn versions.

Do you recall if ajax was enabled or was even an option in dnn versions before 4.7?

Joe in the 4.7 and 4.8 installations you did do you recall if the enable ajax check box was ticked by default and if you enabled ajax for your 4.7 and 4.8 installations with no problems.

I did what you suggested concerning the partial rendering thing and noticed only one module had that item ticked that was user accounts in which I unticked it but that did nto solve the issue but disabling ajax did.

As far as I am concerned that is better news to me than having to go the disable cache route and lose performance unless of course I learn down the road that this disabling ajax was a bad choice. Oh well enough said on this subject hopefully all of you reading this discussion will think before going to the enxt level of dnn and realizing that like me you may have to disable ajax unless you wait for a fix from dotnetnuke in which case you may want to find out if their fix addresses the ajax conflict issue in regards to these id clashes. Ok take care now.

Cheers,

Bo

Since you were upgrading, I think that turning off AJAX probably isn't going to do anything. If you've upgraded some modules, they might benefit from using AJAX, but you don't have to.

I think that AJAX didn't exist in DotNetNuke prior to 4.7.

My 4.8 installation has AJAX enabled, but this site is being built from scratch starting with 4.8. My 4.7 site was upgraded from a earlier version. I do have AJAX enabled there, but haven't run into the problem that you've had. It's probably specific to a module.

Disabling AJAX isn't going to do anything except disable AJAX features. Give it some time and you can try to turn it back on after this issue has been resolved. It might be useful if you'd go to Gemini and leave a note that turning AJAX off solved the problem for you.

Yes Joe,

I did leave a message for the dotnetnuke community in the Gemini site under the discussion about this error. Last I looked 7 votes concerning the problem so ell it is classified as a major bug seems like you not a lot of people have hit the issue. Actually I can't say I have actually noticed this issue creep up on the localhost installation which is a carbon copy of the production server where it was being seen all the time until shutting down ajax support.

It's also good to know that this ajax stuff was just recently supported via dnn starting wtih 4.7 which means since I upgraded from 4.5.1 I shouldn't run into any isses as a result. thanks again for all your help and hope this was as informative to you all out their on this site as it was to me.

Keep up the good work Lee and Joe this dnn creative magazine is a life saver when you are new to dotnetnuke and I am sure it is as well if you are old to it as it is very very informative for certain especially all those viedo tutorials such as the web development toolbar I'll tell ya what I time saver that has turned out to be if anyone hasn't downloaded Lees videos on it it is awesome

Bo

hello,

Glad to hear you find the site useful, if you come across any further information on this issue let us know,

Thanks,

Check out this post on DNN Forum:

http://www.dotnetnuke.com/Community...fault.aspx

It seemed to solve the problem.

Mark Luffredhttp://www.dnncreative.com/Forum/ta...fault.aspx">

Thanks Markandrew21 for this report.

Yes it is true according to the following website: http://support.dotnetnuke.com/issue...2&PROJID=2

You will note that the fix comes with an upgrade to version 4.8.2. I am not sure I will upgrade at this time as disabling ajax fixed the issue for me and as of now I don't have
any need for ajax support but when the time comes that I do I guess I will need to upgrade. Apparently the risk level is none so that is good. So their you are Lee you can safely upgrade your DNN now to 4.8.2 and be assured (at least hopefully) that at least the multiple id issue won't be an isue though who knows what other bug may replace it, LOL

Bo

Thanks for the note, Bo. If and when you upgrade, please drop us a note and let us know if this is working for you. My own personal thoughts are that you should wait for a couple of weeks after any upgrade is released to see what other early adopters report!

yes, thanks for the info, I am going through the upgrade process at the moment, so if anyone has experiences with 4.8.2 let us know - cheers,