Topic: Skim% from spiders 0% in TP Version 1.0.9 build 44 ?

[xxxtreme]

A couple of days ago, I updated a small site to the latest TP version  (1.0.9 build 44).
In the changelog you stated: "2) spiders are now sent 100% to content and not counted in case they go to trades - there is NO POINT to send them to trades - it kills effect values etc"

However, since I updated to this latest version, I noticed just the opposite: my 'spiders' skim% is 0% (instead of 100%)
And I did NOT change any of the settings related to spiders after running the update (Counted Clicks > Spiders: not marked and Specialized Out Settings > Spiders Traffic > To Content)

All this makes that that the skim% in the '24 Hours Site Totals' is only 37%
However, the average skim % to trades in the last 24h is 65%

Is there something I am overlooking or not understanding? Or is this a bug?
Thanks in advance for helping me out...

[allniche]

I've actually noticed this with version Version 1.0.8 build 43 too.  I have a special script which goes in front and handles the skim by passing along a "?p=100" or "?p=0" parameter to TP in order to give me more control.  Anyway It's supposed to ensure skim is 100% (to galleries) for nocookie and certain traffic.  But likewise I notice the stats also seemed to say each click was a trade click instead.

But I tested out the nocookie part and found indeed that the clicks were being sent to galleries.  It only looked like the stats were reporting they were going to trades but they really weren't from what I could tell.  The were actually going to galleries as I specified. YMMV.  Either way if this is the case it looks like a bug of some sort?

[ip0li]

It is just display issue guys, all is fine don't worry

[oil]

It is just display issue guys, all is fine don't worry

well sure its a display issue but it screws up the return stats badly

[ip0li]

It doesn't if checkbox is unselected. As in previous thread please send me access to your tp!

[oil]

sorry my fault checked only at networks stats, and there it was still counted, hence i thought it would be on single tp as well
but since networks stats are completly wrong anyways i should have taken a close look

[ip0li]

its our fault
will be solved, stay tuned.