[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fadge0E9GFCxtLPs0OUJ5nJRzcO4RtRqju8tj2yjw0s0":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":14,"last_updated":15,"tested_up_to":16,"requires_at_least":17,"requires_php":18,"tags":19,"homepage":24,"download_link":25,"security_score":13,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28,"vulnerabilities":29,"developer":30,"crawl_stats":27,"alternatives":34,"analysis":126,"fingerprints":169},"wp-server-date-time","WP Server Date Time","0.5","dhruwal","https:\u002F\u002Fprofiles.wordpress.org\u002Fdhruwal\u002F","\u003Cp>This plugin is useful when you want to know what date time & timezone is it on server where wordpress is hosted if you are in other timezone.\u003Cbr \u002F>\nOutput looks like:\u003C\u002Fp>\n\u003Cp>Server Date\u002FTime: Thu 01st Jan, 2025 11:10 am\u003Cbr \u002F>\nServer Timezone: America\u002FPhoenix, (MST -07:00)\u003C\u002Fp>\n\u003Cp>Version Change log:\u003C\u002Fp>\n\u003Cp>v0.5\u003Cbr \u002F>\nSupports upto WordPress 3.7.1\u003C\u002Fp>\n\u003Cp>v0.4\u003Cbr \u002F>\nSupports upto WordPress 3.6\u003C\u002Fp>\n\u003Cp>v0.3\u003Cbr \u002F>\nMinimize css code\u003Cbr \u002F>\nSupports upto WordPress 3.5.1\u003C\u002Fp>\n\u003Cp>v0.2\u003Cbr \u002F>\nAdded description before date time\u003Cbr \u002F>\nAdded timezone information\u003Cbr \u002F>\nChanged text color from red to green\u003C\u002Fp>\n\u003Cp>v0.1\u003Cbr \u002F>\nInitial release\u003C\u002Fp>\n","This plugin shows the server local current date time & timezone in the upper right of your admin screen on every page.",70,5149,100,1,"2026-01-03T11:42:00.000Z","6.9.4","2.6","",[20,21,22,23],"date","server","time","timezone","http:\u002F\u002Fwww.dhruwal.com\u002Fwp-server-date-time\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-server-date-time.0.5.zip",0,null,"2026-03-15T15:16:48.613Z",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":14,"total_installs":11,"avg_security_score":13,"avg_patch_time_days":31,"trust_score":32,"computed_at":33},30,94,"2026-04-04T06:45:51.216Z",[35,57,73,92,109],{"slug":36,"name":37,"version":38,"author":39,"author_profile":40,"description":41,"short_description":42,"active_installs":43,"downloaded":44,"rating":45,"num_ratings":46,"last_updated":47,"tested_up_to":48,"requires_at_least":49,"requires_php":18,"tags":50,"homepage":54,"download_link":55,"security_score":56,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"blog-time","Blog Time","4.0.1","Scott Reilly","https:\u002F\u002Fprofiles.wordpress.org\u002Fcoffee2code\u002F","\u003Cp>This plugin adds a dynamic, functional clock to the admin bar (at top of all admin pages) to show the server time for the blog. The clock automatically updates as time passes, as you would expect of a digital clock.\u003C\u002Fp>\n\u003Cp>This plugin also supports a static mode which puts a timestamp string at the top of all admin pages instead of the dynamic clock. This static admin time widget can be clicked to update the time in-place (without a page reload) to show the new current server time.\u003C\u002Fp>\n\u003Cp>Also provided is a “Blog Time” widget providing the same functionality as the admin widget, but for your sidebars. You may also utilize the plugin’s functionality directly within a theme template via use of the template tag \u003Ccode>c2c_blog_time()\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>NOTE: For the front-end widget, if the “Use dynamic clock?” configuration option is unchecked, this plugin generates a timestamp and NOT a clock. The time being displayed is the time of the page load, or if clicked, the time when the widget last retrieved the time. It won’t actively increment time on the display. By default the widget displays a dynamic clock that does increment time.\u003C\u002Fp>\n\u003Cp>This is most useful to see the server\u002Fblog time to judge when a time sensitive post, comment, or action would be dated by the blog (i.e. such as monitoring for when to close comments on a contest post, or just accounting for the server being hosted in a different timezone). Or, when used statically as a timestamp and not a clock, it can indicate\u002Fpreserve when the page was loaded.\u003C\u002Fp>\n\u003Cp>Thanks to \u003Ca href=\"https:\u002F\u002Fmomentjs.com\u002F\" rel=\"nofollow ugc\">Moment.js\u003C\u002Fa> for the JavaScript date handling library.\u003C\u002Fp>\n\u003Cp>Links: \u003Ca href=\"https:\u002F\u002Fcoffee2code.com\u002Fwp-plugins\u002Fblog-time\u002F\" rel=\"nofollow ugc\">Plugin Homepage\u003C\u002Fa> | \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fblog-time\u002F\" rel=\"ugc\">Plugin Directory Page\u003C\u002Fa> | \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fcoffee2code\u002Fblog-time\u002F\" rel=\"nofollow ugc\">GitHub\u003C\u002Fa> | \u003Ca href=\"https:\u002F\u002Fcoffee2code.com\" rel=\"nofollow ugc\">Author Homepage\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>Template Tags\u003C\u002Fh3>\n\u003Cp>The plugin provides one template tag for use in your theme templates, functions.php, or plugins.\u003C\u002Fp>\n\u003Ch4>Functions\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ccode>\u003C?php function c2c_blog_time( $time_format = '', $echo = true ) ?>\u003C\u002Fcode>\u003Cbr \u002F>\nReturns and\u002For displays the formatted time for the site.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Arguments\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Ccode>$time_format\u003C\u002Fcode> (string)\u003Cbr \u002F>\nOptional. PHP-style time format string. See https:\u002F\u002Fwww.php.net\u002Fmanual\u002Fen\u002Fdatetime.format.php for more info. Default is ” (which, unless otherwise modified, uses the default time forat: ‘g:i A’).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ccode>$echo\u003C\u002Fcode> (bool)\u003Cbr \u002F>\nOptional. Echo the template info? Default is true.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Examples\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Ccode>\u003C?php \u002F\u002F Output the site's current time.\u003Cbr \u002F>\nc2c_blog_time();\u003Cbr \u002F>\n?>\u003C\u002Fcode>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ccode>\u003C?php \u002F\u002F Retrieve the value for use in code, so don't display\u002Fecho it.\u003Cbr \u002F>\n$site_date = c2c_blog_time( 'M d, Y', false );\u003Cbr \u002F>\n?>\u003C\u002Fcode>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Hooks\u003C\u002Fh3>\n\u003Cp>The plugin exposes four filters for hooking. Code using these filters should ideally be put into a mu-plugin or site-specific plugin (which is beyond the scope of this readme to explain). Less ideally, you could put them in your active theme’s functions.php file.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>c2c_blog_time (filter)\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>The \u003Ccode>'c2c_blog_time'\u003C\u002Fcode> hook allows you to use an alternative approach to safely invoke \u003Ccode>c2c_blog_time()\u003C\u002Fcode> in such a way that if the plugin were deactivated or deleted, then your calls to the function won’t cause errors in your site.\u003C\u002Fp>\n\u003Cp>Arguments:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>same as for \u003Ccode>c2c_blog_time()\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Example:\u003C\u002Fp>\n\u003Cp>Instead of:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003C?php c2c_blog_time(); ?>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Do:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003C?php echo apply_filters( 'c2c_blog_time', '' ); ?>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>c2c_blog_time_format (filter)\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>The \u003Ccode>'c2c_blog_time_format'\u003C\u002Fcode> hook allows you to customize the default format for the blog time. By default this is ‘g:i A’ (though this may be different if modified by localization).\u003C\u002Fp>\n\u003Cp>Arguments:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>$format (string): The default format for the blog time.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Example:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F**\n * Change the default blog time string\n *\n * @param string $format The default time format.\n * @return string\n *\u002F\nfunction change_blog_time_format( $format ) {\n    return 'b, g:i A';\n}\nadd_filter( 'c2c_blog_time_format', 'change_blog_time_format' );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>c2c_blog_time_toolbar_widget_for_user (filter)\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>The \u003Ccode>c2c_blog_time_toolbar_widget_for_user\u003C\u002Fcode> hook allows you to control if the admin toolbar clock widget should be shown, on a per-user basis. By default the admin toolbar clock is shown to everyone who can see the admin toolbar.\u003C\u002Fp>\n\u003Cp>Arguments:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>$shown (boolean): Whether the admin toolbar clock widget should be shown. Default of true.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Example:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F**\n * Only show the admin toolbar clock for the 'boss' user.\n *\n * @param $show bool Status of whether the admin toolbar clock should be shown.\n * @return bool\n *\u002F\nfunction restrict_blog_time_widget_appearance( $show ) {\n    return 'boss' === get_current_user()->user_login;\n}\nadd_filter( 'c2c_blog_time_toolbar_widget_for_user', 'restrict_blog_time_widget_appearance' );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>c2c_blog_time_active_clock (filter)\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>The \u003Ccode>'c2c_blog_time_active_clock'\u003C\u002Fcode> hook returns the boolean value indicating if the Javascript-powered dynamic clock introduced in v2.0 should be enabled or if instead the v1.x era behavior of a static timestamp that can be clicked to update the timestamp via AJAX should be enabled. By default the dynamic clock is enabled.\u003C\u002Fp>\n\u003Cp>Arguments:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>$allow (boolean): Boolean indicating if the admin widget should be a dynamic clock. Default is true.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Example:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F\u002F Disable the dynamic clock and use the static timestamp (whcih can be clicked to update the time via AJAX) instead.\nadd_filter( 'c2c_blog_time_active_clock', '__return_false' );\n\u003C\u002Fcode>\u003C\u002Fpre>\n","Display the time according to your blog via an admin toolbar widget, a sidebar widget, and\u002For a template tag.",600,25105,72,8,"2021-07-29T08:59:00.000Z","5.8.13","4.6",[51,52,53,21,22],"blog","clock","datetime","https:\u002F\u002Fcoffee2code.com\u002Fwp-plugins\u002Fblog-time\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fblog-time.4.0.1.zip",85,{"slug":58,"name":59,"version":60,"author":61,"author_profile":62,"description":63,"short_description":64,"active_installs":65,"downloaded":66,"rating":26,"num_ratings":26,"last_updated":67,"tested_up_to":68,"requires_at_least":69,"requires_php":18,"tags":70,"homepage":71,"download_link":72,"security_score":56,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"current-date-time-widget","Current Date & Time Widget","1.0.3","Chris Jean","https:\u002F\u002Fprofiles.wordpress.org\u002Fchrisjean\u002F","\u003Cp>This is a fairly simple plugin used to display the date and time in any widget-enabled location.\u003C\u002Fp>\n\u003Cp>There were two goals for this plugin:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Provide a means to have the date and time produced match a specific timezone.\u003C\u002Fli>\n\u003Cli>Enable complete customization over how the date and time is formatted.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>I think that I’ve done a fairly good job of meeting those goals. Admittedly, setting either field is fairly user-unfriendly. The timezone specified must match \u003Ca href=\"http:\u002F\u002Fus3.php.net\u002Ftimezones\" rel=\"nofollow ugc\">PHP’s List of Supported Timezones\u003C\u002Fa>. The date and time format has the same requirements as the format parameter of \u003Ca href=\"http:\u002F\u002Fus.php.net\u002Fdate\" rel=\"nofollow ugc\">PHP’s date() function\u003C\u002Fa> (for obvious reasons since the defined format is actually passed directly to the date function in the code 🙂 ).\u003C\u002Fp>\n\u003Cp>If this plugin gets enough attention and use, I’ll find ways of easing the use. I think a series of drop-downs would make selecting the options easier, so that would be the option used if people are interested. If you happen to be one of those interested people, please send me a message on our \u003Ca href=\"http:\u002F\u002Frealthemes.com\u002Fcontact-us\u002F\" rel=\"nofollow ugc\">contact page\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Version History\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>1.0.1 – 2008-06-04 – Basic proof of concept\u003C\u002Fli>\n\u003Cli>1.0.2 – 2008-06-12 – Contained plugin code inside a class to prevent namespace collisions. Standardized code with coding style (http:\u002F\u002Fcomox.textdrive.com\u002Fpipermail\u002Fwp-hackers\u002F2006-July\u002F006930.html)\u003C\u002Fli>\n\u003Cli>1.0.3 – 2008-07-01 – Added support for PHP 4\u003C\u002Fli>\n\u003C\u002Ful>\n","Provides a widget that shows the current date and time given a specified timezone and format.",200,23173,"2008-07-02T02:25:00.000Z","2.5.1","2.3",[20,22,23],"http:\u002F\u002Fblog.realthemes.com\u002F2008\u002F06\u002Fcurrent-date-time-widget\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcurrent-date-time-widget.1.0.3.zip",{"slug":74,"name":75,"version":76,"author":77,"author_profile":78,"description":79,"short_description":80,"active_installs":81,"downloaded":82,"rating":26,"num_ratings":26,"last_updated":83,"tested_up_to":84,"requires_at_least":85,"requires_php":86,"tags":87,"homepage":90,"download_link":91,"security_score":56,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"cc-server-time","CC-Server-Time","1.0.0","Clearcode","https:\u002F\u002Fprofiles.wordpress.org\u002Fclearcodehq\u002F","\u003Cp>This plugin adds a server time to all posts types edit screen.\u003C\u002Fp>\n","This plugin adds a server time to all posts types edit screen.",10,1808,"2018-06-13T13:27:00.000Z","4.9.29","4.9.6","7.0",[20,88,89,21,22],"pages","posts","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcc-server-time","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcc-server-time.zip",{"slug":93,"name":94,"version":95,"author":96,"author_profile":97,"description":98,"short_description":99,"active_installs":81,"downloaded":100,"rating":13,"num_ratings":14,"last_updated":101,"tested_up_to":102,"requires_at_least":18,"requires_php":18,"tags":103,"homepage":107,"download_link":108,"security_score":56,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"display-timezone","Display Time(zone)","1.0.6","Midhun Devasia","https:\u002F\u002Fprofiles.wordpress.org\u002Fmidhund\u002F","\u003Cp>\u003Ca href=\"http:\u002F\u002Fgithub.com\u002Fmidhundevasia\u002Fwp-display-timezone\u002F\" rel=\"nofollow ugc\">Display Timezone\u003C\u002Fa> is simple plug-in to display current time with timezone in the upper right of your admin screen on every page. It takes the values from the option Timezone, Date Format, Time Format and starts the clock. There is no configuration page.\u003C\u002Fp>\n\u003Ch4>When you going to use\u003C\u002Fh4>\n\u003Cp>If your wordpress site is hosted at London and you are from China, both time are diffrent. You get confused while schedule the post and other events related to time. If you look at your machine its shows your time, not the server time. Here you can use the plugin. ie The Plugin Shows your server time, not the machine time or browser time.\u003C\u002Fp>\n","Display Timezone is simple plug-in to display current time with timezone in the upper right of your admin screen on every page.",4663,"2016-11-08T18:53:00.000Z","4.6.30",[104,52,105,106,23],"admin","servertime","timer","http:\u002F\u002Fgithub.com\u002Fmidhundevasia\u002Fwp-display-timezone\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdisplay-timezone.zip",{"slug":110,"name":111,"version":112,"author":113,"author_profile":114,"description":115,"short_description":116,"active_installs":81,"downloaded":117,"rating":118,"num_ratings":119,"last_updated":120,"tested_up_to":121,"requires_at_least":122,"requires_php":18,"tags":123,"homepage":124,"download_link":125,"security_score":56,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"wp-user-timezone","WP User Timezone","1.0.2","Ravi Kiran Katha","https:\u002F\u002Fprofiles.wordpress.org\u002Fravikatha\u002F","\u003Cp>WordPress has a site-level timezone setting configured from the admin back-end. All dates and times displayed on the front-end are typically displayed in this timezone.\u003C\u002Fp>\n\u003Cp>This plugin enables the display of dates\u002Ftimes in the front-end using the browser’s timezone. This is done by overriding the WordPress’s \u003Cstrong>‘timezone_string’\u003C\u002Fstrong> and \u003Cstrong>‘gmt_offset’\u003C\u002Fstrong> options to match the user’s timezone \u003Cstrong>for the duration of a particular request\u003C\u002Fstrong>\u003Cbr \u002F>\n\u003Cstrong>ONLY on the front-end interface\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Ch4>Browser Timezone Detection\u003C\u002Fh4>\n\u003Cp>The browser’s timezone is detected using one of the following two methods\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Ca href=\"http:\u002F\u002Fpellepim.bitbucket.org\u002Fjstz\u002F\" rel=\"nofollow ugc\">jsTimezoneDetect\u003C\u002Fa> (default)\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"http:\u002F\u002Fcaniuse.com\u002Fgeolocation\" rel=\"nofollow ugc\">HTML5 Geolocation API\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Fdevelopers.google.com\u002Fmaps\u002Fdocumentation\u002Ftimezone\" rel=\"nofollow ugc\">Google Timezone API\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>\u003Cstrong>jsTimezoneDetect (default)\u003C\u002Fstrong>\u003Cbr \u002F>\n    This is the default timezone detection mechanism. Please refer to the script \u003Ca href=\"http:\u002F\u002Fpellepim.bitbucket.org\u002Fjstz\u002F\" rel=\"nofollow ugc\">home page\u003C\u002Fa>\u003Cbr \u002F>\nfor the compatibility and other notes\u003C\u002Fp>\n\u003Cp>\u003Cstrong>HTML5 Geolocation API\u003C\u002Fstrong>\u003Cbr \u002F>\n    Detects the current geo-location using \u003Cem>\u003Ca href=\"http:\u002F\u002Fcaniuse.com\u002Fgeolocation\" rel=\"nofollow ugc\">navigator.geolocation.getCurrentPosition\u003C\u002Fa>\u003C\u002Fem>. The location thus detected will be sent to the \u003Ca href=\"https:\u002F\u002Fdevelopers.google.com\u002Fmaps\u002Fdocumentation\u002Ftimezone\" rel=\"nofollow ugc\">Google Timezone API\u003C\u002Fa>\u003Cbr \u002F>\nwhich returns the timezone id – similar to “Asia\u002FKolkata”.\u003C\u002Fp>\n\u003Cp>This method requires you to\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Enable the “Google Timezone API” option on the plugin options page\u003C\u002Fli>\n\u003Cli>Specify a valid \u003Ca href=\"https:\u002F\u002Fdevelopers.google.com\u002Fmaps\u002Fdocumentation\u002Ftimezone\u002Fget-api-key\" rel=\"nofollow ugc\">Google API Key\u003C\u002Fa>\n\u003Cul>\n\u003Cli>The key should be a browser key\u003C\u002Fli>\n\u003Cli>The “Accepted HTTP Referrers” should include the domain name used by the hosting wordpress site or left blank to allow all referrers\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>If the required options for the usage of Google Timezone API are not met, the detection mechanism falls back to the default one.\u003C\u002Fp>\n\u003Ch4>Post Timezone Detection\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>If the browser’s timezone id is not detected successfully, everything else behaves as if this plugin is not installed.\u003C\u002Fli>\n\u003Cli>If the browser’s timezone id is detected, the following actions take place\n\u003Cul>\n\u003Cli>A cookie will be set in the browser, based on the cookie options specified on the plugin options page\u003C\u002Fli>\n\u003Cli>If a cookie already exists previously with the same id, no action is taken\u003C\u002Fli>\n\u003Cli>If a cookie doesn’t already exist previously or exists with a different timezone id, then a \u003Cem>window.reload\u003C\u002Fem> is triggered to refresh the page so that the dates\u002Ftimes on the page are updated\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>EventON Hook\u003C\u002Fh4>\n\u003Cp>This plugin provides a feature to hook into the EventON plugin. When enabled, all EventON dates\u002Ftimes are updated to reflect the browser’s timezone.\u003C\u002Fp>\n\u003Ch4>Shortcodes\u003C\u002Fh4>\n\u003Cp>This plugin defines the below shortcodes\u003C\u002Fp>\n\u003Col>\n\u003Cli>[wp_user_timezone_id] => Returns the timezone id of the browser or \u003Cem>null\u003C\u002Fem> if not available.\u003C\u002Fli>\n\u003Cli>[wp_user_timezone_offset] => Returns the timezone’s gmt offset in hours of the browser or \u003Cem>null\u003C\u002Fem> if not available.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Options\u003C\u002Fh4>\n\u003Cp>This plugin defines the below options to retrieve the original timezone_string and gmt_offset defined at the site level\u003C\u002Fp>\n\u003Col>\n\u003Cli>get_option( ‘site_timezone_string’ ) => Returns the original timezone_string option for the site\u003C\u002Fli>\n\u003Cli>get_option( ‘site_gmt_offset’ ) => Returns the original gmt_offset option for the site\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Actions\u002FHooks\u003C\u002Fh4>\n\u003Cp>This plugin defines the below filters\u002Fhooks\u003C\u002Fp>\n\u003Col>\n\u003Cli>apply_filters( ‘wp_user_timezone_id’, $tz_id ) => Allows you to override the timezone string determined by the plugin. This filter can be used to apply user’s timezone preference. If any plugin or wordpress core implements a feature to accept and store user’s preferred timezone, the ‘wp_user_timezone_id’ can be used to apply that timezone value to the front-end. Reference: \u003Ca href=\"https:\u002F\u002Fcore.trac.wordpress.org\u002Fticket\u002F18146\" rel=\"nofollow ugc\">Add user-level timezone setting\u003C\u002Fa>).\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Admin Backend Dates\u002FTimes\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>Important: The admin back-end is not modified by this plugin. All dates\u002Ftimes displayed in the back-end are still in the original timezone specified by the WordPress General Settings.\u003C\u002Fstrong>\u003C\u002Fp>\n","WP User Timezone displays the front-end dates & times in the browser's local timezone without actually modifying your database.",2228,60,4,"2016-05-07T07:05:00.000Z","4.5.33","3.0.1",[20,22,23],"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-user-timezone\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-user-timezone.zip",{"attackSurface":127,"codeSignals":143,"taintFlows":156,"riskAssessment":157,"analyzedAt":168},{"hooks":128,"ajaxHandlers":139,"restRoutes":140,"shortcodes":141,"cronEvents":142,"entryPointCount":26,"unprotectedCount":26},[129,135],{"type":130,"name":131,"callback":132,"file":133,"line":134},"action","admin_notices","get_server_date_time","wp-server-date-time.php",21,{"type":130,"name":136,"callback":137,"file":133,"line":138},"admin_head","server_date_time_css",38,[],[],[],[],{"dangerousFunctions":144,"sqlUsage":145,"outputEscaping":147,"fileOperations":26,"externalRequests":26,"nonceChecks":26,"capabilityChecks":26,"bundledLibraries":155},[],{"prepared":26,"raw":26,"locations":146},[],{"escaped":26,"rawEcho":148,"locations":149},2,[150,153],{"file":133,"line":151,"context":152},16,"raw output",{"file":133,"line":154,"context":152},29,[],[],{"summary":158,"deductions":159},"The wp-server-date-time plugin v0.5 presents a generally good security posture based on the static analysis. The absence of direct entry points like AJAX handlers, REST API routes, and shortcodes, along with zero recorded vulnerability history, suggests a low risk of common exploitation vectors. The plugin also demonstrates good practices by using prepared statements for any potential SQL queries, though none were detected, and by not performing file operations or external HTTP requests. This minimal attack surface and lack of historical vulnerabilities are positive indicators.\n\nHowever, a significant concern arises from the output escaping analysis. With two total outputs and 0% properly escaped, there is a clear risk of Cross-Site Scripting (XSS) vulnerabilities. Any data that the plugin displays to users, especially if it originates from user input or external sources (though none were found to be directly processed), could be manipulated to execute malicious scripts in the user's browser. Furthermore, the complete absence of nonce and capability checks, while not directly exploitable given the limited attack surface, indicates a lack of robust security hardening that could become an issue if the plugin were to expand its functionality or if new entry points were introduced in the future.\n\nIn conclusion, while the plugin's current minimal functionality and lack of historical issues are strengths, the unescaped output is a critical weakness that needs immediate attention. The absence of authentication checks, while not currently problematic, represents a potential future risk. The plugin is straightforward and seems to handle its limited scope well, but the XSS vulnerability is a significant oversight.",[160,163,166],{"reason":161,"points":162},"Unescaped output detected",7,{"reason":164,"points":165},"Missing nonce checks",3,{"reason":167,"points":165},"Missing capability checks","2026-03-16T21:36:53.123Z",{"wat":170,"direct":175},{"assetPaths":171,"generatorPatterns":172,"scriptPaths":173,"versionParams":174},[],[],[],[],{"cssClasses":176,"htmlComments":178,"htmlAttributes":179,"restEndpoints":180,"jsGlobals":181,"shortcodeOutput":182},[177],"server-date-time",[],[],[],[],[183,184],"\u003Cp id='server-date-time'>\u003Cstrong>Server Date\u002FTime:\u003C\u002Fstrong>","\u003Cbr\u002F>\u003Cstrong>Server Timezone:\u003C\u002Fstrong>\u003C\u002Fp>"]