I have some pages and blog posts where I embed an image in a body part. In some of these embedded images I have a url link set up. I have my environment set up so that when I make changes, I make the changes in a development environment using
Visual Studio. When I move the web site folder from my development environment to staging. I am using Dropbox to move the changed files to the staging server, then copy the whole folder to my staging folder on that server. I then move to
Webmatrix to test that everything moved as expected. When it all looks good, I publish to production using Webmatrix on the staging server.
This approach seems to work really well, since both Dropbox and Webmatrix are good about only moving things that changed and the folder copy on the staging server gives me a good fallback in case some unexpected change on the dropbox side occurs.
The only problem I seem to be having with this approach is that pointers to the images in body parts don't resolve back to the image files when the folders are moved. I end up with empty rectangles where the images are supposed to be.
I can rectify this by running Orchard in the new location as administrator, editing the pages, deleting the empty rectangles and re-establishing the image pointers. This can be a bit of a pain because:
1. Sometimes the image embedder won't go to the level of detail I need to access the image and I need to delete it from its location and re-upload it.
2. If the image has a link associated with it, I need to re-add that link.
These actions have to be performed twice per image in each move, once when the programs are moved to staging (if I want a complete test) and once again when it moves to production. In general it somewhat defeats the purpose of have development and
staging environments, as I can't lock changes at the development point.
We kicked this problem around briefly in the code club meeting on Monday and by looking at the properties on the image placeholders, found that they still contained localhost in their path. I haven't tracked down all the details, but it appears
related to that. There is apparently a workaround to this problem in the Vandalay module somewhere that I guess will find all these errant pointers and fix them.
But before I go messing with that, I wanted to see if a better solution exists, specifically one that enables me to lock changes in the development environment before moving the folders to staging. Once they are in staging, they should not be modified
at the administrator level.
Thanks - any advice appreciated.