Can the megazine files reside in a subfolder

[fimmtv]

Hi all

I am trying to archive our magazines.  So for June 2011, the magazine will reside in
http:www.jewelsmagazine.org/2011/june.html or index.html.

Getting a webpage cannot be found, but my magazine loads if placed in the root folder, www.jewelsmagazine.org.

Does anyone know if there is a problem with loading in subfolders.

many thank

[Hans Nücke]

There shouldn't be any problems at all, but you must assure that the path remains valid.
If you use absolute path names, you must adjust all references; could be somehow critical.
We suggest you use relative path names. Then the root of the relative path refers to the folder where megazine.swf is located in; e.g. archive_folder/megazine/.
If your content is e.g. in archive_folder/book/version/pages/page_l1.swf, then the correct path would be ../book/version/pages/page_l1.swf.
With "../" moving up the folder structure one level from archive_folder/megazine/ to archive_folder/.

Based on that the simplest way will be to

• use always relative path names
• move the complete content, i.e. your megazine/ folder and subfolders as well as your book folders into a new folder
• have your book folder at the same level as your megazine/ folder

This at the end is the suggested folder structure as used and created by the MZ3-Tool (see demo packages).
The advantage of such structure is that all books in the new subfolder share the same MegaZine3 software.

So your structure would look like this:

Code: [Select]

yourwebsite.com/index.html                        (your actual book)
                           /megazine/...          (the MegaZine3 software for your actual book)
                           /js ..                 (and all other files and fodlers like css/ and style.css that are part of MegaZine3 software)
                           /2012/                 (your actual and newest magazine, already using the correct future version name;  e.g. january/)
                           /archive/2011/         (your book content of 2011, using the month as version name, like june/ )
                           /archive/megazine/     (the MegaZine3 software you used in 2011; and all other needed folders and files)
You then only need to adjust the index,html file and point to the correct version name (month).
Access to the archived magazines could be managed by different index_year_month.html files with the correct path to the archive/ folder and year/month folder of your book; and the MegaZine3 software of that year.

Over the year you would add new version folders 2012/january/, 2012/february/, ... 2012/december/; and adjust the index.html file to point to the actual month whenever a new version comes out.
And at the end of the year you can create a new year/ folder (i.e. 2013/) and move the complete 2012/ folder to the archive/ folder.
You even can automate the index.html file for the archived magazines with javascript and HTML, asking for the year and month and then building the correct path name automatically.

Hope this gives an idea about one possible structure and approach. You of course can structure it as you want and need, e.g. instead of month names give it month numbers and even add an additional folder level for different magazines like 2012/01/mag_1/megazine.mz3

BTW: I added this hint to my tips-blog