We could configure the flash magazine so that it imports the content from a different location. We have many clients who use content management systems.

We create a special solution for them where they upload the  pageflip.html [which you will rename b4 upload]& the 3dissue.swf file to their CMS system and then upload all the other content (subfolders relating to that issue) to a remote location. The general URL location of those subfolders is embedded inside the 3dissue.swf application and the name of the HTML page that you upload along with the 3dissue.swf  contains the name of the folder in which that content is stored on the server.

Lets say for example that

1. you decide that you will be storing the content that makes up the magazine at http://www.mymediaserver.com/emags/ 

2. The issue that you have created is "issue1"

3. The CMS website is called www.myCMSwebsite.com 

Before forwarding you the software, our team would embed the “http://www.mymediaserver.com/emags/” url inside the flash app 3dissue.swf.

When you create an issue, you

1. Create a folder on your mediaServer called "issue1"

2. Go the project folder and upload all the subfolders to the mediaserver.com/emags/issue1/

3. Then all you have to do is rename “pageflip.html” to “issue1.html” and upload it to your CMS along with the 3dissue.swf

And that’s it. When you want to launch this on your  www.myCMSwebsite.com site you open issue1.html, this launches the flash magazine engine 3dissue.swf.

The flash magazine then combines the URL hardcoded inside the 3dissue.swf (http://www.mymediaserver.com/emags/) with the name of the html page that you launched the digital editions from (issue1) and this is how it will know that all the content will be stored at

 http://www.mymediaserver.com/emags/issue1/

This elevates the worry of interference with existing CMS systems.