hmm, one problem is caching. Thats why newly added forums are not displayed. After clearing the cache it works. Anyway the caching function of Xoops is hard to understand. All modules are set to "no cache" but still i have to clear it if i change things like templates or some module options.

the fact that the "default permissions" for newbb are not saved is still there.

Hello,

i am using newbb module 4.2. The permissions system has some problem. If i add a new forum and set all permissions then it does not always appear in the forum. Also the default permissions cannot be set. Everytime when i set it and reopen the administration setting the previously set options disappeared. It seems that the changes are not always saved, only sometimes.

Any idea?

greets

Ten Long

Hello,

i have a very strange problem. I have a XOOPS 2.5.5 system running on my NAS without any problems. The same installation i now did on my webhosters server.

If i now open the webhosters page and click some entries in my menu, e.g. news, wfdownloads, myalbum or other modules, then sometimes (and only sometimes) the layout looks strange. Refresh will show the correct layout. "Strange means that the background color of <div> areas are shifted out of their boundary, and thicker <div> borders lap into neighbored <div>.

I never had this effect on my NAS. Can this be related to another software version (e.g., php, mysql, ...) of the webhoster or cache management? What i wonder is that the refresh will correct the display problem, so basically the output of XOOPS should be fine.

I would appreciate any tip :)

greets

Ten Long

hmm, i think the standard installation procedure should be modified slightly. What i did now is:

1) create an index.php which simply shows an "under construction" logo.
2) copy xoops system via ftp to the server except the index.php file
3) rename the install.php file of XOOPS to something like index_install.php
4) upload the index_install.php
5) access viahttp://www.myserver.com/index_install.php and finish installation
6) after install rename index_install.php to index.php

In this way anybody accessing the page at the same time gets only the information that the site is under construction but does not know that an installation process of xoops is going on.

Simple modifications to the XOOPS package.

It might be no big deal to do it the normal way. However, if XOOPS is installed to a server which has a high frequency of visits, then i definitely would prefer that nobody can interfere in whatever kind of way.

greets

Ten Long

Hello,

although this might be a stupid question:

I previously installed the xoops system on my NAS, i.e in the local network. As far as i remember it was just copying the files and then browsing to the webserver with firefox. Now i want to install xoops on my webhosters server. I wonder how i can install it without anybody interfering the install process. Basically everybody can connect to the site at the same time and participate at the installation process.

Do i need put the webhoster account in some kind of administration mode?

Or is it only critical during the ftp copy process and - once i start the installation process and quickly set the admin password - everything is blocked during the further install procedures?

thanks in advance

TenLong

aaargs, it was so small i didnt see it.

The ipb_blue_2 theme misses an important entry in the "theme.html":

<!-- customized header contents -->
<{$xoops_module_header}>

Problem finally solved

The strange thing is that even though some modules include additional css files, they do not appear in the final webpage if the theme is change. I currently have the problem with wfdownloads.

Can you tell me in which php script the css files added by $xoThemes->addStylesheet(...) are included to the html file in the section
"customized header contents"?

And why is this include successfull for the "default" theme, but fails for others?

greets

TenLong

This is definitely not the cache bug reported before. I disabled caching for all modules.

I now have the feeling that the problem is related to the theme, since the default theme gets the css information. However, the "theme.html" from default theme does not have any include area. Where are the css of $xoTheme included to the theme before showing the webpage?

ok i found out something for two modules which are scrambled up:
WFdownload and Profile.

I enabled either default theme or the ipb_blue_2 theme in administration settings, then I viewed the webpage and saved the html code in firefox. In doing so i noticed that in the case of the ipb_blue_2 theme some css styles are not imported.

For example the "Profile module" does not include the css

<link rel="stylesheet" href="https://wepage/language/english/style.css" type="text/css" />

if the ipb_blue_2 theme is used. The width of each table row is then different which is annoying.


The wfdownloads module makes even more strange things since it does not include its own css styles, i.e.

<link rel="stylesheet" href="https://webpage/modules/wfdownloads/module.css" type="text/css" />
<link rel="stylesheet" href="https://webpage/modules/wfdownloads/thickbox.css" type="text/css" />

are missing if the ipb_blue_2 theme is used. If "default theme" is used they become included.

Especially for wfdownloads i dont understand this behavior since the viecat.php imports both style sheets. I have no idea where the import gets failed and why the final webpage does not contain the imports.

Any idea? Fails in css imports are very annoying for the usage of modules. I would suggest to revise all modules with regard to this issue.

Greets

Ten Long

Hello PeeKay,

thank you for the tips. Unfortunately i dont really see the problem in the code. The template wfdownload_viewcat.html (which shows the list of downloadable programs)
does only use css classes provided by the wfdownload module. If i use the standard theme of xoops, the download list looks completely different. In this case the formatting is different with 3 columns. If i use another theme, all is quite scrambled and only 2 columns are used. Any idea why this is so strange? When in the template only wfdownload css classes are used then it should always look the same or not?

greets

TenLong