But when I access the members tab in the back office, I'm just getting the spinning disc (in the tree bit). Any ideas? Or have I missed something glaringly obvious?
You need to set an application name for both the membership provider and role membership provider. My umbraco config file is the same format as yours but the parts where it says applicationName="/" I replaced "/" with the application name I'm using in the config file of the application I want to connect to. I can now view all the member and role details from my other app within Umbraco. I got the idea from this page
* actually I've only half cracked it as it crashes if I try and update member details. Also the ability to reset passwords has been lost. Looking into those things now....
Using External ASPNetMembership Provider v6.1.6
I'm trying to wire up the members on the site to use .Net Membership from another database. I've ammended my web.config as follows
But when I access the members tab in the back office, I'm just getting the spinning disc (in the tree bit). Any ideas? Or have I missed something glaringly obvious?
Hi Tony. Did you manage to resolve this ?
I'm just about to start trying to do the same thing ...
Sorry, no.
I've cracked it! *
You need to set an application name for both the membership provider and role membership provider. My umbraco config file is the same format as yours but the parts where it says applicationName="/" I replaced "/" with the application name I'm using in the config file of the application I want to connect to. I can now view all the member and role details from my other app within Umbraco. I got the idea from this page
http://weblogs.asp.net/scottgu/archive/2006/04/22/Always-set-the-_2200_applicationName_2200_-property-when-configuring-ASP.NET-2.0-Membership-and-other-Providers.aspx
* actually I've only half cracked it as it crashes if I try and update member details. Also the ability to reset passwords has been lost. Looking into those things now....
What I'm stuck on appears to be recognized as a known bug
http://issues.umbraco.org/issue/U4-2694
is working on a reply...