an inline css style will override a style from an included css style sheet. Instead of changing the default css, which changes everything, try finding the one template with the table causing the problem and use an inline style to override the width for just that table.

I like this site for css info:
http://www.htmlhelp.com/reference/css/

Just a heads up for others- I had lots of problems after uploading from my Mac OS X box to a Linux box. The install went ok, got through all the steps but when I went to the main page I got the header (with banner) and the footer but nothing in between -- no blocks for logging in, no main menu.

I did manage to get logged in, but going to the blocks preferences would show no blocks available to be turned on.

After much hair pulling, I decided to extract the files on the command line using tar instead of Stuffit Expander.

This fixed the issue. I've run into problems with Stuffit Expander and tar.gz files before (I'm on Panther now, I had problems under Jaguar too).

Kevin

I can't speak to why they made it an option, but it is frequently requested so I guess that's why the code is in there.

It isn't an option you can turn on during the install, you have to go edit the code itself to turn it on. My guess is they did this to force people to consider the security repurcusions of enabling this.

If turned on correctly, users can select if they want a password remembered or not, it is not automatic.

Yep, that's it. Although I modified the expiration time to a year from login time, instead of basing it on the cookie session time.

I edited each of the following files:

include/common.php
include/checklogin.php
user.php

modules/system/language/english/blocks.php
modules/system/blocks/system_blocks.php

In there search for 'auto' or 'rememberme' and it should jump to the commented out areas that handle auto-logins.

Then I duplicated the default template set, and edited the system_block_login.html template. It has a commented out check box to enable auto-login.

I just installed 2.05 for a new site last night and when applying one of the auto-login hacks from the forum I noticed that there seems to be an auto-login already included, just commented out.

I uncommented all the sections that apply to the auto-login and it seems to work fine (minimal testing so far).

I assume this is a use at my own risk feature, but are there any major bugs with the included code?

hmm, i just downloaded and installed on a hosted server last night, worked fine for me.

Maybe your download was corrupt? I'd try downloading a fresh copy and try with that.

Under the GPL you can sell XOOPS as much as you want (slap it on a CD, put it in a box, sell it at CompUSA). As long as you make the source code available, and you can do NOTHING about someone turning around and selling (or giving away) as many copies of that XOOPS they bought to others.

You can also build modules, from scratch, and put those modules under your own license. However if you incorporate any code from someone else's GPL module, or the core systems, your code must also be released under GPL.

If you modify any of the core or GPL modules, and sell or give away (i.e. distribute) that code then you must make that source code available too, and that code is also covered by the GPL.

If you modify the core and or GPL modules, and do not distribute the code (i.e. for an intranet or system where all clients are purchasing it as a service and it runs on your servers) then you do not need to release the source code.

Of course, this is PHP -- no compilation is possible so technically every time you give someone XOOPS they get the source code anyway... And if you build a module no matter what license you put it under they'll have the source code (so you could sue if they violate the license but it's much harder to hide the code like companies that sell binary-only stuff)

Kevin