You found the setting.

Basically, if you are making theme changes you need it on so they update between changes. Once you are done making changes, set it to off.

See notes for beta 3.

http://dev.xoops.org/modules/xfmod/project/?group_id=1001

They are coming soon.

Yes, some means of reporting http referrers is a standard part of all web stat programs I'm pretty sure.

I use this module on my site:

https://xoops.org/modules/mydownloads/singlefile.php?cid=24&lid=696

Someone posted an alternative template about two months ago that you can search for here in the forums.

Good search words would be "web stats" or "istats".

Good find! XOOPS keeps amazing me....

Great idea! I don't think anything like this is implemented but it would be really nice.

Makes perfect sense. It's similiar to the many permutations that I've tried however.

The above code centers the logo and then spreads the rest of the header (the shield buttons) and the center column to 100%. So the buttons get spread out which is what I'm trying to avoid.

What I'm aiming for is a fixed 1000px theme centered with gutters on both sides.

Thanks for the help. You confirmed I was heading in the right direction and I appreciate your excellent advice. 80% of my users view at 1024 and another 10% at 1280 with a few people at 1600 and two at 800. I'll keep fiddling with it because I want it to look perfect, but I'm betting none of my users will even notice. Especially since many 1600 users tend to not browse with their browser full screen.

I'd like to set to 1000px wide fixed. I'll be making a second version for 800px.

Thanks for spooting the block title width. It wasn't an oversight. I just learned something new from you regarding how css works. On the surface it's straightforward, but there are some subtle nuances in how the different browsers render that can make it quite a challenge. I need to remember that values are being inherited.

Ok, I'm just cleaning up the last loose ends with the theme so I can get to the real work of adding some long-needed content. However, I've got two things that are giving me no end of trouble.

1) I've tried everything that I know of to center the theme to no avail. I've tried as many of the suggestions as I could find here in the forums.

2) The theme looks fine in Mozilla but the right column gets wierd in IE. What did I mess up???

I'd be happy to sent CSS and theme info to anyone that can help out. Or if you use Mozilla Firefox, check out the following fantastic extension which I've found to be a godsend for tracking down exactly where bits of css. It also allows you to view the css for whatever page you are viewing online.

http://update.mozilla.org/extensions/moreinfo.php?id=60

EDIT: I forgot the site url.... Argh!!! Sorry about that! The site is presently at:http://log.game-host.org

For me, I find that XOOPS fits my needs better than phpNuke did. I have no vested interest in any particular CMS. I only run small game/personal interest sites. Your needs might require something different. For me, the biggest differences between XOOPS and phpNuke are modules, themes and updates. I've run Nuke for several years and have been switching those sites over to XOOPS these last few months.

phpNuke has a LOT of modules for a huge variety of things. On the surface that's a good thing and I miss it. But there doesn't seem to be any interaction between mod developers in phpNuke. Whenever I installed a phpNuke module I was rolling the dice as to whether my admin menus would work anymore. In Xoops, I have never had this issue. Due in large part to the Module Dev Forge and strong community discussing matters on the development site here instead of on multiple fan sites with divergent agendas is a really nice thing.

Themes seem to be easier to modify in Xoops. But that is likely just be my knowledge of css, xhtml and php have improved over the years. I do however like that there are a number of people working towards tableless themes and actively considering standards. I need to learn more about Smarty to see whether it will be useful to me.

Updates are painless and timely. In phpNuke, since the fixes to the core code went to Francisco's paid users for a few weeks before public release, it took some time.... This was particularly frustrating in light of the increase in defacement and sql injection attacks last year. XOOPS is very secure against those issues as far as I can tell. Truth be told, I haven't seen a single compromised machine due to XOOPS since this spring when I started looking at it.

Well-coordinated, easy to integrate with straightforward installation and administration. XOOPS works.