Hallo @all,

after I have searched the issue for hours, I have found the problem in the "Javascript Countdown Timer"-module.
The problem was, that this module throws an error to drupal.js which could not handled and the whole execute of the file was stopped. So the counter could not continue, and all AJAX and AHAH funktions stopped, e.g. the collapsing of the filedsets.

The error was the translation of the sting "1 hour" to "1 Stunde" of the "Event"-module. This localization was used by the "Javascript Countdown Timer"-Timer in line 448:

var hours_str = Drupal.formatPlural(hours, "1 hour", "@count hours");

It would be nice to fix this problem, so that I can use the "Javascript Countdown Timer"-block on my website.

Regards
the-sandman

Comments

jvandervort’s picture

Which web browser, language(German?), and format string are you using?
I'm using firefox with German, but can't replicate the error with Countdown timer 6.x-2.21

Also, can you try removing the German po files from the countdowntimer/translations directory?

the-sandman’s picture

Yes, the language is German.
I have used Firefox, Opera and Internet Explorer to testing this issue, but the error is no occurred in Firefox, only in Opera and Internet Explorer. Perhaps Firefox ignore this issue?!?

I used the module togehter with "autologout"-module to logout user automatically after 1 hour.
When I set the logout-time to 3600 sec (1 hour) the error will be caused by the translation "1 hour" -> "1 Stunde" of the "Event"-Module. When I set the logout-time to 3599 sec (59 minutes and 59 seconds), no error will be caused. When I remove the translation of the event-module in the localization, no error will caused, too.

I think the error is in the line 448 of the file countdowntimer.module

var hours_str = Drupal.formatPlural(hours, "1 hour", "@count hours");

because the Drupal-function "format_plural()" contains the translation-function "t()".

I hope you can replicate the error now.

Regards the-sandman

jvandervort’s picture

Status: Active » Fixed

Committed fix in the Dec 3, 2009 6.x-2.x-dev snapshot.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.