Guistock,

Theme is wonderfully simple and clean. Very MACish, (from a non-mac guy). Please forgive me for re-hijacking your thread.

Nautis -

The way the themes/template break went, you can build alternate templates into your themes in the /templates directory. If you build theme suites (similar features but different color/image patterns, you can maintain a complete template set (Xoops supports multiple template sets) and them choose the one that supports the theme you are working on.

Xoops also let you save the "template package" as a gzip.tar and you can publish this with your theme as well.

I agree with you that it would have been better for the themes/templates to remain together as a unit. The problem is that third party modules provide their own templates, and themes usually only cover the core modules anyway, so either way, you will need to muck with the templates to make 3pty mods look reasonable.

BTW, I really like your template for the links module. I have been building lots of simple themes lately, and know exactly how much work it is to get things looking the way you want.

My template pet peeve is that the non-index templates (i.e. system_redirect, system_siteclosed, etc.) do not let you slurp in the theme_css into the template, so if you want them to match your theme, you have to hack the program, or hardcode the colorscheme into the templates. Both are evil.

Cheers,

Rich

There was a visitor2 statistics module, that was available for 1.3.x but it was eliminated due to some security issues.

There are several news articles and forum threads regarding visitor2 that should answer all of these questions.

Thread here!

Cool hack.

noticed that it works on the default theme and the phpkaox theme but not the x2t theme.

What exactly do you think is wrong with the DHTML - other than the goofy grape ape color, it doesn't look that bad to me.

Nice Job!! Plus I really enjoyed your bible discussion forum humor.

CoolPops and Ndial,

You guys have lots of ambition... Great ideas.

It would be cool if this could be done as a post editor "plug-in". If the XOOPS core allowed a module to register a plug-in to the to post editor for exactly this reason.

This would be a powerful way to extend the system. But definitely not for X2. Would be a core hack in X2.

Would you be surprised if you were not the only one interested in a bible module or hack for Xoops...

Come and check out The Regenerate Web

I would be happy to collaborate on this kind of a function, either as an extension of the editor, or through some other technique.

this is the problem with the php directive register_globals
In order for the forum admin functions to work in RC2, register_globals must be on.

if you are hosted, most times you can set this using .htaccess

php_value register_globals 1

Actually, it is just extra sessions in the database that stick around, and how long before the session cookie on your client expires. Only dangerousif you have hundreds of users, but much less annoying than having my session time out because I got a phone call interrupting a post. It does however confuse the hell out of the Who's Online block...

It just happened again this morning. I started a post on this site, got interrupted and when I hit submit...

Whack!!!

My public site has timeout set at 1 hour, but my test site has it set for 1 day (because I hate logging in, and nobody lse uses it.)

In the System Admin / Preferences / General Preferences dialog, there is a session timeout parameter that defaults to 15 minutes in the X2 install. You can extend this timeout to a more reasonable amount of time say 2 hours or all day if you want.

In XOOPS 1.3.8 it was specified in seconds, and so ya had ta do a little math!!!

Higher volume sites like this one, have a shorter session expiration time to improve performance.

No kidding! It would be nice, even if the registration process could tell the user that he miskeyed his e-mail address. I get e-mail from less savvy users who never got the activation key, and most of the time it's because they keyed their e-mail incorrectly.

I've seen some raw smtp scripts that can do this, it would be optimal to add a validate method to the XOOPS Mailer that would go out to the smtp server and validate the address's existence.

It would be cool to have a user admin functions that would run through the member list and detect those who had invalid e-mails and flag them as well. Then you could send a PM warning them before you whack their account.