[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fu9CSoLOXry0t1SNKFGSSgSLo8ishEJeT48UrLoC4X9c":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":18,"download_link":24,"security_score":25,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28,"vulnerabilities":29,"developer":30,"crawl_stats":27,"alternatives":37,"analysis":139,"fingerprints":172},"debugger","Debugger","1.4","Modern Tribe, Inc.","https:\u002F\u002Fprofiles.wordpress.org\u002Fmoderntribe\u002F","\u003Cp>You can use this plugin to manually log data or to capture logging on WordPress actions. You can capture load time, memory, backrace, data dumps, urls, and server IPs.\u003C\u002Fp>\n\u003Cp>This is designed to either be managed using wp-config.php and logging OR using the admin and debugbar plugin ( https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fdebug-bar\u002F ). Most of the following documentation applies equally to the settings panel or the wp-config.php vars.  Either one works fine. The only exception is the DEBUG_LOG configuration which is only supported as a wp-config var.\u003C\u002Fp>\n\u003Cp>Firstly, you can manually log things using the following function:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>do_action( 'log', $message, $group, $data );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The $group allows you to selectively output logging based on groups of log messages. The $message is the string you want to see in the log. $data is an optional parameter for the data that you want to display in the log (objects, arrays, or any other sort of data really).\u003C\u002Fp>\n\u003Cp>To render messages to the log, you must configure wp-config.php as follows:\u003C\u002Fp>\n\u003Cp>Run debug on only these groups. Use ‘ALL’ to debug everything. The group ‘ACTIONS’ is reserved for WordPress actions.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'DEBUG_GROUPS', 'ACTIONS,default,myspecialgroup' );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Display these outputs in the log for each log message.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'DEBUG_PARAMS', 'time,timedelta,memory,memorydelta,data,backtrace,url,server' );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>WordPress actions that you wish to log.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'DEBUG_ACTIONS', 'wp_head,switch_theme,wp_footer' );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Optional restriction by URL (useful on MU installs).\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'DEBUG_URLS', 'myurl.com' );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Minimum time in milliseconds required to register a log entry as being slow. Default 0 for no minumum.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'DEBUG_MIN_TIME', 500 );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Minimum memory in killobytes required to register a log entry as being heavy. Default 0 for no minumum.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'DEBUG_MIN_MEM', 1024 );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Path to log file or set to TRUE to use php error log. Default FALSE for no logging.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'DEBUG_LOG', '\u002Fpath\u002Fto\u002Fwritable\u002Flog\u002Ffile' );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>or\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'DEBUG_LOG', TRUE );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Todo\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Add variable for sample rate so that this could run randomly on production installs\u003C\u002Fli>\n\u003Cli>Admin panel per site\u003C\u002Fli>\n\u003Cli>Admin panel globally\u003C\u002Fli>\n\u003Cli>WordPress error logging\u003C\u002Fli>\n\u003Cli>Mysql query logging\u003C\u002Fli>\n\u003Cli>WP_Error integration\u003C\u002Fli>\n\u003Cli>Alerts ex: if this takes more than this much memory then log it…\u003C\u002Fli>\n\u003C\u002Ful>\n","You can use this plugin to manually log data or to capture logging on WordPress actions. You can capture load time, memory, backrace, data dumps, urls …",10,4278,90,2,"2013-05-05T23:08:00.000Z","3.6.1","3.0","",[20,4,21,22,23],"debug","modern-tribe","profiling","tribe","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebugger.1.4.zip",85,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":31,"display_name":7,"profile_url":8,"plugin_count":32,"total_installs":33,"avg_security_score":25,"avg_patch_time_days":34,"trust_score":35,"computed_at":36},"moderntribe",7,7830,30,84,"2026-04-04T17:22:14.819Z",[38,60,81,98,119],{"slug":39,"name":40,"version":41,"author":42,"author_profile":43,"description":44,"short_description":45,"active_installs":46,"downloaded":47,"rating":48,"num_ratings":49,"last_updated":50,"tested_up_to":51,"requires_at_least":52,"requires_php":53,"tags":54,"homepage":18,"download_link":58,"security_score":59,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"debug-this","Debug This","0.6.7","Razvan Aldea","https:\u002F\u002Fprofiles.wordpress.org\u002Fraldea89\u002F","\u003Cp>For admins, developers, and support staff, \u003Cstrong>Debug This\u003C\u002Fstrong> provides a ton of information about your WordPress installation, all from the front-end admin bar.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cem>The current WP_Query object\u003C\u002Fem>\u003C\u002Fli>\n\u003Cli>Blog info and options\u003C\u002Fli>\n\u003Cli>Embed providers\u003C\u002Fli>\n\u003Cli>Files in rendered HTML (CSS, images, JavaScript)\u003C\u002Fli>\n\u003Cli>Filters and actions\u003C\u002Fli>\n\u003Cli>Images sizes\u003C\u002Fli>\n\u003Cli>Globals and constants\u003C\u002Fli>\n\u003Cli>Menus\u003C\u002Fli>\n\u003Cli>Object cache stats\u003C\u002Fli>\n\u003Cli>Plugins, must-use plugins, and dropins\u003C\u002Fli>\n\u003Cli>Rewrite rules\u003C\u002Fli>\n\u003Cli>Queries\u003C\u002Fli>\n\u003Cli>PHP and server information\u003C\u002Fli>\n\u003Cli>Post attachments\u003C\u002Fli>\n\u003Cli>Post types\u003C\u002Fli>\n\u003Cli>Scripts and styles enqueued\u003C\u002Fli>\n\u003Cli>Shortcodes\u003C\u002Fli>\n\u003Cli>Sidebars and widgets\u003C\u002Fli>\n\u003Cli>Taxonomies and terms\u003C\u002Fli>\n\u003Cli>Themes\u003C\u002Fli>\n\u003Cli>Users\u003C\u002Fli>\n\u003Cli>WP cron schedules and jobs\u003C\u002Fli>\n\u003Cli>WP debug log\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Debug This\u003C\u002Fstrong> helps you save time and effort when trying to figure out what’s going on. Instead of hardcoding debug snippets or writing complex unit\u003Cbr \u002F>\ntests for small functionality, you can simply bring to the surface what you need right from the admin bar.\u003C\u002Fp>\n\u003Cp>For example, when viewing a single post, you can see:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>a list of post attachments,\u003C\u002Fli>\n\u003Cli>which menus and sidebars are being displayed,\u003C\u002Fli>\n\u003Cli>the post type, post fields, and meta data,\u003C\u002Fli>\n\u003Cli>the current query variables and query string,\u003C\u002Fli>\n\u003Cli>the rewrite rules applied,\u003C\u002Fli>\n\u003Cli>the author,\u003C\u002Fli>\n\u003Cli>the terms,\u003C\u002Fli>\n\u003Cli>and much more.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Extend\u003C\u002Fh3>\n\u003Ch4>Debug This Functions\u003C\u002Fh4>\n\u003Cp>New debug modes can be created easily:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_debug_extension(\n    $mode,\n    $menu_label,\n    $description,\n    $callback,\n    $group = 'General'\n);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Example\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_debug_extension(\n    'actions',\n    __('Actions', 'debug-this'),\n    __('$wp_actions contains all active registered actions', 'debug-this'),\n    'foo_callback',\n    'Filters And Actions'\n);\nfunction foo_callback($buffer, $template){\n    global $wp_actions;\n    $debug = print_r($wp_actions, true);\n    return $debug;\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>You can add links to the header of a debug mode page. Place this code within your debug callback function.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_debug_header_link('http:\u002F\u002Furltolink', 'Link Label');\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Extensions can be removed as well using \u003Ccode>remove_debug_extension($mode);\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>No PRE Tags\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>If you don’t want your debug output to be enclosed in PRE tags, simply set the following in your extension:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Debug_This::$no_pre = true;\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Saved Queries and Execution Time\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Retrieve saved queries and execution time by using the following static properties:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>Debug_This::$execution_time\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>Debug_This::$queries\u003C\u002Fcode> – SAVEQUERIES must defined as true\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>URL Helpers\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>Debug_This::get_current_debug_url()\u003C\u002Fcode> – current URL with the debug query\u003C\u002Fli>\n\u003Cli>\u003Ccode>Debug_This::get_escape_url()\u003C\u002Fcode> – used for the debug escape link that links to original page URL\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>WP Actions\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ccode>debug_this\u003C\u002Fcode> – receives the $mode arg – outputs the debug code sent from the extension modes. The default action is set to priority 5. This allows you to prepend or append any output without conflict using less or greater priorities.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>WP Filters\u003C\u002Fh4>\n\u003Cp>There are a few filters you can use to customize Debug This to your needs:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>debug_this_template\u003C\u002Fcode> – receives $template arg – Use your own template\u003C\u002Fli>\n\u003Cli>\u003Ccode>debug_this_default_mode\u003C\u002Fcode>  – receives $mode arg – Alters the mode for the parent DT admin bar button link.\u003C\u002Fli>\n\u003Cli>\u003Ccode>debug_this_output\u003C\u002Fcode> – receives $output, $mode args – Filter debug content before it’s rendered\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>JavaScript\u003C\u002Fh4>\n\u003Cp>To access the built-in Debug This JS functionality, enqueue your custom script with the dependency set to \u003Ccode>debug-this\u003C\u002Fcode>. Your script will inherit a jQuery dependency.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Object: debugThis\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>debugThis.mode\u003C\u002Fcode> – current mode\u003C\u002Fli>\n\u003Cli>\u003Ccode>debugThis.defaultMode\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>debugThis.template\u003C\u002Fcode> – current included template\u003C\u002Fli>\n\u003Cli>\u003Ccode>debugThis.queryVar\u003C\u002Fcode> – the defined query string variable\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Functions:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>isDebug()\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>getDebugMode()\u003C\u002Fcode> – uses \u003Ccode>isDebug()\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Events:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>A jQuery \u003Ccode>debug-this\u003C\u002Fcode> event is fired from the footer. You can hook into this event with the following;\u003C\u002Fp>\n\u003Cpre>\u003Ccode>jQuery(document).bind('debug-this', function(event, debugThis){\n    console.log(debugThis);\n});\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Helper Functions\u003C\u002Fh4>\n\u003Cp>There are three included functions to help you work with files.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>debug_this_get_file_ownership($file)\u003C\u002Fcode> – returns \u003Ccode>array('name' => $name, 'group' => $group)\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>debug_this_get_file_perms($file)\u003C\u002Fcode> – returns string – Example: 0775\u003C\u002Fli>\n\u003Cli>\u003Ccode>debug_this_convert_perms_to_rwx($perms)\u003C\u002Fcode> – returns string – converts permission number to RWX format – Example: 0755 folder becomes drwxr-xr-x\u003C\u002Fli>\n\u003C\u002Ful>\n","Peek under the hood with sixty debugging reports just one click away.",2000,158436,96,17,"2025-06-04T08:56:00.000Z","6.8.5","5.2","5.6",[20,4,55,56,57],"developer","hooks","query","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-this.0.6.7.zip",100,{"slug":61,"name":62,"version":63,"author":64,"author_profile":65,"description":66,"short_description":67,"active_installs":68,"downloaded":69,"rating":35,"num_ratings":70,"last_updated":71,"tested_up_to":72,"requires_at_least":73,"requires_php":18,"tags":74,"homepage":79,"download_link":80,"security_score":25,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"duplicate-tec-event","Duplicate TEC Event","1.5.2","Ben Lobaugh (blobaugh)","https:\u002F\u002Fprofiles.wordpress.org\u002Fblobaugh\u002F","\u003Cp>Adds the ability to duplicate an event created by Modern Tribe’s The Event Calendar plugin. This plugin utilizes the TEC functions to ensure that the new event gets passed through all proper filters\u003C\u002Fp>\n\u003Cp>Want to get involved? For this project on Github https:\u002F\u002Fgithub.com\u002FFreshMuseDesign\u002Fduplicate-tec-event\u003C\u002Fp>\n\u003Ch3>1.5.2\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Updated compatibility with WordPress 4.8\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>1.5.1\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Verified working with WP 4.4.1\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>1.5\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Updated to ensure functionality with 3.7\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>1.4\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Fixed bug causing duplicated recurring events to also alter the original recurring events on edit ( thanks Steve! )\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>1.3\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Added a nonce for security\u003C\u002Fli>\n\u003Cli>Performed updated requested by Modern Tribe\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>1.0\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>First release\u003C\u002Fli>\n\u003C\u002Ful>\n","Adds the ability to duplicate an event created by Modern Tribe's The Event Calendar plugin.",1000,16154,13,"2017-06-05T15:39:00.000Z","4.8.28","3.1",[75,76,77,21,78],"clone","duplicate","events","the-events-calendar","https:\u002F\u002Fgithub.com\u002FFreshMuseDesign\u002Fduplicate-tec-event","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fduplicate-tec-event.zip",{"slug":82,"name":83,"version":84,"author":85,"author_profile":86,"description":87,"short_description":88,"active_installs":89,"downloaded":90,"rating":48,"num_ratings":91,"last_updated":92,"tested_up_to":93,"requires_at_least":94,"requires_php":18,"tags":95,"homepage":18,"download_link":97,"security_score":25,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"debug-bar-slow-actions","Debug Bar Slow Actions","0.8.4","Konstantin Kovshenin","https:\u002F\u002Fprofiles.wordpress.org\u002Fkovshenin\u002F","\u003Cp>This plugin lists the top 100 slowest actions and filters during a page request in WordPress. It helps you figure out performance bottlenecks in themes and plugins.\u003C\u002Fp>\n\u003Cp>Requires \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdebug-bar\u002F\" title=\"Debug Bar\" rel=\"ugc\">Debug Bar\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Current limitations:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Does not time nested actions and filters due to a core bug\u003C\u002Fli>\n\u003Cli>Does not time actions and filters before plugins_loaded or muplugins_loaded if placed in mu-plugins\u003C\u002Fli>\n\u003Cli>Does not time actions and callbacks after wp_footer at priority 1000\u003C\u002Fli>\n\u003C\u002Ful>\n","Easily find out which actions and filters are the slowest during a page load.",200,127493,15,"2018-01-18T07:52:00.000Z","4.9.29","3.8",[96,20,22],"actions","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-bar-slow-actions.0.8.4.zip",{"slug":99,"name":100,"version":101,"author":102,"author_profile":103,"description":104,"short_description":105,"active_installs":89,"downloaded":106,"rating":107,"num_ratings":108,"last_updated":109,"tested_up_to":110,"requires_at_least":111,"requires_php":112,"tags":113,"homepage":117,"download_link":118,"security_score":25,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"the-events-calendar-outlook-import-fix","The Events Calendar Outlook Import Fix","1.1.0","Andy Fragen","https:\u002F\u002Fprofiles.wordpress.org\u002Fafragen\u002F","\u003Cp>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fthe-events-calendar\" rel=\"ugc\">The Events Calendar\u003C\u002Fa> allows for the import of calendar events via download of a generated iCalendar file. This generated file contains the \u003Ccode>X-WR-CALNAME\u003C\u002Fcode> header, which is a valid header.\u003C\u002Fp>\n\u003Cp>Unfortunately Outlook chokes and will create a new calendar when it sees this header instead of adding the event(s) to the default Outlook calendar. This plugin removes that header from the generated iCalendar file.\u003C\u002Fp>\n","Fix import of calendar events from The Events Calendar to Outlook.",13214,86,4,"2022-05-14T17:06:00.000Z","6.0.11","3.7","5.3",[77,114,115,21,116],"ical-feed","icalendar","outlook","https:\u002F\u002Fgithub.com\u002Fafragen\u002Fthe-events-calendar-outlook-import-fix","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fthe-events-calendar-outlook-import-fix.1.1.0.zip",{"slug":120,"name":121,"version":122,"author":123,"author_profile":124,"description":125,"short_description":126,"active_installs":59,"downloaded":127,"rating":59,"num_ratings":128,"last_updated":129,"tested_up_to":130,"requires_at_least":131,"requires_php":132,"tags":133,"homepage":137,"download_link":138,"security_score":59,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"display-event-locations-tec","Display Event Location for The Events Calendar","4.6.0","Michael Weiner","https:\u002F\u002Fprofiles.wordpress.org\u002Fvikings412\u002F","\u003Cp>This plugin overrides the template for the tooltip that is displayed when a user hovers over an event on the full month calendar view created by The Events Calendar or The Events Calendar Pro plugin. The name of the event’s venue\u002Flocation that is entered with the event will be displayed under the date and time that the event occurs. The full street address for the location can also be displayed. All of the other elements of the tooltip remain unchanged.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Ftheeventscalendar.com\u002Fproduct\u002Fwordpress-events-calendar\u002F\" rel=\"nofollow ugc\">The Events Calendar\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Ftheeventscalendar.com\u002Fproduct\u002Fwordpress-events-calendar-pro\u002F\" rel=\"nofollow ugc\">The Events Calendar Pro\u003C\u002Fa> are WordPress plugins developed by \u003Ca href=\"https:\u002F\u002Ftri.be\" rel=\"nofollow ugc\">Modern Tribe\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cspan class=\"embed-youtube\" style=\"text-align:center; display: block;\">\u003Ciframe loading=\"lazy\" class=\"youtube-player\" width=\"750\" height=\"422\" src=\"https:\u002F\u002Fwww.youtube.com\u002Fembed\u002FKv3kx8YvzA4?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\u003Ch3>Arbitrary section\u003C\u002Fh3>\n\u003Ch3>CSS Classes:\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ccode>.deltec-tooltip-message\u003C\u002Fcode> – A \u003Ccode>paragraph\u003C\u002Fcode> element that surrounds all of the information that is added to the tooltip by this plugin.\u003C\u002Fli>\n\u003Cli>\u003Ccode>.deltec-location-name-prefix\u003C\u002Fcode> – A \u003Ccode>span\u003C\u002Fcode> element that surrounds the prefix message that you can set in the Display Event Location for The Events Calendar settings area in the textfield labeled \u003Cstrong>\u003Cem>Tooltip Message Before Venue\u002FLocation Name\u003C\u002Fem>\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Ccode>.deltec-location-name\u003C\u002Fcode> – A \u003Ccode>span\u003C\u002Fcode> element that surrounds the name of the event’s venue\u002Flocation name.\u003C\u002Fli>\n\u003Cli>\u003Ccode>.deltec-street-address\u003C\u002Fcode> – A \u003Ccode>span\u003C\u002Fcode> element that surrounds the all elements of the street address for the event’s venue\u002Flocation (if enabled in Display Event Location for The Events Calendar settings area)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Github Repository\u003C\u002Fh3>\n\u003Cp>The Github Repository for this plugin can be found here: https:\u002F\u002Fgithub.com\u002Fmike-weiner\u002Fdisplay-event-locations-tec.\u003C\u002Fp>\n\u003Ch3>References:\u003C\u002Fh3>\n\u003Cp>Below are resources and references that were used to help develop parts of this plugin.\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fsupport.theeventscalendar.com\u002F153124-Themers-Guide\" rel=\"nofollow ugc\">https:\u002F\u002Fsupport.theeventscalendar.com\u002F153124-Themers-Guide\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fdocs.theeventscalendar.com\u002Freference\u002Fhooks\u002Ftribe_events_template_data_array\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Fdocs.theeventscalendar.com\u002Freference\u002Fhooks\u002Ftribe_events_template_data_array\u002F\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fdocs.theeventscalendar.com\u002Freference\u002Fhooks\u002Ftribe_template_theme_path_list\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Fdocs.theeventscalendar.com\u002Freference\u002Fhooks\u002Ftribe_template_theme_path_list\u002F\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fdocs.theeventscalendar.com\u002Freference\u002Ffunctions\u002Ftribe_address_exists\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Fdocs.theeventscalendar.com\u002Freference\u002Ffunctions\u002Ftribe_address_exists\u002F\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fdocs.theeventscalendar.com\u002Freference\u002Ffunctions\u002Ftribe_get_full_address\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Fdocs.theeventscalendar.com\u002Freference\u002Ffunctions\u002Ftribe_get_full_address\u002F\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Ftheeventscalendar.com\u002Fknowledgebase\u002Fk\u002Fcustom-additional-template-locations\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Ftheeventscalendar.com\u002Fknowledgebase\u002Fk\u002Fcustom-additional-template-locations\u002F\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgist.github.com\u002Fcliffordp\u002Fb76421f2490a8b8995493f203e11b331\" rel=\"nofollow ugc\">https:\u002F\u002Fgist.github.com\u002Fcliffordp\u002Fb76421f2490a8b8995493f203e11b331\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>Special Thanks:\u003C\u002Fh3>\n\u003Cp>A special thank you to user \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fcliffordp\" rel=\"nofollow ugc\">@cliffordp\u003C\u002Fa> on Github for several helpful gists that were used as boilerplates to achieve certain functionality within this plugin.\u003C\u002Fp>\n\u003Cp>Thank you to \u003Ca href=\"https:\u002F\u002Fella-ella.studio\" rel=\"nofollow ugc\">Danielle Attinella\u003C\u002Fa> for her amazing work on designing a new icon and banner image for the plugin.\u003C\u002Fp>\n","This plugin works with The Events Calendar by Modern Tribe. It adds an event's location information to the tooltip on the monthly calendar view.",6682,1,"2025-11-24T01:37:00.000Z","6.9.4","5.0.0","7.0.0",[134,77,21,135,136],"customization","override","template","https:\u002F\u002Fmichaelweiner.org\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdisplay-event-locations-tec.4.6.0.zip",{"attackSurface":140,"codeSignals":155,"taintFlows":162,"riskAssessment":163,"analyzedAt":171},{"hooks":141,"ajaxHandlers":151,"restRoutes":152,"shortcodes":153,"cronEvents":154,"entryPointCount":26,"unprotectedCount":26},[142,148],{"type":143,"name":144,"callback":145,"priority":11,"file":146,"line":147},"action","debugger_render_log_entry","render_log","debugger.php",169,{"type":143,"name":149,"callback":149,"priority":128,"file":146,"line":150},"log",180,[],[],[],[],{"dangerousFunctions":156,"sqlUsage":157,"outputEscaping":159,"fileOperations":26,"externalRequests":26,"nonceChecks":26,"capabilityChecks":26,"bundledLibraries":161},[],{"prepared":26,"raw":26,"locations":158},[],{"escaped":14,"rawEcho":26,"locations":160},[],[],[],{"summary":164,"deductions":165},"The \"debugger\" plugin v1.4 exhibits a strong security posture based on the provided static analysis. There are no identified dangerous functions, SQL queries are exclusively prepared, and all outputs are properly escaped. The absence of file operations and external HTTP requests further mitigates common attack vectors. Critically, the plugin appears to have a very limited attack surface, with zero identified entry points like AJAX handlers, REST API routes, or shortcodes, and no cron events. This lack of exposure significantly reduces the potential for malicious interaction.",[166,169],{"reason":167,"points":168},"No capability checks detected",5,{"reason":170,"points":168},"No nonce checks detected","2026-03-17T00:11:07.205Z",{"wat":173,"direct":182},{"assetPaths":174,"generatorPatterns":177,"scriptPaths":178,"versionParams":179},[175,176],"\u002Fwp-content\u002Fplugins\u002Fdebugger\u002Fassets\u002Fcss\u002Fdebugger.css","\u002Fwp-content\u002Fplugins\u002Fdebugger\u002Fassets\u002Fjs\u002Fdebugger.js",[],[176],[180,181],"debugger\u002Fassets\u002Fcss\u002Fdebugger.css?ver=","debugger\u002Fassets\u002Fjs\u002Fdebugger.js?ver=",{"cssClasses":183,"htmlComments":189,"htmlAttributes":190,"restEndpoints":195,"jsGlobals":196,"shortcodeOutput":199},[184,185,186,187,188],"debugger-log-entry","debugger-log-entry-group","debugger-log-entry-message","debugger-log-entry-data","debugger-log-entry-backtrace",[],[191,192,193,194],"data-debugger-log-group","data-debugger-log-message","data-debugger-log-time","data-debugger-log-memory",[],[197,198],"debugger_log","debugger_init",[]]