Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...WebForm_PostBackOptions is undefinedWebForm_PostBackOptions is undefined
Previous
 
Next
New Post
4/4/2006 12:28 AM
 
No doubt that this is a problem that many people are enduring.  The exact same problem happens on both of my DNN installs.  I'm not really ready to go live with this until I can get something resolved. 
 
New Post
4/5/2006 12:14 AM
 
We are having this problem on a DNN 1.0.10 site on a windows 2003 64 bit server.  Anyone have any suggestions to try?
 
New Post
4/5/2006 11:42 AM
 

I just logged an issue with DotNetNuke about this.  There were already 2 issues logged already about this bug, but I figured since those issues have been ignored since February, I'd log another.

Seems the core team doesn't consider this a priority, even though it renders child portals utterly useless.

 
New Post
4/27/2006 5:04 PM
 
  • deleted all users (save host) from Users and aspnet_Users tables (you will have to delete related rows from _Profile and _Membership as well)
  • re-added users to parent portal through DNN client

solved issue.

This was reasonalbe for us (as a quick-fix, mind you) as we use AD synchronization ... after creating users in the parent portal, the subsequent child portals the individuals accessed prior had their account auto-created for us the first time they would log in again.  This was also a reasonable work-around for us as, since we've only just started using DNN as an external site (great first impression! ) we only have a dozen or so users ATM.

I'm hoping there is a variation to this fix that doesn't involve ransacking the users tables so badly.  Maybe simply ensuring that users exist in the parent portal when they already exist in a child?  While I believe this causes an error since the user already exists in the User table, again, perhaps a fix to *this* could help someone who wasn't as "lucky" as us to have so few users.

Hope this helps

 
New Post
5/3/2006 2:56 PM
 
I am not so lucky to do the user trick. Does anyone have a solid solution yet? In my case it is not a child portal.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...WebForm_PostBackOptions is undefinedWebForm_PostBackOptions is undefined


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out