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

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsSkinsSkinsLink to current user's account pageLink to current user's account page
Previous
 
Next
New Post
6/11/2013 11:42 AM
 

I wish to include a link to the current user's account page in my skin.

I guess it'll be something like PortalSettings.UserInfo.Profile.MyAccountURL or PortalSettings.UserInfo.MyAccountURL but that's a wild guess (I've found PortalSettings.UserInfo.Profile.PhotoUrl and PortalSettings.UserInfo.DisplayName)

I often find myself searching for the next these properties and searching for them each time gives me the one I'm looking for (although I haven't been able to find the account page link), howevers, that's just one at a time.

Is there an overview somewhere which porperties exist?

 
New Post
6/11/2013 12:31 PM
 
A google search found this:
http://www.dotnetnukeru.com/dnndocs/a...
 
New Post
6/12/2013 4:22 AM
 

Great find, thanks!

I found something similar (the fact that there are differences is somewhat worrying) via:

http://www.dotnetnuke.com/Resources/Downloads.aspx => API documentation (bottom of the page) => Core API Help File (under Other available downloads, be sure to have javascript enabled and allow scripts from all domains), download the zip-file, unzip it (it won't open properly directly from a compressed folder!) and open it with the microsoft HTML Help Executable.

(yes, it is available... in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying 'Beware of the Leopard'. ;) )

I guess the first thing I needed to do was realize I needed the API documentation :) I didn't consider creating a skin "application programming".

Both documents seem very similar in graphic design and document structure, but there are many differences in content. e.g. given the first 4 namespaces (in alphabetical order) both contain the DotNetNuke.Application and DotNetNuke.Common namespaces, but the website contains DotNetNuke.Authentication.LiveID and DotNetNuke.Authentication.OpenID namespaces which the helpfile does not, while the helpfile contains DotNetNuke.Collections and DotNetNuke.Collections.Internal namespaces, which the website does not.

Both document lack a document title and introduction, so it's unclear to me what the intended purpose or target audience of each is.

 
New Post
6/12/2013 6:00 AM
 
Wow. this api list ( I refuse to call a bare list of properties and methods "documentation") raises even more questions than it answers.

I've found in the API that the user's email is stored in UserInfo.Email of DotNetNuke.Entities.Users, but how was I to know that PortalSettings.UserInfo is the current user?
Is there a blogpost or something describing the most common thing you'd want to know?

Both UserInfo.FirstName and Userinfo.Profile.Firstname exist, what is the difference? should I always get/set both or is one og them deprecated?
Am I correct in thinking that UserInfo is the base table with all frequently used fields (and maps 1-on-1 to a database table) and Userinfo.Profile are 'extended' properties which might map to a more flexible storage which allows for adding properties without changing the database schema?

And I've still not been able to find how I can get the link to the current users profile page. Should I retreive the current user's id, find out (somehow) what the tab-id of the profile page is and construct the url myself using NavigateUrl()?

I guess I should navigate to a page containning the viewprofile module supplying the parameters the view profile module on that page requires. But what are they?

The (autogenerated) API description of the NavigateUrl method isn't helpfull at all either. I don't know if that is the right approach, I don't know how to get most of the 5 parameters it accepts, and what the AdditionalParameters (=array of strings) can/should contain is a complete mystery.


Or, can/should I just hardlink to /ActivityFeed (which contains the "my account" link I am looking for) and let the user find it's way from there?
 
New Post
6/13/2013 10:32 AM
 
I need someone much more knowledgeable than me to answer this, Roland.
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsSkinsSkinsLink to current user's account pageLink to current user's account page


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