[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fAdzue1K8mc8fWsGyRPHP0P92oHsftbyoYB7GLMR1nBw":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":25,"download_link":26,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30,"vulnerabilities":31,"developer":32,"crawl_stats":29,"alternatives":38,"analysis":139,"fingerprints":178},"wp-timezone","WP TimeZone","1.3","ezraverheijen","https:\u002F\u002Fprofiles.wordpress.org\u002Fezraverheijen\u002F","\u003Cp>This lightweight plugin can be used if the scheduled post feature is not working for you (missed scheduled post errors), and you host your site in a European country using CEST in the summer and CET during the winter.\u003C\u002Fp>\n","Takes care of publishing posts that missed their schedule, for CET\u002FCEST time zones only.",200,5709,60,2,"2015-08-17T09:59:00.000Z","4.2.39","3.1","",[20,21,22,23,24],"daylight-saving","time","time-zone","timezone","zone","http:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-timezone\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-timezone.1.3.zip",85,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":33,"total_installs":34,"avg_security_score":27,"avg_patch_time_days":35,"trust_score":36,"computed_at":37},4,11200,30,84,"2026-04-04T03:37:56.963Z",[39,59,76,100,123],{"slug":40,"name":41,"version":42,"author":43,"author_profile":44,"description":45,"short_description":46,"active_installs":47,"downloaded":48,"rating":28,"num_ratings":28,"last_updated":49,"tested_up_to":50,"requires_at_least":51,"requires_php":52,"tags":53,"homepage":56,"download_link":57,"security_score":58,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"time-zone-converter","Time Zone Converter","1.0.2","Vikas Sharma","https:\u002F\u002Fprofiles.wordpress.org\u002Fvikas4travel\u002F","\u003Cp>Time Zone Converter allows users to convert and compare time in different time zones.\u003Cbr \u002F>\nQuick and easy to use interface,  lets you convert time between major world cities and timezones.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Change widget appearance – change background color, font-size, text color etc according to your requirements.\u003C\u002Fli>\n\u003Cli>Increasing user engagement – the widget helps in increasing user engagement on your web page.\u003C\u002Fli>\n\u003Cli>Fully Responsive – works well on most screen sizes.\u003C\u002Fli>\n\u003Cli>Light weight and fast.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>What’s Next\u003C\u002Fh4>\n\u003Cp>If you find this plugin useful, please leave a good rating.\u003Cbr \u002F>\nYou can also provide us \u003Ca href=\"https:\u002F\u002Fwww.vikas4travel.com\u002F\" rel=\"nofollow ugc\">feedback here\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch4>Credits\u003C\u002Fh4>\n\u003Cp>This plugin is created by \u003Ca href=\"https:\u002F\u002Fwww.vikas4travel.com\" rel=\"nofollow ugc\">Vikas Sharma\u003C\u002Fa>.\u003C\u002Fp>\n","Time Zone Converter allows users to convert and compare time in different time zones.",80,1935,"2025-09-01T14:09:00.000Z","6.8.5","5.0","5.6",[54,40,55],"time-difference-calculator","timezone-converter","https:\u002F\u002Fwww.vikas4travel.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ftime-zone-converter.1.0.3.zip",100,{"slug":60,"name":61,"version":62,"author":63,"author_profile":64,"description":65,"short_description":66,"active_installs":35,"downloaded":67,"rating":58,"num_ratings":14,"last_updated":68,"tested_up_to":69,"requires_at_least":70,"requires_php":18,"tags":71,"homepage":74,"download_link":75,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"wp-utz","WP User Level Timezone","1.0.0","khill07","https:\u002F\u002Fprofiles.wordpress.org\u002Fkhill07\u002F","\u003Cp>WordPress displays all dates and times based on a site-level timezone setting configured in the admin back-end. The problem is when you user base handles people from all over the world date and times really don’t mean much any more.\u003C\u002Fp>\n\u003Cp>This plugin enables the user to select their own timezone and it handles the date and time conversion in both the front-end and admin section of the site.\u003C\u002Fp>\n\u003Cp>The plan is to start out simple and improve from there. Currently, due to some complexities with time conversions, this plugin requires your site-level timezone to be set to UTC+0, UTC or some other timezone with no UTC offset. You can find this setting in the admin section under Settings -> General.\u003C\u002Fp>\n\u003Cp>Also, please note that if you are changing your site-level timezone, this will not update any data in the database.  WordPress simply assumes all date and times entered, where entered in UTC.  This will unfortunately shifted all date and times by the number of hours your old timezone was offset from UTC.  But please keep in mind that storing date\u002Ftimes in UTC is a good habit and all new date and times entered correct with not shift.\u003C\u002Fp>\n","Allows the site-level timezone to be changed at the user profile level",1758,"2020-08-04T15:18:00.000Z","5.4.19","5.4.0",[21,72,23,73],"time-zones","user-timezone","http:\u002F\u002Fwww.wpcode.center\u002Fuser-timezone-plugin\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-utz.zip",{"slug":77,"name":78,"version":79,"author":80,"author_profile":81,"description":82,"short_description":83,"active_installs":84,"downloaded":85,"rating":86,"num_ratings":87,"last_updated":88,"tested_up_to":89,"requires_at_least":90,"requires_php":18,"tags":91,"homepage":95,"download_link":96,"security_score":97,"vuln_count":98,"unpatched_count":14,"last_vuln_date":99,"fetched_at":30},"mx-time-zone-clocks","MX Time Zone Clocks","5.1.1","Maksym Marko","https:\u002F\u002Fprofiles.wordpress.org\u002Fmarkomaksym\u002F","\u003Cp>\n    \u003Cstrong>MX Time Zone Clocks\u003C\u002Fstrong> – the ultimate solution for displaying multiple time zone clocks on your WordPress website effortlessly! With our plugin, you can now provide your users with the convenience of viewing time zone differences instantly, making scheduling and collaboration across different regions a breeze.\n\u003C\u002Fp>\n\u003Cp>\n    How does it work?\n\u003C\u002Fp>\n\u003Cspan class=\"embed-youtube\" style=\"text-align:center; display: block;\">\u003Ciframe loading=\"lazy\" class=\"youtube-player\" width=\"600\" height=\"320\" src=\"https:\u002F\u002Fwww.youtube.com\u002Fembed\u002FHoHkyK8kAdk?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent\" allowfullscreen=\"true\" style=\"border:0;\" sandbox=\"allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox\">\u003C\u002Fiframe>\u003C\u002Fspan>\n\u003Cp>        I want to thank Harish Premkumar for his jQuery plugin \u003Ca href=\"http:\u002F\u002Fwww.dhtmlgoodies.com\u002Ftutorials\u002Fcanvas-clock\u002F\" rel=\"nofollow ugc\">Canvas Clock\u003C\u002Fa> \u003C\u002Fp>\n","Add time zone clocks to your website.",1000,28779,94,15,"2024-04-17T08:11:00.000Z","6.5.8","4.9",[92,93,94,22],"clock","clock-on-the-website","%d0%b3%d0%be%d0%b4%d0%b8%d0%bd%d0%bd%d0%b8%d0%ba","https:\u002F\u002Fgithub.com\u002FMaksym-Marko\u002Fmx-time-zone-clock","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmx-time-zone-clocks.5.1.1.zip",46,3,"2025-12-31 00:00:00",{"slug":101,"name":102,"version":103,"author":104,"author_profile":105,"description":106,"short_description":107,"active_installs":108,"downloaded":109,"rating":110,"num_ratings":111,"last_updated":112,"tested_up_to":50,"requires_at_least":113,"requires_php":114,"tags":115,"homepage":121,"download_link":122,"security_score":58,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"simple-location","Simple Location","5.0.24","David Shanske","https:\u002F\u002Fprofiles.wordpress.org\u002Fdshanske\u002F","\u003Cp>Supports adding geo coordinates, a location taxonomy, and a textual location description to a post, comment, user, or attachment. Supports adding weather data to a post or to a widget based on location.\u003Cbr \u002F>\nOffers choice of map displays. It supports retrieving location using the HTML5 geolocation API by default. Clicking the location icon or ‘Lookup Location’ will retrieve the location.\u003C\u002Fp>\n\u003Cp>As it stores the GeoData in the classic WordPress format, Geodata can also be added from other plugins.\u003C\u002Fp>\n\u003Cp>Automatically saves location data from image metadata when uploaded as well.\u003C\u002Fp>\n\u003Cp>Offers the opportunity to change the displayed timezone on a per-post basis for those posts from far off locations and set this based on the coordinates of the location.\u003Cbr \u002F>\nWhile Gutenberg compatible, this is not built for Gutenberg.\u003C\u002Fp>\n\u003Ch3>Privacy and Data Notice\u003C\u002Fh3>\n\u003Cp>Simple Location stores location and weather data inside posts, attachments, comments, and term meta…optionally other post types. This data respects a public, private or\u003Cbr \u002F>\nprotected setting. Attachment data is automatically extracted from images if location is present, which could be extracted by any third-party downloading the picture\u003Cbr \u002F>\nunless removed. For all other data, it is provided by the user, who decides its ultimate use. Location data is made available through a geolocation provider…the default is currently\u003Cbr \u002F>\nHTML5 browser geolocation, for which the user must give consent to share). Other information is secured through use of third-party APIs to identify a\u003Cbr \u002F>\nlocation, calculate elevation, display maps, and weather conditions.\u003C\u002Fp>\n\u003Ch3>Locations and Venues\u003C\u002Fh3>\n\u003Cp>Locations uses WordPress taxonomies to allow you to generate an archive page of all posts from that location and giving it a permalink on your site. Locations are meant to reflect a more general\u003Cbr \u002F>\nlocation…for example, “Here are posts I made in California.”\u003C\u002Fp>\n\u003Cp>Locations are divided by administrative areas. The hierarchy for locations is:\u003Cbr \u002F>\n* Country\u003Cbr \u002F>\n* Region – state, county, or province level.\u003Cbr \u002F>\n* Locality – city, town, or village level\u003C\u002Fp>\n\u003Cp>You can choose to display the location over the textual address field. There is an option in settings to change this behavior.\u003C\u002Fp>\n\u003Cp>The reverse geocoding system attempts to consistently retrieve the country code, region code, and locality for the location and add them to the location taxonomy. This can be potentially problematic, as if the returns\u003Cbr \u002F>\nfrom the locations added aren’t consistent, it will duplicate and explode the list of terms. This is the same issue that has held back venues.\u003C\u002Fp>\n\u003Cp>Locations are matched using the country code, region code, and locality field, and therefore, you can edit the displayed name or the region code without issue. Due to matching issues, you may have to make some manual changes and there may be some occasional duplication.\u003C\u002Fp>\n\u003Cp>There is no top level Location page, \u002Flocation included in the plugin. You can create a page at this location and use a custom template to allow it to show a list of your locations.\u003C\u002Fp>\n\u003Cp>Venues are meant to reflect a specific location, such as a business or point of interest. Venues were originally set up as a taxonomy, and were in the plugin unimplemented for several versions. However,\u003Cbr \u002F>\ndue to various changes since that was set up, they were switched to a custom post type. Under this setup, each venue is represented by a URL on the site that posts can be linked to. The URL contains\u003Cbr \u002F>\ninformation about the venue.\u003C\u002Fp>\n\u003Ch3>Zones\u003C\u002Fh3>\n\u003Cp>Zones allow for geofencing. You can set coordinates and a radius around them. If you set location to a place within a zone, the default behavior is to replace the location\u003Cbr \u002F>\nwith a preset Name and hide the coordinates. This allows you to protect private locations such as your home, or your place of business. For Micropub, it will set the location\u003Cbr \u002F>\nas protected if the location is in the zone and the location-visibility property is not set. For the post editor in WordPress, looking up the location of an item inside the\u003Cbr \u002F>\nzone will result in the visibility being set to protected and the name being set to the zone name. This can be overridden.\u003C\u002Fp>\n\u003Cp>Zones are replaced as of 5.0.0 with Private Venues\u003C\u002Fp>\n\u003Ch3>Weather\u003C\u002Fh3>\n\u003Cp>Weather consists of at minimum the current conditions and temperature but includes future parameters for use such as pressure, wind speed, wind direction degree, etc. Weather widgets are available\u003Cbr \u002F>\nthat can be set to a specific location, a user, station ID, or airport code. Station ID is available from supported providers for weather stations, for example from a Personal Weather Station(PWS).\u003C\u002Fp>\n\u003Ch3>Stations\u003C\u002Fh3>\n\u003Cp>Stations allow for using a custom data source for weather data. This source should be a URL that returns a JSON object. When using the Custom Station provider for weather, it\u003Cbr \u002F>\nwill look for when one of the stations defined is within 10km of your current location. It will then use the return as the current weather conditions. Please note that the\u003Cbr \u002F>\nreturn must be in the format documented in the code.\u003C\u002Fp>\n\u003Ch3>WordPress GeoData\u003C\u002Fh3>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FGeodata\" rel=\"nofollow ugc\">WordPress Geodata\u003C\u002Fa> is an existing standardized way to store geodata about a post, user, comment, or term.\u003C\u002Fp>\n\u003Cp>It consists of four fields: latitude, longitude, public, and address. This matches up with the HTML5 Geolocation fields. The \u003Ca href=\"https:\u002F\u002Fdev.w3.org\u002Fgeo\u002Fapi\u002Fspec-source.html\" rel=\"nofollow ugc\">W3C Geolocation Specification\u003C\u002Fa>\u003Cbr \u002F>\nalso provides for properties of altitude, accuracy, altitudeAccuracy, speed, and heading, which may be stored. Map Zoom is also stored as a geodata property.\u003C\u002Fp>\n\u003Cp>Timezone is also stored as a property and is derived from the location by default or set manually.\u003C\u002Fp>\n\u003Cp>In order to access private location information, the following custom capabilities are added to WordPress:\u003Cbr \u002F>\n* ‘read_{$object_type}\u003Cem>location’ – Whether or not a user is allowed to read information locations for object types: posts, comments, terms, users. A user is always allowed to read the location from their objects.\u003Cbr \u002F>\n* ‘edit\u003C\u002Fem>{$object_type}_location’ – Whether or not a user is allowed to edit information locations for object types: posts, comments, terms, users. A user is always allowed to read the location from their objects.\u003C\u002Fp>\n\u003Ch3>Providers\u003C\u002Fh3>\n\u003Cp>The plugin is designed to be extensible and anyone could write a plugin that would add additional providers.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Map Providers are services that offer an API to retrieve maps, which are displayed on posts with a location. Providers include MapBox, Google, Mapquest, HERE, LocationIQ, Geoapify, TomTom, and Bing.\u003C\u002Fli>\n\u003Cli>Geocoding Providers take geo coordinates and look up the actual location\u002Faddress for textual display. Geocoding Providers include Nominatim, HERE, the Mapquest hosted version of Nominatim, Google, Bing, LocationIQ, OpenRoute and Geonames. They also support looking up coordinate for physical addresses\u003C\u002Fli>\n\u003Cli>Venue providers, similar to Geocoding providers, search for locations from coordinates, however, instead of returning street addresses, or municipality, it returns a list of places or venues.\u003C\u002Fli>\n\u003Cli>Elevation Providers optionally derive the elevation from an API when not available. Elevation is used to estimate altitude and adjust estimated sunrise\u002Fsunset levels accordingly.\u003C\u002Fli>\n\u003Cli>Location Providers attempt to determine your location to add it to a post. Providers include  HTML5 Browser Geolocation, a Provider that takes the location setting out of the author profile, a provider that returns the exact\u003Cbr \u002F>\nlocation of a three letter airport code, and \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Faaronpk\u002FCompass\" rel=\"nofollow ugc\">Compass\u003C\u002Fa>, a self-hosted option for storing your location.\u003C\u002Fli>\n\u003Cli>Weather Providers retrieve weather data about your location and include OpenWeatherMap, Pirate Weather, Dark Sky, Weatherstack, WeatherBit, HERE and the US National Weather Service. HERE, Pirate Weather, Dark Sky, WeatherBit, and Weatherstack do not support stations. There is also an option for custom station URLs that must return the properties as they are stored in WordPress.\u003Cbr \u002F>\n** The National Weather Service(US) uses their station lookup API to find the closest weather station, and uses weather from there. Therefore, if this returns no options, if you are outside the US, it will return no weather.\u003Cbr \u002F>\n** The Met Office(UK) uses the distance from your current location to the nearest UK weather station and finds the closest one. However, if the nearest station is more than 100km away, it will return nothing.\u003Cbr \u002F>\n** For Weather services like the NWS, Met Office, and the Custom Provider, where coverage is not worldwide, if nothing is found, a fallback provider can be set and used.\u003C\u002Fli>\n\u003C\u002Ful>\n","Adds geographic location and weather support to WordPress.",300,58726,92,8,"2026-02-25T21:08:00.000Z","6.2","7.4",[116,117,118,119,120],"geo","geolocation","location","maps","timezones","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fsimple-location\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsimple-location.5.0.24.zip",{"slug":124,"name":125,"version":126,"author":127,"author_profile":128,"description":129,"short_description":130,"active_installs":11,"downloaded":131,"rating":28,"num_ratings":28,"last_updated":132,"tested_up_to":133,"requires_at_least":134,"requires_php":18,"tags":135,"homepage":137,"download_link":138,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"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.",23173,"2008-07-02T02:25:00.000Z","2.5.1","2.3",[136,21,23],"date","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",{"attackSurface":140,"codeSignals":166,"taintFlows":173,"riskAssessment":174,"analyzedAt":177},{"hooks":141,"ajaxHandlers":162,"restRoutes":163,"shortcodes":164,"cronEvents":165,"entryPointCount":28,"unprotectedCount":28},[142,147,151,157],{"type":143,"name":144,"callback":144,"file":145,"line":146},"action","init","wp-timezone.php",41,{"type":143,"name":148,"callback":149,"file":145,"line":150},"plugins_loaded","plugin_translation",42,{"type":152,"name":153,"callback":154,"priority":155,"file":145,"line":156},"filter","gettext","replace_text",20,44,{"type":152,"name":158,"callback":159,"priority":160,"file":145,"line":161},"plugin_row_meta","filter_plugin_meta",10,45,[],[],[],[],{"dangerousFunctions":167,"sqlUsage":168,"outputEscaping":170,"fileOperations":28,"externalRequests":28,"nonceChecks":28,"capabilityChecks":28,"bundledLibraries":172},[],{"prepared":14,"raw":28,"locations":169},[],{"escaped":28,"rawEcho":28,"locations":171},[],[],[],{"summary":175,"deductions":176},"Based on the provided static analysis and vulnerability history, the wp-timezone v1.3 plugin exhibits a strong security posture. The static analysis reveals a completely clean attack surface, with no identified AJAX handlers, REST API routes, shortcodes, or cron events, and importantly, none of these entry points are unprotected. The code also demonstrates excellent security practices with no dangerous functions, all SQL queries utilizing prepared statements, and 100% of output being properly escaped. There are no file operations or external HTTP requests, further reducing potential attack vectors. The absence of any taint analysis findings, including unsanitized paths or critical\u002Fhigh severity flows, is a significant positive indicator. The plugin's vulnerability history is equally impressive, with zero recorded CVEs of any severity, suggesting a well-maintained and secure codebase over its development lifecycle. The lack of any common vulnerability types or recent issues reinforces this. The primary strength lies in the minimal attack surface and the robust coding practices observed.  While the absence of nonce and capability checks on entry points is technically noted, the complete lack of entry points renders this a non-issue in practice for this specific version. Overall, wp-timezone v1.3 appears to be a highly secure plugin.",[],"2026-03-16T20:27:55.587Z",{"wat":179,"direct":188},{"assetPaths":180,"generatorPatterns":182,"scriptPaths":183,"versionParams":185},[181],"\u002Fwp-content\u002Fplugins\u002Fwp-timezone\u002Fcss\u002Fwp-timezone.css",[],[184],"\u002Fwp-content\u002Fplugins\u002Fwp-timezone\u002Fjs\u002Fwp-timezone.js",[186,187],"wp-timezone\u002Fcss\u002Fwp-timezone.css?ver=","wp-timezone\u002Fjs\u002Fwp-timezone.js?ver=",{"cssClasses":189,"htmlComments":190,"htmlAttributes":191,"restEndpoints":192,"jsGlobals":193,"shortcodeOutput":194},[],[],[],[],[],[]]