Counter

[cheval]

I cannot get my web counter to work. Every time I try to create a counter, I get the following error message in IE when its uploaded:

 

"Could not write to counter file: var/cpanel/counters/countername.dat"

 

I have tried naming the counter differently, making sure that I do not use .dat after the name, and that does not work either. I followed directions that I found in the forums, but nothing works.

[Lianna]

Has your domain name propogated yet? I mean, can you access your site via your domain name vs. IP address?

 

If not, the counter may not work. What's the url where we can find the counter you've placed?

 

Lianna

[cheval]

My website is: http://www.historique.net

 

It is, to my knowledge, fully available. I placed the counter on the main page, but removed it when the error appeared.

[mountaindew]

Drop us a help ticket and i will get it fixed asap for you.

[welshwizard]

Cheval, I had the same problem.

 

Go to the HTML code itself and remove the

 

.dat

 

from the middle.

 

This worked perfectly for me

[cheval]

Thanks welshwizard!

 

I removed the .dat from the html code and everything works great!

 

[jrogers7]

Hmmmm... I deleted ".dat" and the counter still didn't appear. Can one of you folks post a link to your web site so I can view your source to see if anything else is different. Here's what I have in mine:

 

<imgsrc="/cgi-sys/Count.cgi?df=jrogers7|display=Counter|ft=6|md=5|frgb=100;139;216|dd=C">

 

I noticed that cheval had the image as part of a table. Can't I just drop the code in the body section of the html?

 

nm, just figured it out - needed a space between img and src

 

Thanks

[dale]

All,

 

I had the exact same problem with the cpanel counter script. What was odd about it was that the HTML code as supplied by the cpanel counter-maker worked when I viewed my page via IP/~username (which is how one sees their page before the DNS has propagated), but didn't work (i.e., gave the error message "Could not write to counter file...") when accessed via the URL, even after DNS propagation was complete.

 

I dropped the ".dat" from the code snippet, as many have suggested, and now the problem is exactly reversed: It works fine when addressed as http://PIC-an-LCD.com, but not when accessed via IP/~username. Of course, this is much preferrable, as the world at large is going to find my page via the published URL.

 

It's still a head-scratcher, though.

 

Thanks,

 

Dale