Forums

This topic is locked

Extension installation problems

Posted 29 Jan 2002 12:27:18
1
has voted
29 Jan 2002 12:27:18 Marja Ribbers-de Vroed posted:
Hi,

I've posted a question about this on the dreamweaver extensions newsgroup, but
noone there was able to help me.
But I now get several installation problem reports each day, so I really would like
to solve this issue.

Some time ago I developed an extension (called Persistent Layers) that is
causing problems upon installation. However, not everyone is experiencing
the problem.

The problem is the following:
When trying to install the MXP file through the Extension Manager the
'accept extension' dialog comes up briefly, but then disappears again
without having to click a button. The extension doesn't show up in the
extensions list, nor in Dreamweaver.

I'm not able to figure this one out myself, because I can't reproduce the
problem.
Maybe there is something wrong with my MXI file?

I would really appreciate it if anyone here could take a very critical look
at my MXI file (and maybe the MXP too).
If you would be willing to do this, please let me know and I will send you
the MXI and the corresponding MXP.

Thanks in advance.

Regards,

--
Marja Ribbers-de Vroed
www.ribbers-zeewolde.nl/dreamweaver/

Replies

Replied 30 Jan 2002 16:30:27
30 Jan 2002 16:30:27 Marja Ribbers-de Vroed replied:
Thanks to Massimo Foti, I found the problem.

He wrote:
"There is an undocumented problem if you use this sort of things inside your
mxi:

<i>&lt;file name="../myfolder/myfile.htm"</i>

If you try to link to a file above the folder's root were your mxi file is
located the mxp file will be created, but it will fail to unpack itself on
win98/ME. It works on win2000/NT/XP, since your file will be unpacked a
level above the temp folder's root, but it will be harder to remove than the
usual garbage left behind by the EM."

This indeed was the case in my MXI file: when creating the MXP file, I was pulling a shared JavaScript functions file from a directory 2 levels below the directory where the MXI file was.

Placing this file directly in the extension directory itself and thus removing the '../../' stuff from the MXI solved the problem.

Regards,


--
Marja Ribbers-de Vroed
www.ribbers-zeewolde.nl/dreamweaver/

Reply to this topic