Test of a faster redirect when a countdown is already expired.
T(-) Countdown Control already has the ability to store a visitors calculated launch time to a cookie. As of version 1.7.7 we have added integration of a new add-on plugin T(-) Countdown Tracking. This new premium plugin adds the ability to save the visitors IP address in the database. More details to follow.
Test using Schedule:
Test using basic shortcode:
[tminus t="+2 minutes" id="test_counter" track_id="2571" /]
This is a test of the cloud-city style for T(-) Countdown to adjust the spacing issue on lower viewports.
This countdown should launch Monday-Friday at 09:00 and 12:00 and certainly NOT on the weekend.
What happens when we display two of the exact same T(-) Countdown Control shortcodes on the same page?
Here is the first countdown:
and Here is the second:
[tminus cid="2022" id="secondcountdown"]
Way to omit weeks from the countdown:
a) Add the omitweeks=”true” attribute to your shortcode (if using a shortcode)
b) tick the omitweeks box in the widget settings (if using a sidebar widget)
c) tick the omitweeks box in the T(-) Countdown Control options page.
This is a test of a countdown that only launches Monday to Friday… excluding Weekends.
Introducing a new shortcode for T(-) Countdown Control that will print out the launch date:
[tminus_launch_date cid=”1921″ format=”Y-m-d”]
[[tminus_launch_date cid="1921" format="Y-m-d"]]
It can also be used inside the countdown it’s self.
Here it is: