support for statcounter.com

[ltobias]

As soon as you hit the Update button, statcounter will be active.
You could see the statcounter code appearing at the bottom of your galleries and image pages if you were to view the page html.

Support for Google Analytics, and ExtremeTracker will follow.

-Slug

Doesn't work for me. I added my statscounter information at my account page:

25448 (project)
0 (partition)
blank (security)

and hit update. But it doesn't work. There is also no information in my source of the gallery website.

Here are the information from statscounter:

var sc_project=254448;
var sc_partition=0;
var sc_security="";

Any ideas?

Leif

[slug]

Honestly I'm getting tired of hearing accusations that we don't care about your hard work or the trouble caused by the change to javascript.

Of course we care.

In this case, the stopping of javascript was not done at a whim because we felt like annoying everyone. We had no choice but to stop javascript in order to prevent a very real and serious cross-site scripting vulnerability.

Now that we've made the change, we're working as hard and as fast as we can to create ways to provide the same or improved functionality as you had before.
We've already implemented improved support for statcounter. Support for slideshows and other statistics services will be following soon.

Next, we can address other features as we became aware of them.
Someone mentioned using javascript to help with adding items to a shopping cart. There's probably something we can do here that will make an easier solution than there was before by making the process even easier than it was before.

Vague complaints about loss of functionality won't help us fix the problem.
We just need to hear specific feature requests from you.

-Slug

[slug]

ltobias -
The partition and security number need to be filled in.
You can get these values by going to statscounter.com and using their Install Code feature. After going through their step by step choices, you will be shown the code. In that code, you'll see the values for project,security and partition. Use these values on the PBase account settings page.

arjun -
I believe that's what the partition is for. It's their own form of load balancing.
Note that that c28 is your partition number + 1. When you get the code from them, look at it and you'll see the c28 there too.

-Slug

[ltobias]

ltobias -
The partition and security number need to be filled in.
You can get these values by going to statscounter.com and using their Install Code feature. After going through their step by step choices, you will be shown the code. In that code, you'll see the values for project,security and partition. Use these values on the PBase account settings page.

Thank you for your fast reply.

My partion is 0 and I don't have a security number. Here is my code from statscouner "Install code":

<!-- Start of StatCounter Code -->
<script type="text/javascript" language="javascript">
var sc_project=254448;
var sc_invisible=0;
var sc_partition=0;
var sc_security="";
</script>

<script type="text/javascript" language="javascript" src="http://www.statcounter.com/counter/counter.js"></script><noscript><a href="http://www.statcounter.com/" target="_blank"><img src="http://c1.statcounter.com/counter.php?sc_project=254448&amp;java=0&amp;security=&amp;invisible=0" alt="web metrics" border="0"></a> </noscript>
<!-- End of StatCounter Code -->


Leif

[slug]

ltobias -

Fixed. Thanks for pointing this out.
We had made the assumption that partition and security needed to be filled in. Apparently some statcounter accounts don't require those.
Maybe you have a very early statcounter account.

Anyway, your statcounter code is now showing up on your pages.

Thanks,
-slug

[andrys]

TO * SLUG * (and for existing statcounter users)

and to ctstone and Dang

Margaret wrote:

Will the general announcement regarding JS eventually disappear from our gallery view? I know it's only visible to us, but distracting nevertheless.

By removing the old codes in your descriptions, it's gone. Guess since we've installed manually, it's necessary to remove manually.

Slug and ctstone especially:
I just got back here after 8 hours away and was already happy that
Slug has been so responsive today to our concerns today and
implemented such a sweet solution for at least new Statcounter users.


QUESTIONS before I do more, after inputting the ID numbers

1. Slug mentioned to me this morning that he would -try- to automate
removal of existing Statcounter code today in existing-users' galleries,
IF the

<!-- Start of StatCounter Code -->
and
<!-- End of StatCounter Code -->

were in our existing gallery description in a consistently
formatted way.

That's because some of us have well over 100 subgalleries using
the code. I have 150.

2. That was great to hear. But I think maybe Slug was considering
a separate action rather than this automagically happening when a
person fills in the ID #s in our account areas ?

3. So, is this still being considered, as a separate action ?

Slug mentioned he'd attempt to remove it if we activate
the new method and that he should be able to get most of it
if the formatting was consistent - it tends to be because we
just use statcounter's wording and paste it in.

