phpOT many issues or just one big one that I am missing?

Richard Green <[email protected]> Wed, 11 Aug 2004 17:01:09 +1000
Newsgroups gmane.comp.web.phpopentracker.general
Message-ID <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Hi

I am attempting to use phpOpenTacker (pOT) with little success. I seem have a 
variety of problems which suggest to me the may be something fundementally 
wrong with the way I have this configured. 

I figure its unlikely the package made it to Version 1.4 being totally 
broken :) so it's more likely to a problem with my installation (even though 
I have done it a couple of times now... 

Using php 4.3.4, mySQL 4.0.18, graphviz 1.10.20030, jpgraph 1.5.2 on Debian 
Sarge. 

Started using pOT 1.5rc1, reverted to last stable on sourceforge (1.4.1) to 
see if this changed anything (it did not).

Debug level of 2 and  
$PHPOPENTRACKER_CONFIGURATION['track_returning_visitors'] = true; 
 $PHPOPENTRACKER_CONFIGURATION['clean_query_string'] = false;
Table names as per distribution.

I get the cookie for tracking according to the name set in the config, with _1 
appended (for the client ID I assume).

I've been working through the examples from the documentation:

- - all_paths - debug shows no database active, no output.

- - average_clickpath_length - works

- - average_time_between_visits - SQL query shows in debug, runs out of memory 
allowable for a PHP process (8M, tried 16M, same result)

- - average_visits - I suspect answer of exactly 1 is not correct for our busy 
site based on data for 3 days.

- - individual_clickpath - SQL query shows in debug, no results, no errors 
(valid accesslog_id shows 2 records on direct SQL query).

- - longest_path - no results, no errors

- - php num_one_time_visitors - returns a negative number (have configured to 
track returning visitiors...

- - num_return_visits - works

- - num_returning_visitors - returns negative value

- - num_unique_visitors - works

- - page_impressions - works

- - returning_vistors - no results, no errors

Any ideas? 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBGcQ1d+qap87eiNgRAtlXAJ9uX67GgOCmbbjMCTi0J+b3s1n26wCfVoFV
GXAAgF9hVgqbmwoIKdi9MhE=
=Bb+g
-----END PGP SIGNATURE-----