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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Capacity and Scalability of DNNCapacity and Scalability of DNN
Previous
 
Next
New Post
8/24/2006 1:55 PM
 

pushed for time at the minute, sorry to bundle all these answers in 1 post

egyptegypt, I appreciate that you cannot donate your changes, that's absolutely fine. I was also not trying to suggest that you didn't bring problems to our attention, if you interpreted my words that way I apologise. However, I would ask that you submit any future issues/enhancement requests via the public issuetracker (http://support.dotnetnuke.com/Main.aspx), as forum posts tend to get lost/unread (there are 500+ posts here on some days, noone can keep up with them all)

Dave, thank you for the offer, I will raise it with the rest of the coreteam to see if it can be used (I know this was an area that was being looked at already, so efforts may already be underway). FYI: code submitted has to go through a process, please look at http://dotnetnuke.com/DotNetNukeProjects/tabid/824/Default.aspx ( look for "To avoid legal problems" ), to see if you are happy about the requirements. Note: these requirements really only apply to addition of chunks of code, code that fixes bugs does not require the signing of documents.

purplebox, you're absolutely right. The best way to get code into the core, is to provide a high quality submission, with as much detail as possible, and state your case well. The easier it is to evaluate/test/secure proposed code, and the more people with a requirement for that code, the faster it will be assessed for inclusion

Cathal

 


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
8/25/2006 3:44 PM
 
DBuckner wrote
 cathal wrote

(I only wish to use your comments to illustrate a point), but your comments are typical of ones I've heard many times ("It required extensive customization to get it to a useable state and it's still a work in progress. "), but we get surprisingly little of this feedback/customisation code from the community. Have you any information/code you wish to share, I'm sure we'de be interested in listening

Cathal,

I recently abstracted DotNetNuke.Services.Mail.SendMail into a provider based object. I would be happy to see this make it's way into the core. From my testing all my core and 3rd party modules are working untouched with the default provider I created.

I have been missing emails due to a issue with my host's mail server being down, so I created a second provider as well to handle queueing of mail. I am willing to give up the default CDO provider.

Question is, how can I contribute this back into the core?

Thanks,

Dave

Dave, could you forward me on the details/code to cathal.connolly@dotnetnuke.com. The forums team has already specc'ed out this requirement, but if your code is suitable they could use it. If this is the case, I'll coordinate the signing of the necessary forms.

Thanks,

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
9/6/2006 8:29 AM
 

Dave, I still haven't received your code - i've been on a break for a few days, so theres a small chance my spam filter caught it and had deleted it before I could retrieve it. If this is the case, can you please resend it.

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Capacity and Scalability of DNNCapacity and Scalability of DNN


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