I'm using the 7dana-jane theme for my site. I replaced the XOOPS logo banner at the top with my own logo banner. I did this by replacing the logo.jpg in the themes images folder (for 7dana-jane) with my own logo.jpg (same file name, different image).

I went into the themes.html, and replaced the banner image reference to themes/7dana-jane/images/logo.jpg. I wouldn't have changed this, but neither my banner nor the original 7dana-jane banner version would render in any module except for the start page. The original code referenced some kind of PHP function, which I don't understand. Thus I replaced it with a pure html reference to my image as stated above.

My changes work out fine on the start page if I do not include a module. However, when I navigate to another module or include a module in the start page (such as the news module), the active module adds it's module address.

Thus, instead of the correct address of:

http://mysite.com/community/themes/7dana-jane/images/logo.jpg,

The address becomes:

http://mysite/community/modules/news/themes/7dana-jane/images/logo.jpg.

Obviously, this is the incorrect address to where the image is currently located. I could fix this by changing themes/7dana-jane/images/logo.jpg to images/logo.jpg in the theme.html, and copying my logo.jpg to the images folder of each module and to the images folder in the main directory. However, this is very redundant, since I would have to include the same logo file in each module.

How do I have XOOPS retrieve/render my banner logo from the same image folder, regardless of which module is navigated to?

Dave

is your theme folder on the same level as your community folder?

What was the address you installed XOOPS to?

Hi Xman04,

you can't use relativ path (in xoops) for logo-image source..

If logo.jpg is located in themes/theme_name/images folder use this code:

Quote:
If logo.jpg is located in xoops_root/images directory use this one:
Quote:

I think his problem goes a bit deeper then that

did you install XOOPS to

http://www.YOURSITE.com

or to

http://www.YOURSITE.com/community

Hi Arowana and SevenD,

I think that maybe I made a huge installation mistake.

The community folder is a subfolder I created within the public_html folder of my host account. I access the XOOPS portion of my site by typing the URL: http://www.mysite.com/community. When I type that, it brings me to the start page of my XOOPS site. The themes folder is a subfolder of the community folder (not on the same level).

Should I have installed XOOPS into the public_html folder of my host account, instead of the community subfolder I created? Is this what is causing my problems? Does the root level domain need to be the start page?

I was going to use http://www.mysite.com as an intro page, which provided a link to the start page of the XOOPS community section of my site (http://www.mysite.com/community). What about installing XOOPS to a subdomain. Would this cause the same problems?

Dave

Dave,

As long as you installed it to http://www.YOURSITE.com/community you should be fine.

You can see my site, I have XOOPS installed on two different subdomains and I have another site that it is installed at http://www.YOURSITE.com/xoops so it will work. You might have gotten a bad install. If it is not too much work you might want to try and delete everything and re-install it


http://www.xoaclan.com - intro page
http://moh.xoaclan.com - one XOOPS site
http://cod.xoaclan.com - Another XOOPS site using subsite to link the database tables to have both sites us same logins