| 开发者 | aacers |
|---|---|
| 更新时间 | 2026年5月6日 02:40 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
[gtg_time date="2025-12-25 15:00:00"] → December 25, 2025 at 3:00 PM (their local time)
[gtg_time date="2025-08-20 14:00:00" format="g:i A (T)"] → 4:00 PM (CEST)
Perfect for
[gtg_time] and [local_time] shortcodes/wp-content/plugins/ or install via WordPress.[gtg_time date="2025-12-25 15:00:00"] anywhere in your content, or use the "Local Time" Gutenberg block.Yes — Global Time Ghost was built specifically for cached sites. Times are rendered on the server in UTC, then localised in the visitor's browser via a tiny JavaScript snippet (~4 KB) and a cookie. WP Rocket, LiteSpeed, Cloudflare, SiteGround, Kinsta — all work flawlessly.
Yes. The browser reports the IANA timezone (e.g. Europe/Amsterdam) and PHP's DateTimeZone handles the DST math automatically.
No. The first render uses UTC; once the timezone cookie is set the displayed time updates instantly. Most users never notice — and the badge degrades gracefully even with JavaScript disabled.
Use the format attribute: [gtg_time date="2025-08-20 14:00:00" format="g:i A"]
Auto-conversion of plugin-managed dates (Events Calendar, WooCommerce, LearnDash, EDD) is a Pro feature. The free plugin works on any date you pass to the shortcode or block.
Locally — only the visitor's selected timezone is stored, and only in a first-party cookie (gtg_user_tz). Conversion counts are stored as anonymous totals in the WordPress options table. Nothing is sent to PluginJoy.
Add style="plain" to the shortcode: [gtg_time date="2025-08-20 14:00:00" style="plain"]