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 ExtensionsModulesModulesCustom tokensCustom tokens
Previous
 
Next
New Post
2/9/2011 9:17 AM
 
Thanks Robert, I have the book and am reading it. I have looked at MyTokens and support was quick and helpful and did suggest a solution which we will consider. I will read up and think about it when I understand it better. We also have a different issue that none of the email modules I've seen are designed for. What we need is something that queues up core DNN registration emails and pwd reminders and re-sends them. The problem is that DNN is very poor in sending out emails. If for example the SMTP server goes down there is nothing in the error log and the emails are not re-tried. They appear to have been sent but never arrive. So we get users complaining that they got no emails and we have no way of knowing what happened. So we have had to set up a trace. What we really need is a replacement for the core DNN email system. Something that logs everything and re-tries or queues up emails. We don't need a module to send out email compaigns which I think lokalerna is referring to. If anyone has any suggestions I'd like to hear them. Ideally we need a package that bolts onto DNN but doesn't break the core (so we can still upgrade) and uses a proper emailing engine that tells us what it's doing. Sadly I have found nothing that does this. Rachel.
 
New Post
8/11/2012 1:48 AM
 

I realize this thread is a bit older, but it's the closest I can find to what I'm trying to achieve.

What I am try to do is HTML Include anywhere on a DotNetNuke page.

It may sound a bit silly at first but after years of struggling with upgrades of 3rd party modules, I am trying to reduce my dependence on them.

In my sample case lets say I have a site with 10 products on 10 different pages. On each product page I have a text/html module that contains some nice, simple CSS tabs. One of those tabs is a Warranty tab. Since my warranty would be the same for all 10 products, I would like to maintain it in one place. Ideally I could define an HTML file somewhere and simply reference it via a token. Then inside the html module in the correct section for the warranty tab I would place this token and DNN would fill in the HTML.

Ths seems alot more intelligent to me than exporting the warranty and importing it 10 different times on 10 different pages!

I realize that 3rd party ,modules exist that allow each tab to contain a module, but I am not interested in 3rd party modules.

Surely there is some way to make a custom token or inject some simple HTML in a reusable / maintainable manner inside a module?

Any guidance is much appreciated. I think I've exhausted my googling options and I'm not any smarter than when I started.

If there is no such capability, what is the feasibility of writting one without patching the core (a big mistake imho). I can envision a list of custom tokens inside the text/html and a little html editor that lets you make and save these little snippets for easy reuse.

 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesCustom tokensCustom tokens


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