I don't know if that was tried or if Slug is planning
a separate action we can choose.

4. Until I hear further, I'll just ignore the javascript warning-box
that comes up while the code is still in all those galleries.

5. Let us existing customers know though. That includes, from this
forum, Tim, Arjun, and my friends Margaret and Karen who recently
arduously added not-intuitive code to all galleries.

6. Your new Statcounter implementation, otherwise is just * EXCELLENT *
in that it worked *immediately* to get us information again.

7. And I am happy to see no statcounter counter, so the default for
'invisible counter' apparently is set to '1' by PBase.

8. The "remove link" option Statcounter requests from us
I've had set to '1' and I guess pbase's default is '1' ?

9. Slug mentioned in an email that the attempted old-script removal
"will not actually modify your gallery description text, the
counter code just won't be displayed when the page loads."

Please let us know if Slug is working on trying to remove
existing statcounter code in our galleries or if he gave up on the
idea.
I may try to reach him, but he's probably resting up after that trauma
and the ER treatment that saved the patient for sure.

THANKS!!! And also thanks for Slug's assurance given already that
the slideshow is definitely going to be in the works.

[andrys]

SLUG, you're up !

Thanks for watching after us.

SECURITY CODE etc. Some of us paying for statcounter accounts
to cover more pageloads needed. This also allows us to have
more flexibility with additional free project accounts.

It could be that the security code is used for us. I know that our
partition numbers are different from the free ones and that does have
to do with load balancing.

I mentioned in the note just previous that they also ask us re
the remove_link option too.

- Andrys

[ltobias]

ltobias -

Fixed. Thanks for pointing this out.
We had made the assumption that partition and security needed to be filled in. Apparently some statcounter accounts don't require those.
Maybe you have a very early statcounter account.

Anyway, your statcounter code is now showing up on your pages.

Thanks,
-slug

It's working again. Thank you for the fast help.

Leif

[pinemikey]

I for one, will give thanks for the Statcounter fix. It is actually much better than what I had before as I was reluctant to add the code to every gallery AND image page. I had implemented the code in a majority of galleries but I was hesitating anymore add-ons for the very reason of a future javascript freeze....which happened before. Now, I'm totally covered and much more info is pouring in.

Lets hope the fix is in for the slideshow as it really has a way to enhance our root galleries.

Thanks again, Pbase team!

[pinemikey]

Oops, I forgot one thing....would it be possible for the javascript for the personal Google search to allow users to search within our galleries?

[pinemikey]

Oops, I forgot one thing....would it be possible for the javascript for the personal Google search to allow users to search within our galleries?

Again, sorry...I should have checked it first. The Google search was working already.

[andrys]

Oops, I forgot one thing....would it be possible for the javascript for the personal Google search to allow users to search within our galleries?

Again, sorry...I should have checked it first. The Google search was working already.

Yah, it's just a form and google runs it. I will be interested to see what
happens with image stats since the statcounter code did not work
within image pages.
Already, our info runs off the log pretty fast even with info for last 500
pageloads allowed at any time for free users these days. And
Statcounter lets you download the logs too for use with external utilities
or just plain Excel.

From what I see, for the last two hours, the code reports entrances
and exits to galleries as before. Any image reports are when people
exit the image to go to another (or same) gallery.

Very useful in the drill-down though!

This is now a real boon for pbase users, who didn't before know
what great info you can get this way, and so easily now.

Thanks much, Slug & team.

[andrys]

Sorry, image reports also happen when a google-search for images lands
them on one our images.
But what we don't (thankfully) get is when people land and then go
from image to image. That would fill the stats. This way we do see if they
choose another gallery in addition.

[flemmingbo]

Thanks very much Slug !!

I understand your frustration as I work as head of an IT-department. What you can do though is try to provide as much info up front as possible to take the sting out of 'bad news' to the users.

This statcounter works brilliantly, what a great implementation of statcounter, and now it works on every single page incl images - actually a much better solution than before!

Thank you for quickly making this available!

[dang]

Slug wrote:

Vague complaints about loss of functionality won't help us fix the problem.
We just need to hear specific feature requests from you.

You might need to be aware, if you read Extreme Counters TOS, note they only allow free accounts to track one page only. At one time I was advised they weren't really concerned with sites having few hits, but adding accessibility from all of Pbase might be a problem. You may know this, but I thought it worth mentioning just in case.

Thanks again,
tom