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 ...Child to Parent portal?Child to Parent portal?
Previous
 
Next
New Post
3/1/2008 4:30 AM
 

I decided to simply create the /test folder beneath the new domain.com and copy the folders Portals and Providers and place then beneath /test.  This avoids having to use Engage F3 and is a very fast solution.

I've tested uploading images, adding to pages etc and all seems OK..

However, are there any hidden drawbacks?

Lea

 
New Post
3/1/2008 5:07 AM
 

hmm I'm a little confused as to what's happening.

The procedure for adding an image in the Text/HTML module is simply:

  1. Click the insert Image toolbar button,
  2. Click the Browse Server button - this opens the FCK Editor Image Gallery.
  3. Use the browse and upload buttons to upload your image/s.
  4. Select one image and click Ok.
  5. This returns you to the Image Properties dialogue
  6. You can examine the image path in this window - This should be a relative path as in this example from one of my portals:
    /Portals/18/Content/WW-Samples/ODW-sample-sites-01.jpg

I don't know how yours got absolute paths, but if you let DNN do its thing, there should be no problem with any of this.

In the last post you made above it sounds as if you've been shifting DNN system folders around... this is a recipe for disaster if that is what has been done and I'm surprised the entire thing hasn't collapsed.

One should really leave DNN to manage each portal's files and folders as it sees fit. The only place one can mess with things when creating content is within the portals/xx/ folder for the particular portal you're working in, and one should only use DNN itself or a DNN module to work in there, not ftp or the server's file manager.

Hope that makes sense

Rob

 

 
New Post
3/1/2008 1:24 PM
 

Hi Rob

That's exactly how I embedded my images, but they all referenced /test/portals/0/image.jpg.  This looks to me relative as there is no domain listed, however of course it fails because the new domain has no child /test of the root.

I happen to be the Host too so access to IIS and root files isn't an issue (it's by RDC).  Here's what I did to ensure the site operates:

1.  Copy all files from root folders mydomain.com/test to newdomain.com (update web.config etc).  However this fails to load any images as thier relative root is /test

ie. Image Properties > Image info displays:

/test/Portals/0/Image.jpg

2.  So, create new child folder newdomain.com/test and copy all files in mydomain.com/test/portals and mydomain/test/providers to newdomain.com/test

Works a treat - or so I think..

Lea

 
New Post
3/1/2008 7:31 PM
 

Hi Lea,

Ok I see what you mean... your portal system was not initially created at root level. The paths are all relative and are in fact correct for the portal - because the portal was in a subfolder.

I'm still a little unsure of point 2. If you have actually moved one of the numbered folders plus contents from inside the DNN portals folder, you'll get into trouble. DNN won't know where to find the portal files if the /portals/xx/ folder was moved. However, I'm not entirely sure that that is what you've done, and if it's working then it may all be fine. Perhaps check  that you can upload a new image and it will show up in the DNN file manager alongside your old images

If you do find there is a problem, move it all back and just use Engage F3. It's the simplest module to use.. after installing, it would take you 2 minutes to do everything required. With it, you just specify a section of the old path e.g. "/test/portals/0/" and replace it with "/portals/0/". It will do this automatically for all instances and only takes a second.

Glad to hear it's working in any case.

Rob

 
New Post
3/2/2008 4:01 AM
 

Hi Rob

I really appreciate all your help , many thanks.

If you have actually moved one of the numbered folders plus contents from inside the DNN portals folder, you'll get into trouble

Yes, I understand that's why there are two portal and providers folders, one pair in newdomain.com root (otherwise DNN will break) and a copied pair under newdomain.com/test.

I'm a little shy of Engage F3 only because I'm not the author of the site and have no experience with adding modules etc.  Also, by looking at their web site I wasn't convinced that a find and replace tool was provided so that would be painful as I have around 100 images - although assuming it does it's the cleaner approach.  I'll give it a go.

Cheers
Lea

 

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Child to Parent portal?Child to Parent portal?


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