Birdie...It's a little strange that it works for everybody else...

What option are you using and what kind of server (also what php version) is that ?

Its a shared host. I still trying to get to the bottom of it. Waiting to hear back from some people who know a lot more than I do about it.

I'm going to install this one on my test forum first to see how it goes. But the idea looks great. Save resourses = save $

Thanks mate.

Have you upload the file in the zip??
or have you delete the file and no unisntall the product?

I have 6 forums; 4 with one host and two with another. I installed the mod on all 6 after it worked fine on one. The 4 with the one host worked fine; the two with the other host really got screwed up. They all in a shared hosting environment.

Unfortunatly, the host of the screwed up ones are not available (its currently 10PM Friday night in Australia). Fortunatly the hosts of the other 4 are available (they in a different country) and looked in to it for me. They have fixed one and given me the instructions to fix the other.

They said the problem is most likely the way the other host has the servers set up (I do not know what).

In case this happens to anyone else, this is the instructions they gave me:Thank you to the great folk at URLJet for allowing me to not have a sleepless night over this one!

Installed on my 3.7 forums, thanks! :D Though, how can I test if the memcache works?

One of the best modifications i've ever seen at vb.org in the last couple years. Code is perfectly structured , doing its job perfectly.

Definately deserves to be the mod of the year.

Indeed, also voted for NOTM.

+1 ;)

Excellent work :)
Pretty similar to what I did (regarding the concept, your code is much better than mine!).

A few suggestions though:

• Support for eAccelerator
• User-definable prefix in cases where there are several installations on one server (maybe use the config.php setting?)
• Hook into template_compile, css_output_build, admin_style_datastore to automatically flag cache dirty
• Take care of custom datastore entries (if a datastore cache is being used) on init_startup to avoind the additional query

Partly - you must rebuild the cache manually afer TMS actions.