kwikone

Yes, for me it is very useful in that I do not have to remember all the various short codes in the several blog sites I am the webmaster for.
Also, I have found what the problem is. It is caused by an extra space between Version and the colon
it is: * Version :
it should be: * Version:
Although what I did was also remove the * from the start of all the secondary comment lines to have
/*
comment lines including the version line
*/

Bart, I left this unresolved for you to mark when you correct your source. (You should also bump the version when you do so everyone can be updated)

On my wish list is to have the ability to display not just the days, or hours, or minutes or seconds to go. Would like to have an option to display any combination – such as days and hours, or days – hours and minutes

Question: Which article/posting is it supposed to get the timer info from?
Is is supposed to get the timer info from the currently displayed posting? What about when it is at the home where it is a list of multiple postings?
Next, in order to put it in your header you would have to insert PHP code to display the timer and the answers to the above are necessary in order for someone to be able to help you.

If you look at: this one there is the fix that works for me.

Now the biggest problem is that it doers not show you the current settings for as post when you go to edit it which means you have to always re-enter it when editing a post.

I got it to work with the following patch(es)…

in live-countdown-timer.php (line 20):

REPLACE:
    $xDBArr = UNSERIALIZE(get_option('live_countdown_timer_Values'));
WITH:
    $xDBArr = get_option('live_countdown_timer_Values');

AND in calculateTimer.php (line 13):

REPLACE:
    $xTheDate = mktime($xFromDate[0],$xFromDate[1],$xFromDate[2],$xFromDate[3],$xFromDate[4],$xFromDate[5]);//$xFromDate
WITH:
    $xTheDate = mktime((int) $xFromDate[0],(int) $xFromDate[1],(int) $xFromDate[2],(int) $xFromDate[3],
			(int) $xFromDate[4],(int) $xFromDate[5]);//$xFromDate

I am marking this as resolved since it is now the correct version being downloaded now

BUT… it does not work!
I inserted a countdown timer in a post and when I viewed the post I got the following..
Warning: mktime() expects parameter 4 to be long, string given in blogs/wp-content/plugins/live-countdown-timer/calculateTime.php on line 7

and no timer was displayed

I followed the steps I previously did which was:
went to: https://www.ads-software.com/extend/plugins/live-countdown-timer/
clicked on the “Download Version 2.1.0.7” button
After the download completed I opened the zip file.

However… this time the file dates are 2010.
So, I tried the auto-update in my blog. IT WORKED!!! It now shows as 2.1.0.7.

The strangest part is why the auto-install downloaded 2.1.0.6 in the first place and auto-update and my own manual download ALL got 2.1.0.6 until now.

But, at least now it is the correct version

Well…
I just downloaded it and opened the zip file. All of the file dates are 2009-12-01 12:23 and in live-countdown-timer.php the version comment indicates 2.1.0.6.
It appears that even though on this site it indicates as 2.1.0.7 the file is actually 2.1.0.6 and that accounts for why the auto-update did not update to 2.1.0.7 and also why when I did the initial install (from my wordpress admin) it then showed an update was available immediately.

Hmmmm… I just installed it and did not get that error. What I get is …
Warning: mktime() expects parameter 4 to be long, string given in blogs/wp-content/plugins/live-countdown-timer/calculateTime.php on line 7

It also appears that what downloads and installs (automatic install/upgrade) is not 2.1.0.7 even though that is what wordpress tells me is the newest version.

When tried it out got the following PHP warning:
Warning: mktime() expects parameter 4 to be long, string given in blogs/wp-content/plugins/live-countdown-timer/calculateTime.php on line 7

AND NOTHING was shown for the timer

OOPS, forgot to mention… It does definitely appear as if the problem was in the tiny_mce_gzip.php as the new level (2.3) has massive changes and restructuring

The latest version 2.3 does resolve this problem

I have found that the problem is related to a javascript error. The error occurs within the initialization code for the compressed tinymce. The error is at: tinyMCE = realtinyMCE. It is almost as if the sequence of the compressed code being sent out is being sent in the wrong order because the error indicates that realtinyMCE is not an object.

AND, until the latest IE7 update it worked. BUT, now even IE7 fails (when I turned on script debugging I discovered the error).