hiteckart:

Does it kick you out or does it redirect you to the login page? Seeing the source of your site there's nothing in the blocks. You have not accessed the site?

Or to start from the beginning: did you check directory and file permissions before the installation? It's there: you need to have the directories cache/, uploads/ and template_c/, as well as the file mainfile.php, writable before the installation.

Another suggestion. If you have access to the database, open table xoops_config, look for the register with conf_title equal to _MD_AM_DEBUGMODE and set the value of conf_value to 1. This will at least give you PHP errors when refreshing the page.

Cheers.

vinit:

WF-Section is a general articles management module, and despite its bugs, it's a very powerful tool. Soapbox is a columns management module. It's not that powerful, because it was designed with simplicity in mind and with not many bells and whistles.

It's been ages since I last updated the module, and I apologize to all XOOPS users for this delay. There is now a final RC3 for version 1.5 over at the dev's site:

http://dev.xoops.org/modules/xfmod/project/showfiles.php?group_id=1020

I'll wait a week for bug reports, correct whatever's reported and by September 20 will release version 1.5 final. Honest.

Cheers.

PS: This release includes too many changes to mention, and it includes no documentation. You'll have to play with it to find the improvements. I hope you see this as an incentive rather than a disuasive thing.

libervis:

A few additional suggestions, if you don't mind:

1) Two notes regarding the introductory text: a) change the styling to make it more readable, like the text of the "About us" page, for instance; b) reduce the word count. Think of it as a mission statement: should be short, sweet and to the point. I guess this comment includes also a free comment about the length of your mission statement...

2) I'm not sure about how you did the block labeled "Sub Menu" (probably with a MultiMenu), but I'm sure of this: a) You need to look for a better label; 2) you might try to use Tiny Content for these pages. I assume they are now static pages that need to be edited by hand; the menu just points to them. If you use Tiny Content, you'll be able to manage them --that is, it'll be easier to edit them.

3) The icon used to denote the topic is at the far left of the text block, but it leaves a white gap there. I think this would look better at the far left and without the gap. You can do that easily with something like a floated span (just take out the spaces): < span style="float:left; width: 20px; margin-right: 6px;" >< img src="etc" width="20" height="20" />< /span >.

4) Change a simple value in your theme stylesheet to make the default line height a larger value. In a 1024x768 screen your text lines are too long (around 120 characters). Giving the text more air will make it more readable. It will also hide the fact that lines with smilies impose a line height.

5) If I were you, I'd take out at least the blue bar below the "Join the libervis.community here". You have too many blues there.

6) I see you've put a lot of effort building the Main Menu. It's actually not the standard menu supplied with the System module. My guess would be this is caused because of the need to have the hover effect. Hey! You can do that with the main menu too! That will save you from having to point your menu items to HTML pages that actually forward the user to the modules' indexes.

Cheers.

jmikow:

Remember that physical paths in a Windows machine or a Linux machine are expressed in different ways. You have to make sure any path in mainfile.php is expressed using UNIX directories logic.

Cheers.

Gopper:

If you wait a bit, I'm almost ready to test a module called FilmMakers that has, among other things, the possibility to list movies and associate them with video clips, and later to reproduce the clips using an embedded player. For the moment only QuickTime and WMV/MPG/ASX formats, though.

Cheers.

zer0fill:

As far as I could see, there's no way of doing it, because the rendering of the selector is done through a recursive function that at the moment has no place for optgroups. Sorry.

cheers.

MarcDeMesel:

Julian's points are very sound. The most common cause of modules not appearing in the admin side has to do with what's uploaded where.

What does "do not get detected" mean? Assuming you don't see them in the admin/modules page, make sure the correct folder was uploaded to the correct folder. Since every module author wraps the module in a personal way, some include more folders than others. And though this might sound very basic, nevertheless happens a lot: make sure the folder with the module name, the one that includes at the first level the file xoops_version.php, gets uploaded to the your_site/modules folder. You can check this with your FTP program.

If the files were uploaded to the right place, but still your XOOPS doesn't see them, first verify you have a complete xoops_version.php file in your module folder. If a file is there, XOOPS should see the module and try to install it.

If everything above is ok and you still have no modules there, try repeating the process. Delete the uploaded module and upload it again.

All this is assuming your XOOPS install is correct. With the available information, it's difficult to go further.

The other thing you should do is to turn on PHP debugging in Admin > Preferences. Turn it on and then go to the Admin > Modules page. If you see PHP warnings or errors in the lower part, post them here.

That's all I can think at the moment.

Cheers.

russtik:

You can't just copy the code from a block and expect it to work outside of a block. Simply stated, that is because XOOPS doesn't know the meaning of the Smarty tags placed in the HTML file. The solution would be to add the menu PHP code to the footer (in an unobstrusive place) and to make the necessary Smarty variable assignments. Of course, it gets a little difficult to keep the dynamic attributes of the main menu, but with persistence, I'm sure you can do it.

Cheers.

Mith:

I saw this problem a lot in the early days of developing Soapbox. Catzwolf used to say that it happened when a form had two textareas. I never figured out really what was the matter, but I played moving lines up and down and suddenly the crashes stopped. What I keep seeing is the appearance of form selector ghosts, and I've tracked this down to memory problems when having extremely long sessions with a lot of program opening and closing. So I'd try switching the order of initial declarations.

Cheers.

naxos:

In your left column you'll see the User Menu options. Click on "Edit account" and once there scroll down until you find "Comments display mode". Change it to whatever you want. Next go to "Comments sort order" and define if you want to see first the oldest posts or the newest posts. Finally, click on "Save changes" to keep these options in your user profile.

Cheers.