1. Remove the index.html file on your server root.

Weird.

Could you try the next operations?

1) Delete the 'upload/multimenu' and go on the admin module link list or image manager (this should automatically recreate the directory).

2) If none appear, create the directory manually and set pemissions to 0777. And go back to 1 and see if the module recreate all the sub directories.

3) If permissions are not correctly set (and you can't change it with your FTP), go in your hosting admin pannel and use the FTP (or file) manager. Usually this one allows you more access than a distant FTP client.

Let me know please...

Quote:

Hmmm... Does this directory exists on your server? Or did you created it manually?



Quote:

Got it. I will prepare a guide on how to create your own menu templates. That's not that difficult.

Sorry, but I don't agree.

multimenu 2.0 is not a new module. It's a new version of this module.

Anyway, if you want to install the new version alongside the old one, I suggest you clone the multimenu 2.x (a 2 click away operation) with a different name.

Hello Xoopsers,

I'm very proud to announce the release of my brand new creation :

>> multimenu 2.0 beta <<

Important notes before use of this beta version :

1) The 2.0 version is absolutely not compatible with any previous version of multimenu (thus any 1.x previous version).
The 2.0 version has been redevelopped from scratch and has nothing to do, regarding code, nore spiritwise with the older version. So, do not attempt to replace and upgrade from a previous version.

2) This is a test version. Please, do not use it on a production website. No support is provided with this test version!

Functionalities

This 2.0 version is full of new functionalities. For instance :

- no more limitations regarding the number of available menus (you can create as much menus as you want).

- categorised module general settings.

- image manager (manage your menu pictures directly with the module build in thumb manage).

- Template manager (customise your templates directly in the build in module template manager)

- Separated code (html, java script and style sheets are separated from the source code and managed independently).

- Automatic detection of new custom templates.

- Templates are common to both index pagea and bloc menus.

- Module cloning.

- Query manager (which allow you to automatically feed your menus from your XOOPS site database).

- Style sheet preferences availaible on templates, menu and link level.

- Deep group permission settings (from menu to links).

- Build in contextual help.

Lack

- Sorry for all who requested it, but the module doesn't support more than one sub link level (I know you will hate me for that).

- Not all english defines are over (help files mainly). Sorry for that. If anyone feel like to give me a hand on this, he is welcome.


Thanks in advance for your feedback on this module.

Make sure your user has activated javascript on his browser...

Xoops offers possibilities for skilless module developper to develop usefull modules.

It doesn't work that way. A module can not pass parameters to the site theme.

My suggestions :

- Media uploader (images, video, flash, sounds, etc.)

- Groups and blocs interface. It's quite tricky actually to find out which bloc belong to what module and so goes with the group permissons). A good example of what can be done is the GIJoe's bloc and group manager interface for modules. Anyway, having the possibility to select datas regarding modules would be good.

- A customisable admin homepage. Instead of having that awfull blank page, get the possibility to insert a custom text (or even shortcut links). A simple textarea in the admin settings could be a good start.

- Modules settings/preferences with a categorie system included (or available).

you can PM me here if you want.