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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Help needed updating content...Help needed updating content...
Previous
 
Next
New Post
2/1/2006 2:37 PM
 
I am trying to determine the best way to handle updating content on my DNN site, which will be a ciontent heavy site.  I need to update content on the site at least twice a week .  The main  issue is being able to update an existing page (that is viewable to the public) without the changes being seen by the public until all changes are done

The other issue is being able to copy a page and then make changes to the page without all the changes effecting the original page (the page that was copied)

Any suggestions on these problems?.


 
New Post
2/2/2006 12:03 PM
 
  1. What are the changes you need to make twice a week? Are they typical things that you can programmatically determine? If so, you can create a scheduled task within SQL Server to do these. You just need to make sure you write your T/SQL appropriately to take care of any exceptions that may come up during the update process and rollback, if necessary.

  2. Currently, you have two options for copying content. First off, you can create a new page and tell it to copy the modules from another page. This will not copy content. If you tell it to copy content, then it will use the same module instanes as are on the first page, which - as I'm sure you've figured out - means that changing one will change both. You might be able to solve this if all modules that were used on the copied page implement IPortable (import/export capabilities). If they do, then you can export each module individually from the copied page and import it into the new page. The only other way to do it would be to export the site as a whole to XML, strip the stuff you don't want, and import only the content you want to copy. If you're not familiar with XML or the import/export capability, then this could be a big undertaking.

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com
 
New Post
2/19/2006 5:56 PM
 

Does this mean that if I have say three sites ( on different servers) using DotNetNuke, and I want the same Text/HTML page on each one, I must manually create the page three times?

There is no way to copy content from one site to another?

 

 
New Post
2/21/2006 10:01 AM
 
You can use site or module import/export features to more easily update content. You'll still have to put it into one module to do the export - unless you want to write the XML manually, which isn't hard. You do have some options, tho

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com
 
New Post
2/21/2006 10:31 AM
 
We currently have a module that allow HTML/Text content to be shared across portals within the same DNN instance without the need to copy & past or import/export.  However if your portals reside on separate DNN instances then you'll resort to using the module import/export features.

Enterprise Forms for DotNetNuke

Version Control, Forms and Workflow Suite

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Help needed updating content...Help needed updating content...


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