Problems with imagepaths after migration to production server

May 18, 2015 at 11:02 AM
I'm working on a multiple-portals dnn installation and accessed the two sites locally over


After moving the sites to production server all content shows up correctly,except the '2sic'-images 'cause their path still contains the 'site1'-part and 'site2' respectively in front of /Portals/
<img class=" img-responsive img-rounded center-block" alt="ToSic.SexyContent.DynamicEntity" src="/site1/Portals/0/zumGrotto/Hauptseite/zum-grotto-breitenbach-fassade_640.jpg?w=630&amp;h=420&amp;mode=crop">
instead of what it should be:
<img class=" img-responsive img-rounded center-block" alt="ToSic.SexyContent.DynamicEntity" src="/Portals/0/zumGrotto/Hauptseite/zum-grotto-breitenbach-fassade_640.jpg?w=630&amp;h=420&amp;mode=crop">
Well, i could rebind all images over contentedit-dialog, but in my case this would be a real pain (lots of images).

Are there other strategies to solve the problem?
How can I avoid this problem in future projects?

thx for answers and thx 2sic for this great project

May 18, 2015 at 11:50 AM
The core thing is to have images in an own field in your content-type, and use File:37 kind of linking. That way they will get resolved properly an re-wired on export/import.
May 18, 2015 at 12:55 PM
Edited May 18, 2015 at 2:41 PM
Thank you, but i'm still a bit clueless.

The images have their own field (as HyperLink).
How can i achieve this kind of 'File:xx' linking? Everytime i insert an image with image- or filepicker the common relative (test-) path shows up.

Should I type in the term 'File:xx' manually, and if so, how i get the correct Filenumber?

I really hope that I do not ask for silly point. thank you.


I've found "Permanent Page, Image and File Links"- article on
2SexyContent will automatically use the FileID or PageID whenever you choose a file or page through the UI.
However. That's not the case. always '/Portals/0/logo.gif'-style shows up.

DNN 7.3.4
2sxc 6.6.6
May 18, 2015 at 4:14 PM
The file:xx happens automatically IF the DNN-permissions are set correctly in DNN.

If not (so if DNN doesn't know that the user has read-permissions) it will keep the path.

So if it doesn't auto-resolve, go to the admin-file manager, set the correct permissions on top and make sure you inherit them downwards - should fix everything.
Marked as answer by Collective on 5/18/2015 at 10:45 AM
May 18, 2015 at 5:45 PM
thank you. It works.