Home > Archive > PHP Smarty Templates > May 2004 > Re: [SMARTY] Before I reinvent the wheel, Call for href munging prefilters
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: [SMARTY] Before I reinvent the wheel, Call for href munging prefilters
|
|
|
| --- Greg Stark <gsstark@mit.edu> wrote:
>
> I want to track some information on every page hit. In my case I want
> to use
> it for an uber-referrer that can identify specifically which hit in
> my
> database logs the referring page was. I have the unique identifier
> handy as a
> Smarty template var, I just don't want to have to manually modify
> every href
> and every form action etc to pass it.
Wouldn't it be wise to use a PHP prepend file for this and keep it out
of Smarty? And perhaps the PHPOpenTracker library?
http://www.phpopentracker.de/en/index.php
xo boots
__________________________________
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs
http://hotjobs.sweepstakes.yahoo.com/careermakeover
| |
| Greg Stark 2004-05-04, 4:05 pm |
|
boots <jayboots@yahoo.com> writes:
> Wouldn't it be wise to use a PHP prepend file for this and keep it out
> of Smarty? And perhaps the PHPOpenTracker library?
> http://www.phpopentracker.de/en/index.php
Well PHPOpenTracker looks interesting. But it suffers from the same problem
these systems usually suffer from, namely it doesn't know enough about the
application. Querying OpenTracker's tables for any kind of
application-specific reports will be nigh impossible.
It also has a few other issues, it's based on Cookies so the paths aren't
actually correct, and it's based on sessions so it will fail with multiple web
servers.
My goal was to pass the actual database id of the page hit from the previous
page to the next one so that the paths are iron-clad. That's looking like it
might just be too much work though.
--
greg
|
|
|
|
|