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

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsLinksLinksTeam MemberTeam Member
Previous
 
Next
New Post
8/4/2006 10:42 AM
 
Anything that messes with the core would not be able to be put into a project module. As far as having these features in the links module, I do not believe this would be wanted as you can already do all of this with SkinObjects, therefore they can be placed where ever they need them. Your second idea is very intriguing though. I think links that appear for some roles but not others would be a neat idea.
 
New Post
8/9/2006 2:35 PM
 

I am just trying to think outside the box on this one a bit.

You are correct that you can add a logon link and a register link, and a profile link to the skin as a skin object, but you have to take those functionalities as they come.  IE, if you want a logon link, you also get a logoff link, same goes for register and profile.

What happens when you want to add an image next to the logon link?  or use an image as the logon link?  See where I am going with this?  I don't believe that functionality is built into the skin object.  Although I could be wrong.

Another thing you need to consider is that an option for the links component is to have it as a dropdown list.  From what I can tell the skin objects cannot add items to the dropdown list.

As far as editing the core framework, I have duplicated code thus far to make this happen until I can get this stuff built into the core framework.  That makes this code portable.  Albiet I have to make mods as they do to the areas of the core that get changed.

I have all of the items I have described finished.  They are being tested as I am writing this note.  I don't anticipate many fixes needing to be made at this point as there has been testing going on and we are winding down.

Thanks,

Keith

 
New Post
8/10/2006 10:04 AM
 
I know where you are coming from, but I would still say that this does not belong in this module. The reason behind this is the fact you are duplicating core functionality, waiting for it to be incorporated into the core. This would be great for a third party module, but not one that is part of the DNN project itself as it breaks standard practices. The chances that you will miss something as far as changes go, increases signifigantly when you duplicate core functionality. By all means, I do not mean to discourage you with this, but this is not a path I would like to put this module on.
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsLinksLinksTeam MemberTeam Member


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