If you want to use the DNN profile, make sure that the User Profile Page is set to User Profile. The Registration page should be set to the new page you created with Dynamic Registration on it.

As far as AS settings are concerned, just make sure that any components you are not using are set as -Disabled- in the Define Social Pages section of the Settings page in the control panel.

Hi Ben,

This is precisely the problem. Disabled is not set and when checking the control panel after exiting it first I discovered that all social pages, except the members list page. All other pages were set to the page on which I had installed the messaging component.

The workaround, I already deployed, is to install the Active Social Profile View and have the Profile View/Group List & Group View all set to the page on which the Profile View was deployed. The page containing the registration module has been set in the website settings for the registration & user profile page.

I can live with this solution as a workaround but shouldn't the control panel respect the Disabled setting?

Thanks in advance.

The Control Panel should allow you to set the pages to disabled, but I have confirmed that it is not saving correctly.

I am not sure why this would matter though. As long as the settings in your Admin Site Settings are correct, the links at the top of the skin should work as follows:

Register > DNN Registration page (Site Settings Registration page set to None Specified)
Username while logged in > DNN User Profile Page (Site Settings User Profile Page set to User Profile)

Perhaps I am not understanding the problem you are having.

Ben,

Scenario:
AS Messaging component installed;
Seperate Login page (DNN Default)
Separate Registration (DNN Default)
Site Settings:
- Login page set to page described above;
- Registration Page set to page described above;
- User page set the same as registration page.

You already noticed that the settings were not saved properly in the control panel and as a result the profile view, group list & group view pages are all set to the page that contains the AS messaging component.

When I log in as a regular user I get the following url when hovering my display name: http://www.domain.com/home/asuid/number.aspx and when I click on the link I am actually brought to that page but it is just the home page. In this setup there is no way that I can enter my profile to adjust my profile settings.

Please keep in mind that I already have this solved by adding the AS profile view to the portal and after that I am brought to the Active Social profile view. I hope this is a better description of the situation.

Try setting your Site Settings like I described:

Site Settings:
- Login page set to
- Registration Page set to
- User page set to User Profile (the default DNN User Profile page, this has nothing to do with AS)

Ben,

I assume that you mean that I need to set the login/registration page to "None specified". I have done this and changed the user profile page back into the DNN default page as you suggested.

The following happens when I login as a regular user and:
- click on the login I go the default DNN login page (tabid36);
- click on the registraton page I am brought to the Home page, not the registration page. The registration page is now only accessible when I click on the Login page and use the register link from that page, as presented by the account control module. When I hove the registration link in my skin the url for the user profile page is shown.
- click on the display name I am brought to the url http://www.domain.com/home/asuid/number.aspx but no profile that I can edit is shown.

Update:

I have selected the default DNN skin to determin whether that would be the cause and it is. I am using the Catalyst2 skin with the Active Social adjustments and it appears that this is somehow causing this behavior. I'll get in touch with James and inform him about this. I'll keep you all posted.

Thanks for your patience & support.

Update:
Running the default Catalyst2 skin is not giving any issues at all. It is all coming from the adjustments that are related to showing the inbox & alerts in the breadcrumb of the skin.

I'll keep you posted.

That makes sense. If the links were changed to point to AS specific locations, then they probably were not using the Site Settings to determine the User Page.