RESOLVED: html code for hidden counters are scrambling my site lay-out

[sessileoak]

Okay, a bit of a newby query maybe, but what the heck...
The code I've inserted for the invisible counters on my web pages have sent many of the images and links on my pages way off to the right, almost as though I'd inserted code for some much larger boxes where there is insufficient space. Also, a little blue "missing image" box (you know the one - with a question mark in it) has appeared where they are invisibly positioned on the page. Oddly, it was fine yesterday.

Has anyone else noticed this?

I think I can get it straightened out by positioning the two sets of code (one for the standard and the other for the SC4) either down at the bottom of the pages or over to the right. We'll see.

[sessileoak]

Aha, it's fixed now - thanks! :grin:

[sessileoak]

OOOPS!

No it aint - it's doing it again.

I seems pretty intermittent.
Is there any way of preventing this?

[sessileoak]

Alright... I think I've got it licked - for the most part.

The problem is undoubtedly with the beta counter as it sits within my site. The old standard counter sits fine. This I know because I've removed each from certain pages and observed the results.
The invisible beta counter regularly appears as a "missing picture" square and links back to the StatCounter site when clicked. When its in this state, the space required to accommodate it near any pictures or text boxes becomes elongated to around one third of the page width - much wider than the counter, as it would be if it were visible.
I've mostly been able to reposition the two counters (one directly above the other) at the bottom of each page and clear of anything to their right. On one page, I tried this at the top. Despite there being nothing to their right, the effect on the rest of the page contents was pretty similar - ie. various pictures and text boxes shifted way to the right. I can only surmise that it isn't a good idea to position the counters (invisible or not) too close to the top of any page.
On another page, I've had to ditch the beta counter altogether in order to keep the layout presentable, simply because there is insufficient space to take it at the bottom. Perhaps when I get my own server up and running to host my own (and associates) pages, this will be less of a problem - I hope.
The thing is, I'm not really a techie - I'm a carpenter - and I dread learning all the HTML stuff... now, if computers were made of wood...

[webado]

Modify this line in the javascript.

From:
var sc_invisible=0;

to:
var sc_invisible=1;

[sessileoak]

Thanks Christina, I will.

I've also been advised on good authority that the many errors in the html code for my page are bound to start adding up, to the point where they are likely to exacerbate otherwise minor problems. Not being an exponent of the art of htmling, I have to rely on the ISP's automated web building software. Fortunately, the good authority in question has given me a couple of useful pointers for me to start from (without messing things up too badly, I hope) - cheers Howard.

[Conny]

My beta counter did a good job the first few days but since a day or 3 to 4 the difference with the old one it shows a few hundred to a few thousand visitors less than the old counter!!!!
I compared it with Google Analytics which I also use for comparison. The old Statcounter was closer to Google totals and the new one was really not even close!

Today (Saturday) my entire site was messed up because all of a sudden the new script seems to want to show text; a sort of hidden image and hyperlink in every page. We wanted an invisible counter but alas.. We had to remove the beta counter script in order to keep measuring. The layout of a lot of pages was stretched (statcounter script used for 'alt')

Best thing I like are the new extras: the exit links and downloads!! I just hope you will be able to fix all bugs soon so we can use it without worries..

[howard]

- cheers Howard.

No problem.

The thing is, I'm not really a techie - I'm a carpenter - and I dread learning all the HTML stuff... now, if computers were made of wood...

My son's a carpenter. Says he now believes the old adage: "Measure twice, cut once."

For the benefit of others, here is the content of the PM I sent:

What others may or may not tell you but which I have found out on my own and had reaffirmed by others, is if the code on the page doesn't validate, there's a good chance any script (statcounter or other) will not work as it is supposed to. Often, coding errors compound themselves until something breaks.

Go to http://validator.w3.org/ and check it out. The best way I have found is to do it by file upload, where I have saved a local copy of the page on my desktop. Be sure to check all the frames in a frame set.

You can get a local copy of your content frame (not the top aol frame but your lower content frame) by using your aol site builder in code view (aol may call it something else) where you can edit the code, such as to add statcounter code. Select all you see, copy, then paste it into a newly created text document on your desktop, then change that text document's file extension to .html.

If you can't do that, copy the code as above, and select "by direct input" on the W3C site, and paste it there. As it is now, your content frame is loaded with validation errors. Even if they don't make your page un-viewable (modern browsers are very forgiving) they will cause trouble with statcounter from time to time.

[Tamas Kalman]

Hey,

you've absolutely right - and that's a really wise advice about your carpenter son :) Anyway, we've made a lot of modifications and I hope these problems all fixed now. We're really happy with your and other beta testers' work since you are the persons who are helping us testing and finding all the bugs and problems what we're unable to find all - especially in a short period of time. With your help we can make a better, high quality product so when we'll release SCv4 finally everybody can enjoy a highly stable, precise, fast & reliable product for all webmasters' benefit!
Thank you for the help,

regards,
Tamas Kalman

No problem.



My son's a carpenter. Says he now believes the old adage: "Measure twice, cut once."

For the benefit of others, here is the content of the PM I sent:

What others may or may not tell you but which I have found out on my own and had reaffirmed by others, is if the code on the page doesn't validate, there's a good chance any script (statcounter or other) will not work as it is supposed to. Often, coding errors compound themselves until something breaks.

Go to http://validator.w3.org/ and check it out. The best way I have found is to do it by file upload, where I have saved a local copy of the page on my desktop. Be sure to check all the frames in a frame set.

You can get a local copy of your content frame (not the top aol frame but your lower content frame) by using your aol site builder in code view (aol may call it something else) where you can edit the code, such as to add statcounter code. Select all you see, copy, then paste it into a newly created text document on your desktop, then change that text document's file extension to .html.

If you can't do that, copy the code as above, and select "by direct input" on the W3C site, and paste it there. As it is now, your content frame is loaded with validation errors. Even if they don't make your page un-viewable (modern browsers are very forgiving) they will cause trouble with statcounter from time to time.