mz3 not being found

[Hans Nücke]

I have an idea... the demo/tutorial still uses an old version of MegaZine3 (I think v2.0 rc2). So if you downloaded the latest version (what is OK and what you should do!), then you have to use the index.html file that comes with that version.
And modify that!
Best is to leave it at the position within the directory structure as is and only adjust the path to your mz3 file!
I.e. remove the // (comment indicator) and define the location where your mz3 file is.
You probably can use/copy what you already have in your (old) index file, i.e. something that starts with ../../

So: Use the index file that comes with the package! And modify that.
Do not use the old one.
Compatibiity probems!

I know... I have to update the tutorial. It is on my list

[CraziestOzzy]

.MZ3 and .ASUL can be be given permissions on your server for access rights. You need to log into your respective accounts and grant permission there for those extensions. I have not uploaded my content for my version of the Megazine3 book yet to a server to experience your problems with errors, but can say that security from some server providers may need to be looked at. I use Linux as my website engine as issues like that encountered here are easier to fix.

[Crusader12]

wish I had the answer to this one! I'm stuck in the same boat as everyone else. I also have hosting through a large provider and when I change the mz3 file it loads the preloader.swf then the gray screen... and that's all.

I really hope there is an answer to this one. Having to switch back to fresh flash catalog for now and hate it.

[mrmaskedrider]

I'm having the same issue. When it was named megazine.mz3 it would result in the 2032 error. I renamed it XML and changed the name in the HTML file. Now it does not return an error, but it never loads. The "Megazine3" logo fades away and Firefox reports that it is reading data, but nothing ever happens.

I'm on a Windows hosting account with godaddy.com.

The URL in question is: http://www.department203.com/photo.html

All files are in the standard directory structure (i.e. megazine.swf is in the /megazine folder).

[Florian Nücke]

The extension of the ASUL definition files will be adjustable using the book@asulextension parameter introduced in the next version (2.0.3).

[Crusader12]

So I guess in the meantime the current version of megazine is dead weight?? Is there a workaround for the ASUL files? Looks like a large number of people can't use it.

[Crusader12]

Ok, I'm hoping that I'm able to contribute a little on this subject:

I moved all of my files over to a different host (was originally GoDaddy and was having the exact problem of finally being able to load the XML file, but watching the preloader fade into a sweet gray nothing.)

The other host I'm using is Yahoo, and as soon as I moved the files over everything worked perfectly.
Best to all!

[Florian Nücke]

New version is out, you can now use book@asulextension to set a custom file extension for asul files, e.g. book@asulextension="xml". Additionally to that you'll have to adjust the actual extensions of the .asul files in the gui folder, of course.

[Crusader12]

Awesome! This may be a totally dumb question, so apologies in advance, but where does the book@asulextension="xml" go?

I'm used to the previous version and don't remember seeing this, but it's also popped up in the tutorial for the search and has me confused. Thanks!

[Hans Nücke]

notations like tag@attribute mean that "attribute" is an attribute of tag.

book@asulextension therefor says:
add the attribute "asulextention" to the "book" tag like

Code: (XML)

<book asulextension="xml" .... >

[Crusader12]

Thanks!

[mrmaskedrider]

Unfortunately, this has not solved my problem. My book tag now reads:

<book pagewidth="450" pageheight="400" plugins="backgroundsound" asulextension="xml">

It works locally, but not on the server.

Curiously, if I change all of the files with .asul extensions to .xml, it stops working even locally. If I leave them as .asul extensions, it works locally, even with the asulextension="xml" in the book tag. This leads me to suspect that this functionality is not present yet.

[Azazel]

Thanks for your help and sorry for the late in my answer!

i had do all that you had say me.. ..and more and more(change extension, put files html,mz3.. in every where..)! but the magazine don't work in internet..

so i had phone at my administrators server (fortunately i had can) and ask they to accept the .mz3 extension.. ..and so the megazine charge.. ..only the music!! so after i ask they to accept also the exstension .asul and the megazine work perfect!! the version 2.00 and the version 2.02!!

now i read that the new version accept the change of the .asul with the .xml with the metod asulextension, but for the extension .mz3? i think that the server that not accept .asul dont'accept .mz3 as my server..(i'm not sure.. ..i ask you about this..)

many thanks guys!

[Florian Nücke]

Meh, forgot to change one line [don't know how I overlooked that...], get the 2.0.3b version (hotfix). The megazine.asul file still had to be named megazine.asul, regardless of the book@asulextension setting. This is fixed now. So just change the file extension of the .asul files to whatever you set in book@asulextension (probably "xml" )

[patrocipes]

Hello Guys, I was having the same problem with version 3. I look in the tutorials and found this so I sent a mail to my hosting company explaining that I was installing the awesome Megazine3 and asking them to add the two new mime types, dz3 and asul, along with a link to the tutorial just in case they had any concern.

And voila! Problem fixed!