i have no problems with banners beside timers, except for the 'pay me right now' one. because it takes such a long time to load, my timer can take over two minutes....i generally just refresh the page, but sheesh....
please if you design a banner, at least keep the size DOWN! preferably under 100kb, and it will load quicker and not hold the timers up! and at the end of the day, banners are supposed to be seen.
Full Version: Banners and Timers
Any banners that seem to take forever to load on my pc...I will hit the stop button before they are loaded and then the timer will start. its a few extra seconds, but its worth it than waiting over 2 minutes for the banner to load then the timer to start.
Hello,
I own TrafficThatEarns and some of my members emailed me concerning this problem.
I have solved the issue and am sure my solution would also solve most other owners problems as well.
In the surf bar script most scripts have something like this <body onload="timer(15,15)">
*timer is the name of the function that calls the counter.
By simply removing the timer(15,15) function from the onload and place it inside the page itself will solve this problem.
The reason it happens because the onload feature means the script will not call the function until the page is finished loading.
Hope this helps other WMs. Members feel free to email the WMs this solution.
I own TrafficThatEarns and some of my members emailed me concerning this problem.
I have solved the issue and am sure my solution would also solve most other owners problems as well.
In the surf bar script most scripts have something like this <body onload="timer(15,15)">
*timer is the name of the function that calls the counter.
By simply removing the timer(15,15) function from the onload and place it inside the page itself will solve this problem.
The reason it happens because the onload feature means the script will not call the function until the page is finished loading.
Hope this helps other WMs. Members feel free to email the WMs this solution.
QUOTE (doobster @ May 30 2003, 08:22 PM)
Hello,
I own TrafficThatEarns and some of my members emailed me concerning this problem.
I have solved the issue and am sure my solution would also solve most other owners problems as well.
In the surf bar script most scripts have something like this <body onload="timer(15,15)">
*timer is the name of the function that calls the counter.
By simply removing the timer(15,15) function from the onload and place it inside the page itself will solve this problem.
The reason it happens because the onload feature means the script will not call the function until the page is finished loading.
Hope this helps other WMs. Members feel free to email the WMs this solution.
I own TrafficThatEarns and some of my members emailed me concerning this problem.
I have solved the issue and am sure my solution would also solve most other owners problems as well.
In the surf bar script most scripts have something like this <body onload="timer(15,15)">
*timer is the name of the function that calls the counter.
By simply removing the timer(15,15) function from the onload and place it inside the page itself will solve this problem.
The reason it happens because the onload feature means the script will not call the function until the page is finished loading.
Hope this helps other WMs. Members feel free to email the WMs this solution.
i'm not a member of your program, but it's nice that you tried to fix it
QUOTE (doobster @ May 31 2003, 11:22 AM)
Hello,
I own TrafficThatEarns and some of my members emailed me concerning this problem.
I have solved the issue and am sure my solution would also solve most other owners problems as well.
In the surf bar script most scripts have something like this <body onload="timer(15,15)">
*timer is the name of the function that calls the counter.
By simply removing the timer(15,15) function from the onload and place it inside the page itself will solve this problem.
The reason it happens because the onload feature means the script will not call the function until the page is finished loading.
Hope this helps other WMs. Members feel free to email the WMs this solution.
I own TrafficThatEarns and some of my members emailed me concerning this problem.
I have solved the issue and am sure my solution would also solve most other owners problems as well.
In the surf bar script most scripts have something like this <body onload="timer(15,15)">
*timer is the name of the function that calls the counter.
By simply removing the timer(15,15) function from the onload and place it inside the page itself will solve this problem.
The reason it happens because the onload feature means the script will not call the function until the page is finished loading.
Hope this helps other WMs. Members feel free to email the WMs this solution.
Wish everyone was as thoughful.. as you ...
Love,
Simz
QUOTE (indreams @ May 31 2003, 05:50 PM)
QUOTE (doobster @ May 30 2003, 08:22 PM)
Hello,
I own TrafficThatEarns and some of my members emailed me concerning this problem.
I have solved the issue and am sure my solution would also solve most other owners problems as well.
In the surf bar script most scripts have something like this <body onload="timer(15,15)">
*timer is the name of the function that calls the counter.
By simply removing the timer(15,15) function from the onload and place it inside the page itself will solve this problem.
The reason it happens because the onload feature means the script will not call the function until the page is finished loading.
Hope this helps other WMs. Members feel free to email the WMs this solution.
I own TrafficThatEarns and some of my members emailed me concerning this problem.
I have solved the issue and am sure my solution would also solve most other owners problems as well.
In the surf bar script most scripts have something like this <body onload="timer(15,15)">
*timer is the name of the function that calls the counter.
By simply removing the timer(15,15) function from the onload and place it inside the page itself will solve this problem.
The reason it happens because the onload feature means the script will not call the function until the page is finished loading.
Hope this helps other WMs. Members feel free to email the WMs this solution.
i'm not a member of your program, but it's nice that you tried to fix it
very nice! - it's wm's that listen that make all the difference
let's hope some wm's do take that advice
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.