[ phpopencounter-Support Requests-708317 ] Results with Webbug
"SourceForge.net" <[email protected]> Mon, 24 Mar 2003 14:13:50 -0800
| Newsgroups | gmane.comp.web.phpopentracker.devel |
|---|---|
| Message-ID | <[email protected]> |
Support Requests item #708317, was opened at 2003-03-23 02:50 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=201716&aid=708317&group_id=1716 Category: None Group: None Status: Open Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Results with Webbug Initial Comment: Hi, We are planning to use phpOpenTracker for a number of sites hosted by a hosting providers. We have a main domain, lets say www.main.com and a number of secondary domains e.g. www.domain_1.com and www.domain_2.com. As our sites are mainly html-based we are using the webbug to trace our visitors. We are hitting the bug by www.main.com/phpOpenTrackerDirectory/webbug.js. P3P is implemented in the .htaccess file of the webserver: Header append P3P 'CP="NOI NID ADMa OUR IND UNI COM NAV"' However, we experience a number of issues: 1) domain_1 is having client_id 1, domain_2 is having client_id 2. In the simple_report example, column "Client"`, domain_1 is listed as "main", domain_2 w/o name and thus not clickable. How to get the name. 2) the referrer is not filled correctly; "internal" links, e.g. a click on www.domain_1.com/page_1.html to www.domain_1/page_2.html is recorded with page_1 as referrer. Problem now is that they are pushing the real (external) referrers e.g. from google or other external sources from the top-10 list of referrers. 3) The document title in simple_report/current_activity is not correct. In webbug.js document.URL is used where you would expect document.title, is this right? 4) What extra functions are in webbug.js in comparison with directly calling the image.php script? 5) Are there any standard-reorg functions for the database? Thanks for the support, Ingo ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2003-03-24 14:13 Message: Logged In: NO 1) Too bad, this seemed to be a pretty generic feature, not depending on the simple_report. 6) great. Again, Tx for all your work; just might close this support request by now. Ingo ---------------------------------------------------------------------- Comment By: Sebastian Bergmann (bergmann) Date: 2003-03-23 23:02 Message: Logged In: YES user_id=7993 1.) simple_report is meant as a simple, sample application that uses the phpOpenTracker API. I will not add simple_report specific configuration to the phpOpenTracker.ini file. 2.) 3.) Thanks for the offer, but I already have enough production data to test with. 5.) Aggregation of old data is planned for the future. 6.) A full-fledged, report wizard / front-end for phpOpenTracker should become available later this year. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2003-03-23 10:26 Message: Logged In: NO Hi Sebastian, Thank's for your very fast reply. 1) I will change the coding. Feature request: translation table "client id"-> "name for display" in phpOpenTracker.ini; e.g. client_name_1 = "domain name 1" client_name_2 = "domain name 2" 2/3) In case you need any productive data I am happy to give you access to our productive data. Just let me know: e-mail: ingo.land at vbb-bv.nl (replace at with @). 4) Unfortunatly we do not get these extra functions to work properly (see 2/3). 5) Hosting at hosting provider means that we do not have GBs for a logging database. A reorganisation module could clean-up historical data (e.g. older than 3 month) but sustain key data as the top-lists or number of hits per page for future reference. Best regards, Ingo Extra comment: Somewhere you positioned your tool (thanks for building it free) as a framework for developers. Please keep in mind that for developers not having full control over the webserver (like us using a hosting provider) your tool is great for traffic analysis. Rather than additional APIs we would welcome more end-user facilities, as we prefer investing web-site development time into functionality of the site instead of rather generic analysis functions. Examples are detailed analysis, data cleansing, country analysis, evaluations over all clients, information with regard to returning visitors, etc. ---------------------------------------------------------------------- Comment By: Sebastian Bergmann (bergmann) Date: 2003-03-23 03:12 Message: Logged In: YES user_id=7993 1.) You need to edit simple_report/index.php if you are using more than one client_id. 2.) 3.) I never really tested the Web Bug in a production environment. I have scheduled some time to do so and improve the Web Bug functionality during the next couple of days. I plan to get this working properly before phpOpenTracker 1.2.0 gets released. 4.) You need JavaScript to get the correct document and referer information. 5.) Please elaborate. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=201716&aid=708317&group_id=1716 ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf