[RESOLVED] caching question

Desbrina

I've been looking at caching my files since my host has told me the scripts i'm using take up to much RAM

I've followed the below tutorial
http://www.theukwebdesigncompany.com/articles/php-caching.php

Which i can get working, but my website has different skins for different people. They choose which one they want to use. Obviously when i cache the page it only cahces one skin, no matter what one the user is using.

In all of my pages i have the following include ibn the head section

<?php include('css/css.php'); ?>

and in the css.php file

<?php 
	$layout = "SELECT layout FROM user_settings WHERE user_id = '".clean($_COOKIE['mttcg']['i'])."' LIMIT 1";
	$lresult = mysql_query($layout) or die(sql_error($layout));
	if(mysql_num_rows($lresult)) {
		while($lrow = mysql_fetch_array($lresult)) {
			if($lrow['layout'] == 12) {
				print '<link href="/css/layout12.css" rel="stylesheet" type="text/css" />';
			} elseif($lrow['layout'] == 13) {
				print '<link href="/css/layout13.css" rel="stylesheet" type="text/css" />';
			}
		}
	} else {
		print '<link href="/css/layout13.css" rel="stylesheet" type="text/css" />';
	}
?>

<!-- This is for use within Dreamweaver and should be commented out when used live
<link href="/css/layout13.css" rel="stylesheet" type="text/css" /> -->

How would i go about getting it working with the correct layout for the correct user?

2005

I think you need to cache pages for each layout and then:

if (file_exists($layout-$cachefile)) {

include($layout-$cachefile); 

}

Why you don't want to store layout information in cookie instead of quering DB every time when page is loaded?

Desbrina

I was against cookies because if a user clears them then they would have to go and change the layout back to the one they want

I guess what i could do is to get it on one page to find the database info and store it on a cookie, then use the cookie until it expires (i'd probably make it last only 24 hours). It'd cut down on the queries to the database, since they are on every single page i have (which is probably about 100)

djjjozsi

lets say that, registered users could change the design.
and then you can store the style in a field connected with the userID.

its enough to you ?

Desbrina

Do you mean a field in the database, if yes, then thats how its currently done

2005

Why you are against cookies if you store other user information as user_id in a cookie anyway.? If user clears cookies, all cokies will be deleted, not only layout information and user will be forced to relogin.

You can store layout info in DB, but it's not necessary to query DB every time when page is loaded. Do it only once when user logs in and store layout information in a cookie.

Desbrina;10893964 wrote:
I was against cookies because if a user clears them then they would have to go and change the layout back to the one they want