I've been looking for a fix for cross platform CSS support for awhile, and it's increasingly looking like I'm just going to have to byte the bullet and learn how to code CSS.

If I read it right, I see two methods mentioned above (browser detection and alteration within the CSS file itself, or detection via PHP which then directs the browser to the appropriate CSS file) , which is the better of the two for performance, scalability and reliability?

Well I'm starting to run short of ideas . I also imagine you've tried deleting all your temporary internet files, and have tried manually looking at the code in the relevant files?

And you are using the default template I take it? That is weird. You do have cookies enable on your browser don't you? Have you tried testing this on a different machine?

That is weird then

What kind of time period are we talking about. The code from the jan304 hack is set to leave the session open for 1 hour from memeory. I assume you're just logging in with the remember me checkbox selected, closing the browser and opening it again?

Reason I ask is because when I tried to first apply the hack, I tried doing it by manually adding the lines of code to the files. After much stuffing around I couldn't get it to work, so I downloaded and applied the hack from jan304 and it worked straight off.

However, last night I decided to recreate my test site from scratch, and I could not get the checkbox to be displayed after applying the appropriate hack to a dead stock install of either 2.02 or 2.03.

What I found I had to do to get the checkbox to be displayed to be able to select using the exteneded session was go into the template_c directory off the site root, then look for a file names something like system_block_login.html, then add the line of code below (which is included in the jan304 hack readme) to it manually.

<input type="checkbox" name="rememberme" value="On" class ="formButton" checked />Remember me?<br />

I have no idea what the template_c folder is for. I can only imagine its a template cache of some sort? As to why the hack worked for me in the first place, I can only assume I had already done exactly as above before applying the jan304 hack.

The ironic thing is that this is my second attempt at this post, my first session timed out. Just goes to show how useful a hack like this is .

Hey Ace_Armstrong,

Do you get the "Remember me?" checkbox? As I think the advantage with the hack from www.jan304.org is that you must select that checkbox to use the extended session timeout. Otherwise you use what ever the default session timeout you have set.

I've used the hack from Jan's site, and it worked without a problem using XOOPS 2.02, W2K Server and IIS.

My only reservation with using such a hack (which has already been brought up I think) is that to my understanding the way it works is by leaving sessions open for extended periods of time. My problems with this method are;

1. on a site with a lot of traffic, there would be a significant performnace hit on your server.

2. Using this method is not suitable to have true "never log off" option.

3. Using this method the "Who's Online" block will always be inaccurate as it'll be populated by not only active sessions, but sessions that may have been inactive for several days depending on what you have set your session timeout to be.

This all said I think it's a very welcome hack, and given the option of having it, or not having it I most certainly am on the side of it being there. Better to have some form of auto login than none at all.

I've been an end user of CMS modules for far longer than I've been running them on my website (and thus have zero programming knowledge, so forgive me if I'm being simplistic), and I've always found it extremely frustrating not being able to set the option to login automatically to a site, especially when signing up to dozens of sites with lots having different username and password length and makup requirements making it difficult to have a generic username and password to use on all sites.

The lack of a auto login feature is one of three problems I've come across with XOOPS which if I hadn't been able to find some workaround for would've forced me to look at another CMS as my solution. Other than that, XOOPS is a top CMS and is well ahead on the easy of use and managebility side of things.

like most people aware of the lack of a true auto login feature, I encourage the XOOPS devs to keep up the great work, but please look into implementing a configuratble true auto-login feature into the core for a future release. Perhaps even in it's own module?

Quote:

True to a degree, but a lot of users also get tied up and enjoy having access to forum usage statistics data, and for the web site owner I see this as being quite important for aiding in tracking site usage. I've really only looked at phpbb and newbb, and phpbb seems to accomodate a lot more statistical data than newbb. If newbb where to incorporate some of these features I'd have no desire to look elsewhere. As is, I think newbb is a perfectly functional forum, if only a slightly vanilla flavoured one.

Quote:

Thanks for that Tom, I plan at this stage on using the phpbb module unless I find any great reason not to. I only plan on upgrading XOOPS on major change releases, or on releases that directly address problems I have. As a work around to upgrading the non XOOPS supported modules such as these forums you suggested, couldn't you use one of the current migration tools for phpbb or IBF to convert to an older XOOPS version, then upgrade that via standard XOOPS upgrade path instead of migrating directly to the new XOOPS version? I'm sure there would have to be a catch with this idea ? But I'm not that smart .

Thanks for the theme suggestion too, I actually found a pretty nice XP theme on this very site .

Quote:

Thanks thepod, I actually ended up downloading the hack from www.jan304.org which is working a treat on 2.02 atm.

Hey thepod, you have just answer 2 out of the 3 highest ranking reservations I had about XOOPS. After reading your post I went straight to that site and have already got IPBoard working on my testsite and will give his phpBB module a spin in the next week.

Only problem I've had is that I've been unable to get the login hack to work . However through tinkering I've managed to stop my site working at all , lucky I backed up. I'm using a W2K / IIS combo, are you able to point me in the direction of getting this login hack to work? I've tried doing everything discussed on the forums there, but nothing changes.

This is coming from a total PHP / CMS newbie purely from the viewpoint of manageablity and functionality and site layout. I almost chose PHP-Nuke over XOOPS with one of the main reasons being PHP-Nukes use of the phpBB forums (I also like the Somara XP theme for PHP-Nuke, I'm sick I know ) . One of the other major issues I have is with XOOPS is the CSS aligment issues with the seemingly very broken IE 5.X.

The things that stopped me was the rather hacky method it seems to take to get PHP-Nuke to work on a W2K / IIS server (especially in comparison to XOOPS), and reading through some of the post here saying how far ahead the XOOPS project is compared to the others which I'm inclined to believe given the very slick installation and general feel of XOOPS. The other thing was I've now come across several XOOPS based sites that don't seem to suffer the CSS layout issues I have at all indicating to me there must be an achieveable fix which I'm yet to persue.

Anyway, my point being although the newbb forums are totally functional, imho they lack a lot of statistical and management features that phpbb seems to offer. In the end I suppose it comes down to I'm looking for a complete cms, not one that'll just do the job. I think XOOPS is so close it's frustrating seeing it not taking that little bit further to improve on what I see as almost its only weakness (that being lack of top notch forums), especially when I lack the programming skills to be able to contribute in the area.

Just my 2 cents...