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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Connecting DNN to a large event databaseConnecting DNN to a large event database
Previous
 
Next
New Post
7/23/2007 10:11 AM
 

That, currently, would need to be a customization for your site if you need to extend portal attributes. You could do it either by developing a custom module to do so, or you could modify the core code to do so. The recommended means would be to develop a module that does this for you.


Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
7/23/2007 11:01 AM
 

Hello, and thank you for your replies! :)

Making some sort of attribute module could work - it could store whichever attributes I needed along with a portal ID in a table. I do not know if there is an easy way to automatically create a module instance upon the creation of a portal, but I guess there is and I could look into it.

Also, at the local level, since some festivals are joint arrangements for usually two or three municipalities, joint festivals should have only one portal each, while a list of local municipalities for any region should have a link for each municipality. The database we have supports this, but it shows that there is an added level of complexity here. Also, there is a problem in that some of these joint festivals probably will split, some new will be formed, and whole local municipalities might be merged. Fixes for this should be possible while retaining the old portal in some way.

Portal creation would probably be done ad hoc with a script before the site is made public.

 

 
New Post
7/23/2007 11:08 AM
 

Going through the settings for my dummy DNN site I can find no way to hide the portal (perhaps the expiry date under host settings could do this, but that would not be very intuitive) - is it possible to make functionality for this without altering the core?

 
New Post
7/23/2007 11:17 AM
 

Why do you want to "hide" a portal? Would deleting it be an option?


Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
7/23/2007 11:52 AM
 

I am unsure if we really need it. Today the manager wants to be flexible and have the ability to hide the "festival newspaper" of coming festivals when no content has been created yet. Today old newspapers are are always parked at the end of a festival season, so this is logically achievable today.

However, by merging the festival newspaper with the information site as we are thinking about doing - hiding the festival newspaper would also hide the information site AND all earlier newspaper pages. Therefore we probably would not be able to use this, and you assumption was correct;)

This highlights a challenge in information organization. It should be possible to park away last years content and make it easily accessible under sound categories. I will have to look into this.

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Connecting DNN to a large event databaseConnecting DNN to a large event database


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