hi all,

I see in the most XOOPS (core)modules that I use static image url's. In the Partners module it is not even possible to use the <{$xoops_url}> or the <{$xoops_imageurl}> shortcuts because the http:// is standard in the beginning of each line for the image url.

The rest of the xoopsprogramming is using the <{$xoops_url}> or the <{$xoops_imageurl}> shortcuts!

So maybe it's an idea to use these shortcuts for the images in one of the next coming releases of XOOPS or their modules! It would be great if this can be integrated in the XOOPS imagemanager!

When you want to host your site on another server or domain, you need to edit all your [img] tags due to this!
Not very handy when, for example, a server is crashed and you want to put is back online via your backupfiles and database, cause the url is changed then most of the time.

Another suggestion is to change the <{$xoops_imageurl}> into <{$xoops_subdirectory_url}> because this shortcut is used for all subdirectories and their files and not only for imagefiles...

Just to make it more understandable...

Regards....

All these variables point to something specific.

To use <{$xoops_url}> which points to the root directory of the site, it would be something like:
http://<{$xoops_url}>/filename
or
http://<{$xoops_url}>/subdirectory/filename

To use <{$xoops_imageurl}>,which points to the image directory in the root of the site, you would:

http://<{$xoops_imageurl}>/filename
or
http://<{$xoops_imageurl}>/subdirectory/filename

The image directory by default is for images, other types of files may end up there but it is still the image folder, therefore the imageurl logic.

HTH

well maby i have it wrong but when i look in some theme.html files, the <{$xoops_imageurl}> points to that directory where it is accessed from in the theme.html...

so it points, if i have it right, to the subdirecory where the file is located from where you acces this command...

thru or not?