[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fpX92GAUwOMW7gyQa3c8UnojBLQ78xNDi_AKUnIW23Lo":3,"$fcGLGVuQO5YZcFEU2W2Xgb9Sy0VIOtSQBVDWN3-UXzAQ":365,"$fcRGoBE90O83JNtYGFJ0RWkCFnD1XC5jAbO1eSR6OOXs":369},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":11,"num_ratings":11,"last_updated":13,"tested_up_to":14,"requires_at_least":15,"requires_php":16,"tags":17,"homepage":23,"download_link":24,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27,"discovery_status":28,"vulnerabilities":29,"developer":30,"crawl_stats":26,"alternatives":37,"analysis":136,"fingerprints":323},"globus-debug-control","GLOBUS Debug Control","2.2.5","Yevhen Leonidov","https:\u002F\u002Fprofiles.wordpress.org\u002Fglobusstudio\u002F","\u003Cp>Working with \u003Ccode>WP_DEBUG\u003C\u002Fcode> enabled often floods the screen with notices and deprecation warnings from third-party plugins and themes – things you neither wrote nor can fix. GLOBUS Debug Control lets you filter out the noise and focus on what actually matters.\u003C\u002Fp>\n\u003Cp>All settings are available in \u003Cstrong>Settings – GLOBUS Debug Control\u003C\u002Fstrong>. The plugin provides eight tabs: Settings, WP_DEBUG, Error Log, Cron Tasks, Transients, Autoloaded, HTTP Log, and Constants. No code editing needed.\u003C\u002Fp>\n\u003Ch4>Settings tab\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>Choose which errors to see\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Turn off specific PHP error types independently:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Notices – informational messages that rarely indicate a real problem\u003C\u002Fli>\n\u003Cli>Deprecated – warnings about outdated functions, usually from third-party code\u003C\u002Fli>\n\u003Cli>Warnings – optional, keep them on if you are actively debugging\u003C\u002Fli>\n\u003Cli>Strict – PHP 7 strict standards messages (not applicable in PHP 8+)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Control error display\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Three modes for showing errors on screen:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Inherit\u003C\u002Fstrong> – follows your \u003Ccode>wp-config.php\u003C\u002Fcode> settings (default, non-intrusive)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>On\u003C\u002Fstrong> – always show errors, useful during active development\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Off\u003C\u002Fstrong> – hide all errors from screen even if \u003Ccode>WP_DEBUG_DISPLAY\u003C\u002Fcode> is on\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Errors are always hidden automatically during AJAX requests, REST API calls, WP-Cron, and WP-CLI, so your API responses stay clean regardless of the display setting.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Error logging\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Enable logging to capture errors in a file instead of (or in addition to) showing them on screen:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Set a custom log file path (absolute or relative to \u003Ccode>wp-content\u002F\u003C\u002Fcode>)\u003C\u002Fli>\n\u003Cli>Set a maximum log file size (1-100 MB); the file rotates automatically when the limit is reached\u003C\u002Fli>\n\u003Cli>Defaults to \u003Ccode>wp-content\u002Fdebug.log\u003C\u002Fcode> if no path is specified\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Remove the php-error CSS class\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>When WordPress encounters a PHP error, it adds a \u003Ccode>php-error\u003C\u002Fcode> class to the \u003Ccode>\u003Cbody>\u003C\u002Fcode> tag, which can break your page layout. This option removes it via both CSS and JavaScript so your front-end and admin look normal even in debug mode.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Early error interception (optional)\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>WordPress loads plugins in alphabetical order. If another plugin throws an error before GLOBUS Debug Control initialises, those errors will not be filtered. Enabling the \u003Cstrong>MU-plugin dropin\u003C\u002Fstrong> installs a small helper file into \u003Ccode>wp-content\u002Fmu-plugins\u002F\u003C\u002Fcode> that runs before any regular plugin, ensuring your filter settings apply from the very start of the request. The dropin is removed automatically when the plugin is deactivated or uninstalled.\u003C\u002Fp>\n\u003Ch4>WP_DEBUG tab\u003C\u002Fh4>\n\u003Cp>Toggle the five most important debug constants directly from the admin panel without editing \u003Ccode>wp-config.php\u003C\u002Fcode>:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>WP_DEBUG\u003C\u002Fcode> – master debug switch\u003C\u002Fli>\n\u003Cli>\u003Ccode>WP_DEBUG_LOG\u003C\u002Fcode> – write errors to a log file\u003C\u002Fli>\n\u003Cli>\u003Ccode>WP_DEBUG_DISPLAY\u003C\u002Fcode> – show errors on screen\u003C\u002Fli>\n\u003Cli>\u003Ccode>SCRIPT_DEBUG\u003C\u002Fcode> – use unminified core JS\u002FCSS\u003C\u002Fli>\n\u003Cli>\u003Ccode>SAVEQUERIES\u003C\u002Fcode> – log all database queries\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The plugin locates your \u003Ccode>wp-config.php\u003C\u002Fcode> automatically and patches it in place, adding the constant if it is missing or updating the existing value. Commented-out defines and block-comment sections are never touched. The current status of \u003Ccode>WP_DEBUG\u003C\u002Fcode> is always visible as a badge in the plugin header.\u003C\u002Fp>\n\u003Ch4>Error Log tab\u003C\u002Fh4>\n\u003Cp>Displays the contents of your \u003Ccode>debug.log\u003C\u002Fcode> file directly in the admin panel using a CodeMirror editor with line numbers. Lines are color-coded by severity: fatal\u002Fparse errors, warnings, notices\u002Fdeprecations, and cron-related messages. The log is paginated (200 lines per page), supports live polling for new entries, and can be downloaded or cleared with one click. Large log files (over 2 MB) are read from the tail to keep memory usage low.\u003C\u002Fp>\n\u003Ch4>Cron Tasks tab\u003C\u002Fh4>\n\u003Cp>Lists all scheduled WordPress cron events with hook name, next run time, recurrence interval, and arguments. Summary cards show total events, overdue count, orphaned hooks, and duplicates. Overdue events are highlighted. You can run any event immediately or delete orphaned hooks directly from the table.\u003C\u002Fp>\n\u003Ch4>Transients tab\u003C\u002Fh4>\n\u003Cp>Displays database-stored WordPress transients from the options table with key name, data size, and expiration time. Transients stored in an external object cache (Redis, Memcached) are not shown. Expired transients are highlighted. You can delete individual transients or purge all expired ones in one click. Summary cards show total count, expired count, and total data size.\u003C\u002Fp>\n\u003Ch4>Autoloaded tab\u003C\u002Fh4>\n\u003Cp>Lists autoloaded options from \u003Ccode>wp_options\u003C\u002Fcode> sorted by data size (top 200). Shows the option name and value size. Summary cards display total autoloaded row count and total payload size with warnings when thresholds are exceeded (over 800 KB or over 100 rows). This is a read-only diagnostic view to help identify options that inflate every WordPress request.\u003C\u002Fp>\n\u003Ch4>HTTP Log tab\u003C\u002Fh4>\n\u003Cp>Captures outgoing WordPress HTTP API requests (\u003Ccode>wp_remote_get\u003C\u002Fcode>, \u003Ccode>wp_remote_post\u003C\u002Fcode>, etc.) via the \u003Ccode>http_api_debug\u003C\u002Fcode> hook. Capturing must be explicitly enabled and stores up to 100 entries (6-hour TTL). Each entry shows the request URL, HTTP method, status code, response time, and transport class. Useful for spotting slow or failing external API calls.\u003C\u002Fp>\n\u003Ch4>Constants tab\u003C\u002Fh4>\n\u003Cp>Displays all WordPress-related PHP constants defined at runtime, grouped by category: Debug, Performance, Security, Database, Auth and Salts, Paths, and Other WP_* constants. Sensitive values (database password, auth keys, salts) are automatically masked. This is a read-only reference view.\u003C\u002Fp>\n","WordPress debug toolkit: filter errors, toggle WP_DEBUG, view error logs, monitor cron, transients, HTTP requests, and more.",0,84,"2026-04-13T19:27:00.000Z","6.9.4","5.2","7.4",[18,19,20,21,22],"cron","debug","error-log","transients","wp-config","https:\u002F\u002Fglobus.studio","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fglobus-debug-control.2.2.5.zip",100,null,"2026-04-16T10:56:18.058Z","no_bundle",[],{"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},"globusstudio",2,2000,30,94,"2026-05-19T20:14:31.497Z",[38,57,76,93,116],{"slug":39,"name":40,"version":41,"author":42,"author_profile":43,"description":44,"short_description":45,"active_installs":46,"downloaded":47,"rating":25,"num_ratings":32,"last_updated":48,"tested_up_to":14,"requires_at_least":49,"requires_php":16,"tags":50,"homepage":52,"download_link":53,"security_score":54,"vuln_count":55,"unpatched_count":11,"last_vuln_date":56,"fetched_at":27},"0-day-analytics","0 Day Analytics","5.0.0","Golemiq","https:\u002F\u002Fprofiles.wordpress.org\u002Fawesomefootnotes\u002F","\u003Cp>\u003Cstrong>0 Day Analytics\u003C\u002Fstrong> is a comprehensive WordPress debugging and operational\u003Cbr \u002F>\nintelligence plugin. It is purpose-built for developers and site administrators\u003Cbr \u002F>\nwho need real-time visibility into their PHP errors, scheduled tasks, database\u003Cbr \u002F>\nstate, outgoing emails, HTTP requests, hook behaviour, and overall site health —\u003Cbr \u002F>\nall from a single admin interface.\u003C\u002Fp>\n\u003Cp>Unlike general monitoring services, 0 Day Analytics runs entirely inside your\u003Cbr \u002F>\nWordPress installation with no third-party data collection. Every module is\u003Cbr \u002F>\nopt-in and designed with performance in mind.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Plugin Website:\u003C\u002Fstrong> \u003Ca href=\"https:\u002F\u002F0-day-analytics.com\u002F0-day-analytics-wordpress-debugging-monitoring-toolkit\u002F?src=readme\" rel=\"nofollow ugc\">0-day-analytics.com\u003C\u002Fa>\u003Cbr \u002F>\n\u003Cstrong>User Documentation:\u003C\u002Fstrong> \u003Ca href=\"https:\u002F\u002F0-day-analytics.com\u002Fcategory\u002F0-day-plugin\u002Fuser-guide\u002F?src=readme\" rel=\"nofollow ugc\">User Guide\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch4>Error Log Manager\u003C\u002Fh4>\n\u003Cp>Read, search, filter, and manage your PHP\u002FWordPress error log without leaving\u003Cbr \u002F>\nthe admin. Engineered for very large (GB-sized) logs using a reverse-line reader\u003Cbr \u002F>\nthat never performs a full-file read. Supports code-context viewing (click any\u003Cbr \u002F>\nerror to see the surrounding source), per-severity filtering, log truncation,\u003Cbr \u002F>\nand download. Optionally randomise the log filename to reduce exposure.\u003C\u002Fp>\n\u003Ch4>PHP Fatal Error Tracker\u003C\u002Fh4>\n\u003Cp>Captures and stores PHP fatal errors in a dedicated database table, it records PHP errors even if the WP_DEBUG is turned off so they persist even after the log is rotated or overwritten. Each record includes\u003Cbr \u002F>\nerror type, file, line, stack trace, and timestamp — searchable and filterable\u003Cbr \u002F>\ndirectly in the admin.\u003C\u002Fp>\n\u003Ch4>Site Performance & Security Scanner\u003C\u002Fh4>\n\u003Cp>Runs 32+ automated checks across three categories — Security, Speed, and\u003Cbr \u002F>\nResources used — and presents a scored dashboard with actionable\u003Cbr \u002F>\nrecommendations. Checks include: PHP version, WordPress version, SSL\u003Cbr \u002F>\ncertificate, debug mode exposure, file permissions, database prefix, XML-RPC,\u003Cbr \u002F>\nlogin URL, active plugin count, autoloaded options, cron health, page caching,\u003Cbr \u002F>\nobject caching, gzip compression, lazy loading, image optimisation, and more.\u003C\u002Fp>\n\u003Ch4>Google PageSpeed & Core Web Vitals\u003C\u002Fh4>\n\u003Cp>Analyse any URL directly from the WordPress admin using the Google PageSpeed\u003Cbr \u002F>\nInsights API. Displays Performance, Accessibility, Best Practices, and SEO\u003Cbr \u002F>\nscores with Lighthouse category breakdowns for both desktop and mobile. For that you need to provide your own PageSpeed Google API key.\u003C\u002Fp>\n\u003Ch4>URL Tracker & Asset Analyser\u003C\u002Fh4>\n\u003Cp>Automatically tracks visited page URLs on your site. For each recorded URL,\u003Cbr \u002F>\nyou can collect all associated JS, CSS, and media assets (with file sizes), run\u003Cbr \u002F>\na Google PageSpeed analysis, and review visit counts — making it easy to audit\u003Cbr \u002F>\npage weight and performance regressions over time.\u003C\u002Fp>\n\u003Ch4>Cron Manager\u003C\u002Fh4>\n\u003Cp>View, search, edit, manually run, and delete WordPress scheduled tasks. Shows\u003Cbr \u002F>\nnext run time (UTC), recurrence interval, arguments, and last execution status.\u003Cbr \u002F>\nSupports bulk actions and advanced filtering.\u003C\u002Fp>\n\u003Ch4>Transients Manager\u003C\u002Fh4>\n\u003Cp>Browse, search, edit, and safely delete database transients. Displays expiry\u003Cbr \u002F>\ntime, serialised value (pretty-printed), and size. Bulk delete supports\u003Cbr \u002F>\nfiltered selections.\u003C\u002Fp>\n\u003Ch4>Outgoing HTTP Requests Viewer\u003C\u002Fh4>\n\u003Cp>Logs all outgoing \u003Ccode>wp_remote_*\u003C\u002Fcode> calls made by WordPress core, themes, and\u003Cbr \u002F>\nplugins. Records URL, method, status code, response time, triggering plugin,\u003Cbr \u002F>\nuser, and full request\u002Fresponse detail. Export to CSV for external analysis.\u003Cbr \u002F>\nAdvanced filtering by domain, plugin, status, and date range.\u003C\u002Fp>\n\u003Ch4>Mail Logger & Composer\u003C\u002Fh4>\n\u003Cp>Records every email sent through \u003Ccode>wp_mail()\u003C\u002Fcode> — including headers, body,\u003Cbr \u002F>\nattachments, CC, and BCC — and stores it in a searchable log. View the\u003Cbr \u002F>\nrendered email body, resend any logged email, or compose and send new emails\u003Cbr \u002F>\ndirectly from the admin. Supports HTML and plain-text previews.\u003C\u002Fp>\n\u003Ch4>SMTP Configuration\u003C\u002Fh4>\n\u003Cp>Configure custom SMTP settings (host, port, encryption, username, password)\u003Cbr \u002F>\nwith a built-in test email tool. Optionally log SMTP debug output to the\u003Cbr \u002F>\nWordPress debug log.\u003C\u002Fp>\n\u003Ch4>WP Hooks Monitor\u003C\u002Fh4>\n\u003Cp>Define which WordPress actions and filters (core or custom) you want to\u003Cbr \u002F>\nobserve. The Hooks Capture module records each invocation with its parameters,\u003Cbr \u002F>\nreturn value (for filters), and a full stack backtrace. Organise monitoring\u003Cbr \u002F>\nrules into named groups, enable\u002Fdisable per hook, and review the captured\u003Cbr \u002F>\noutput in a dedicated list view.\u003C\u002Fp>\n\u003Ch4>DB Table Manager\u003C\u002Fh4>\n\u003Cp>Browse, search, edit, and delete records across any table in your\u003Cbr \u002F>\nWordPress database — including custom plugin tables. Displays table size,\u003Cbr \u002F>\nengine, collation, row count, and schema information. Supports full and\u003Cbr \u002F>\nfiltered truncation and table drop with confirmation.\u003C\u002Fp>\n\u003Ch4>Server Info & System Status\u003C\u002Fh4>\n\u003Cp>Displays real-time server metrics (CPU load, memory usage, disk space,\u003Cbr \u002F>\nPHP version, active extensions) as both admin-bar badges and a dashboard\u003Cbr \u002F>\nwidget. Also provides a detailed environment report useful for support tickets\u003Cbr \u002F>\nand deployment checks.\u003C\u002Fp>\n\u003Ch4>Plugin Version Switcher\u003C\u002Fh4>\n\u003Cp>Roll back or switch between any previously downloaded version of an installed\u003Cbr \u002F>\nplugin without leaving the admin. Useful for quickly reverting after a bad\u003Cbr \u002F>\nupdate. Supports only free plugins from the WordPress repo.\u003C\u002Fp>\n\u003Ch4>Code Snippets\u003C\u002Fh4>\n\u003Cp>Write, save, and execute custom PHP snippets from the admin. Snippets support\u003Cbr \u002F>\nshortcodes, can be enabled\u002Fdisabled individually, and are sandboxed before\u003Cbr \u002F>\nexecution. Useful for one-off data migrations, testing custom logic, or\u003Cbr \u002F>\ngenerating dynamic output without creating a custom plugin.\u003C\u002Fp>\n\u003Ch4>REST API Manager\u003C\u002Fh4>\n\u003Cp>A security and management tool that gives full visibility and control over\u003Cbr \u002F>\nevery registered REST API endpoint (\u003Ccode>\u002Fwp-json\u002F\u003C\u002Fcode>). Inspect all registered\u003Cbr \u002F>\nroutes, disable individual endpoints, restrict HTTP methods, and hide routes\u003Cbr \u002F>\nfrom discovery responses. Useful for hardening your site by removing\u003Cbr \u002F>\nunnecessary API surface area.\u003C\u002Fp>\n\u003Ch4>WP Panel\u003C\u002Fh4>\n\u003Cp>A centralised control panel for toggling WordPress core features and settings.\u003Cbr \u002F>\nEnable or disable comments, revisions, auto-updates, XML-RPC, the REST API,\u003Cbr \u002F>\nemojis, embeds, heartbeat behaviour, frontend asset loading, and more — all\u003Cbr \u002F>\nfrom a single, organised admin page. No code changes or custom snippets\u003Cbr \u002F>\nrequired.\u003C\u002Fp>\n\u003Ch4>Recovery Mode\u003C\u002Fh4>\n\u003Cp>Generate single-use recovery links that can disable a specific plugin or\u003Cbr \u002F>\ntrigger a custom action — delivered via Slack, Telegram, or any configured\u003Cbr \u002F>\nwebhook channel. Designed for emergency recovery when the site is inaccessible\u003Cbr \u002F>\nthrough normal means. The recovery URLs are sent in Slack and Telegram channels for security.\u003C\u002Fp>\n\u003Ch4>Other Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Dark mode for all admin screens.\u003C\u002Fli>\n\u003Cli>CSV export on all list views (requests, errors, mails, hooks, etc.).\u003C\u002Fli>\n\u003Cli>Screen Options on every screen (configure columns, items per page).\u003C\u002Fli>\n\u003Cli>WP CLI compatible scaffolding for background operations.\u003C\u002Fli>\n\u003Cli>Multisite aware (note: recovery mode has core multisite limitations).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Short Description\u003C\u002Fh3>\n\u003Cp>All-in-one WordPress debug & operations toolkit: error log manager, PHP fatal\u003Cbr \u002F>\ntracker, cron & transient manager, mail logger, SMTP, outgoing requests viewer,\u003Cbr \u002F>\nDB table manager, site performance & security scanner, Google PageSpeed\u003Cbr \u002F>\nintegration, URL tracker, WP hooks monitor, code snippets, and recovery mode.\u003C\u002Fp>\n\u003Ch3>Requirements & Compatibility\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>WordPress 6.0+ (tested up to 6.9)\u003C\u002Fli>\n\u003Cli>PHP 7.4+ (compatible with PHP 8.0, 8.1, 8.2, 8.3, 8.4, 8.5)\u003C\u002Fli>\n\u003Cli>MySQL 5.7+ \u002F MariaDB 10.3+\u003C\u002Fli>\n\u003Cli>Not intended as a primary multisite recovery tool (see FAQ)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Best Practices & Security Notes\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Keep log files outside the webroot when possible, or restrict access via\u003Cbr \u002F>\nserver rules (.htaccess \u002F nginx) to prevent public exposure.\u003C\u002Fli>\n\u003Cli>Use the built-in “Randomise Log Filename” feature when logs must stay in the\u003Cbr \u002F>\nwebroot.\u003C\u002Fli>\n\u003Cli>All plugin capabilities are restricted to \u003Ccode>manage_options\u003C\u002Fcode> (administrators)\u003Cbr \u002F>\nby default. The menu can optionally be restricted to admins only.\u003C\u002Fli>\n\u003Cli>Sanitize and escape all output; nonces are enforced on all state-changing\u003Cbr \u002F>\nactions.\u003C\u002Fli>\n\u003Cli>Secure SMTP credentials using TLS\u002FSTARTTLS; credentials are stored in the\u003Cbr \u002F>\nWordPress options table.\u003C\u002Fli>\n\u003Cli>Set file permissions tightly (e.g., 600\u002F640) and restrict ownership to the\u003Cbr \u002F>\nweb server user.\u003C\u002Fli>\n\u003Cli>Backup database and files before using bulk delete or table truncation.\u003C\u002Fli>\n\u003Cli>Disable unused modules to reduce footprint and potential attack surface.\u003C\u002Fli>\n\u003Cli>Disable or throttle high-frequency background polling on high-load sites.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Usage Notes & Performance\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>The Error Log viewer reads the last N lines (default 100, max configurable\u003Cbr \u002F>\nvia Screen Options) to avoid full-file reads on GB-sized logs.\u003C\u002Fli>\n\u003Cli>No pagination on error logs by design — pagination would force repeated\u003Cbr \u002F>\nexpensive full-file reads.\u003C\u002Fli>\n\u003Cli>The PHP Fatal Error Tracker uses its own DB table; apply a retention policy\u003Cbr \u002F>\nin Settings to avoid unbounded growth.\u003C\u002Fli>\n\u003Cli>The Hooks Capture module adds minimal overhead per captured hook invocation;\u003Cbr \u002F>\ndisable capturing on production when not actively debugging.\u003C\u002Fli>\n\u003Cli>The URL Tracker records page visits in a custom table; configure retention\u003Cbr \u002F>\nor pause tracking on high-traffic sites.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Support & Notes\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Secure log paths and consider randomising filenames in production.\u003C\u002Fli>\n\u003Cli>Disable unused modules to reduce footprint and attack surface.\u003C\u002Fli>\n\u003Cli>Recovery Mode has limitations on multisite — test before relying on it.\u003C\u002Fli>\n\u003Cli>For bugs or feature requests, open an issue on the plugin page.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Live preview and full details:\u003Cbr \u002F>\nhttps:\u002F\u002Fwordpress.org\u002Fplugins\u002F0-day-analytics\u002F\u003C\u002Fp>\n\u003Cp>Plugin website and documentation:\u003Cbr \u002F>\nhttps:\u002F\u002F0-day-analytics.com\u003C\u002Fp>\n","0 Day Analytics is a comprehensive WordPress debugging and operational",40,5961,"2026-04-06T08:45:00.000Z","6.0",[18,19,20,51,21],"performance","https:\u002F\u002F0-day-analytics.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002F0-day-analytics.5.0.0.zip",99,1,"2025-11-12 00:00:00",{"slug":58,"name":59,"version":60,"author":61,"author_profile":62,"description":63,"short_description":64,"active_installs":11,"downloaded":65,"rating":11,"num_ratings":11,"last_updated":66,"tested_up_to":67,"requires_at_least":68,"requires_php":69,"tags":70,"homepage":73,"download_link":74,"security_score":75,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"all-in-one-debug-lab","All-in-One Debug Lab","1.0.0","panoskarras","https:\u002F\u002Fprofiles.wordpress.org\u002Fpanoskarras\u002F","\u003Cp>The “All-in-One Debug Lab” plugin, makes it easy to search and locate errors in wordpress.\u003C\u002Fp>\n\u003Ch4>View “debug.log” file\u003C\u002Fh4>\n\u003Cp>You can see the “debug.log” file, through this debug plugin.\u003C\u002Fp>\n\u003Ch4>Toggle Debugging\u003C\u002Fh4>\n\u003Cp>Now you can enable\u002Fdisable debugging with a click. No need to manually edit wp-config.php\u003C\u002Fp>\n\u003Ch4>Clear Log\u003C\u002Fh4>\n\u003Cp>Easily clear your “debug.log” file with one click.\u003C\u002Fp>\n\u003Ch4>Download Log\u003C\u002Fh4>\n\u003Cp>Easily download your “debug.log” file with one click.\u003C\u002Fp>\n","The \"All-in-One Debug Lab\" plugin, makes it easy to search and locate errors in wordpress.",1094,"2020-05-25T11:22:00.000Z","5.4.19","3.4","7.0",[19,71,72,20,22],"debug-log","develop","https:\u002F\u002Fwww.yourpluginwebsiteurl.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fall-in-one-debug-lab.zip",85,{"slug":77,"name":78,"version":79,"author":80,"author_profile":81,"description":82,"short_description":83,"active_installs":11,"downloaded":84,"rating":25,"num_ratings":55,"last_updated":85,"tested_up_to":14,"requires_at_least":86,"requires_php":69,"tags":87,"homepage":90,"download_link":91,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":92},"developer-debug-mode","Developer Debug Mode","1.2.5","Glimbyte","https:\u002F\u002Fprofiles.wordpress.org\u002Fglimbyte\u002F","\u003Cp>\u003Cstrong>Stop editing wp-config.php every time you need to debug your WordPress site.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Developer Debug Mode lets you toggle all WordPress debug constants directly from your dashboard with beautiful toggle switches. Changes save automatically — no clicking save buttons, no FTP access needed, no risk of syntax errors in your config file.\u003C\u002Fp>\n\u003Ch4>🎯 The Problem This Plugin Solves\u003C\u002Fh4>\n\u003Cp>Every WordPress developer knows the pain:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Something breaks on your site\u003C\u002Fli>\n\u003Cli>You need to enable WP_DEBUG to see the error\u003C\u002Fli>\n\u003Cli>You open FTP\u002FFile Manager, find wp-config.php, edit it carefully\u003C\u002Fli>\n\u003Cli>Debug the issue\u003C\u002Fli>\n\u003Cli>Remember to turn debug off before visitors see ugly error messages\u003C\u002Fli>\n\u003Cli>Repeat next time something breaks\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>\u003Cstrong>Developer Debug Mode eliminates steps 2-5 entirely.\u003C\u002Fstrong> Toggle debug on, find the error, toggle off. Done in seconds.\u003C\u002Fp>\n\u003Ch4>✨ Key Features\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>One-Click Debug Toggles\u003C\u002Fstrong>\u003Cbr \u002F>\nControl all six WordPress debug constants from a clean, modern interface:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>WP_DEBUG\u003C\u002Fstrong> — Master switch for WordPress debugging\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WP_DEBUG_LOG\u003C\u002Fstrong> — Save errors to wp-content\u002Fdebug.log\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WP_DEBUG_DISPLAY\u003C\u002Fstrong> — Show errors on screen (careful on production!)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>SCRIPT_DEBUG\u003C\u002Fstrong> — Use unminified core CSS\u002FJS files\u003C\u002Fli>\n\u003Cli>\u003Cstrong>SAVEQUERIES\u003C\u002Fstrong> — Log database queries for performance analysis\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WP_DISABLE_FATAL_ERROR_HANDLER\u003C\u002Fstrong> — See raw PHP fatal errors instead of recovery mode\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Admin Bar Quick Toggle\u003C\u002Fstrong> \u003Cem>(New in 1.2.0!)\u003C\u002Fem>\u003Cbr \u002F>\nToggle any debug constant directly from the WordPress admin bar — no need to visit the settings page. Perfect for quick debugging sessions.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Built-in Debug Log Viewer\u003C\u002Fstrong>\u003Cbr \u002F>\nView, search, download, and clear your debug.log without leaving WordPress:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Color-coded entries (fatal, error, warning, notice)\u003C\u002Fli>\n\u003Cli>Search with highlighting\u003C\u002Fli>\n\u003Cli>Auto-refresh option for real-time monitoring\u003C\u002Fli>\n\u003Cli>One-click download and clear\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Auto-Save Technology\u003C\u002Fstrong>\u003Cbr \u002F>\nChanges save instantly as you toggle. No save button, no page refresh, no waiting.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Frontend Debug Warning\u003C\u002Fstrong>\u003Cbr \u002F>\nA tasteful notification bar appears when WP_DEBUG_DISPLAY is active, reminding you to turn it off before visitors see error messages.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Cross-Tab Synchronization\u003C\u002Fstrong>\u003Cbr \u002F>\nToggle debug in one browser tab and watch other open tabs update instantly.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Automatic Backups\u003C\u002Fstrong>\u003Cbr \u002F>\nEvery change creates a backup of wp-config.php. The plugin keeps the 5 most recent backups, so you can always recover if something goes wrong.\u003C\u002Fp>\n\u003Ch4>🔧 Perfect For\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Theme developers\u003C\u002Fstrong> debugging template issues\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Plugin developers\u003C\u002Fstrong> testing new code\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Site administrators\u003C\u002Fstrong> troubleshooting problems\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Agencies\u003C\u002Fstrong> managing multiple client sites\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Freelancers\u003C\u002Fstrong> who need quick debugging without FTP access\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Anyone\u003C\u002Fstrong> tired of manually editing wp-config.php\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>💡 Why Choose Developer Debug Mode?\u003C\u002Fh4>\n\u003Cp>Unlike other debug plugins, we focus on \u003Cstrong>user experience\u003C\u002Fstrong>:\u003C\u002Fp>\n\u003Cp>✅ \u003Cstrong>Instant toggles\u003C\u002Fstrong> — No save buttons, changes apply immediately\u003Cbr \u002F>\n✅ \u003Cstrong>Visual feedback\u003C\u002Fstrong> — Clear status indicators show exactly what’s enabled\u003Cbr \u002F>\n✅ \u003Cstrong>Admin bar access\u003C\u002Fstrong> — Toggle debug from anywhere in WordPress\u003Cbr \u002F>\n✅ \u003Cstrong>Production-safe\u003C\u002Fstrong> — Frontend warnings prevent accidentally exposing errors\u003Cbr \u002F>\n✅ \u003Cstrong>Modern design\u003C\u002Fstrong> — Beautiful UI that fits naturally in your dashboard\u003Cbr \u002F>\n✅ \u003Cstrong>Lightweight\u003C\u002Fstrong> — No bloat, loads only where needed\u003C\u002Fp>\n\u003Ch4>🔒 Built With Security In Mind\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Capability checks ensure only administrators can change settings\u003C\u002Fli>\n\u003Cli>Nonce verification on all AJAX requests\u003C\u002Fli>\n\u003Cli>Automatic wp-config.php backups before every change\u003C\u002Fli>\n\u003Cli>No data sent to external servers\u003C\u002Fli>\n\u003Cli>Clean uninstall removes all plugin data\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>📚 Debug Constants Explained\u003C\u002Fh4>\n\u003Cp>Not sure what each constant does? Here’s a quick guide:\u003C\u002Fp>\n\u003Cp>\u003Cstrong>WP_DEBUG\u003C\u002Fstrong>\u003Cbr \u002F>\nThe master switch. When enabled, WordPress will display PHP errors, notices, and warnings. Required for the other debug constants to work.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>WP_DEBUG_LOG\u003C\u002Fstrong>\u003Cbr \u002F>\nSaves all debug messages to \u003Ccode>\u002Fwp-content\u002Fdebug.log\u003C\u002Fcode>. Essential for debugging issues that happen in the background (AJAX, cron jobs, REST API).\u003C\u002Fp>\n\u003Cp>\u003Cstrong>WP_DEBUG_DISPLAY\u003C\u002Fstrong>\u003Cbr \u002F>\nShows errors directly on your web pages. Useful during development but \u003Cstrong>never enable on production\u003C\u002Fstrong> — it can expose sensitive information to visitors.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>SCRIPT_DEBUG\u003C\u002Fstrong>\u003Cbr \u002F>\nForces WordPress to use the development versions of core CSS and JavaScript files instead of minified versions. Helpful when debugging scripts.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>SAVEQUERIES\u003C\u002Fstrong>\u003Cbr \u002F>\nStores database queries in a global array for later analysis. Useful for identifying slow queries but adds overhead — disable when not needed.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>WP_DISABLE_FATAL_ERROR_HANDLER\u003C\u002Fstrong>\u003Cbr \u002F>\nDisables WordPress’s “recovery mode” so you see the actual PHP fatal error instead of “There has been a critical error on this website.”\u003C\u002Fp>\n\u003Ch4>🤝 Support & Documentation\u003C\u002Fh4>\n\u003Cp>Need help? We offer:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Free Support\u003C\u002Fstrong> — Post in the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fdeveloper-debug-mode\u002F\" rel=\"ugc\">WordPress.org support forum\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Documentation\u003C\u002Fstrong> — Visit \u003Ca href=\"https:\u002F\u002Fglimbyte.ie\" rel=\"nofollow ugc\">glimbyte.ie\u003C\u002Fa> for guides and tutorials\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Express Support\u003C\u002Fstrong> — Fast turnaround for urgent issues via \u003Ca href=\"https:\u002F\u002Fglimbyte.ie\u002Fsupport\" rel=\"nofollow ugc\">glimbyte.ie\u002Fsupport\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>🌐 Works Great With\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Query Monitor\u003C\u002Fstrong> — Use alongside for deeper debugging\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Debug Bar\u003C\u002Fstrong> — Compatible with Debug Bar and its add-ons\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Any caching plugin\u003C\u002Fstrong> — Clear cache after toggling debug constants\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Managed WordPress hosts\u003C\u002Fstrong> — Works on most hosts including Kinsta, WP Engine, SiteGround\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Credits\u003C\u002Fh3>\n\u003Cp>Developed with ❤️ by \u003Ca href=\"https:\u002F\u002Fglimbyte.ie\" rel=\"nofollow ugc\">Glimbyte\u003C\u002Fa> — WordPress Development & Support.\u003C\u002Fp>\n\u003Cp>Special thanks to the WordPress community for feedback and suggestions.\u003C\u002Fp>\n\u003Ch3>Privacy Policy\u003C\u002Fh3>\n\u003Cp>Developer Debug Mode does not collect, store, or transmit any personal data. All settings are stored locally in your WordPress database and wp-config.php file.\u003C\u002Fp>\n\u003Cp>The optional support contact form (available in the plugin settings) sends data directly to Glimbyte’s support team. This data is handled according to \u003Ca href=\"https:\u002F\u002Fglimbyte.ie\u002Fprivacy\" rel=\"nofollow ugc\">Glimbyte’s Privacy Policy\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Additional Info\u003C\u002Fh3>\n\u003Ch4>Contribute\u003C\u002Fh4>\n\u003Cp>Found a bug or have a feature request? We’d love to hear from you!\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Support Forum:\u003C\u002Fstrong> \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fdeveloper-debug-mode\u002F\" rel=\"ugc\">wordpress.org\u002Fsupport\u002Fplugin\u002Fdeveloper-debug-mode\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Website:\u003C\u002Fstrong> \u003Ca href=\"https:\u002F\u002Fglimbyte.ie\" rel=\"nofollow ugc\">glimbyte.ie\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Translations\u003C\u002Fh4>\n\u003Cp>Want to help translate Developer Debug Mode into your language? Visit \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Fprojects\u002Fwp-plugins\u002Fdeveloper-debug-mode\u002F\" rel=\"nofollow ugc\">translate.wordpress.org\u003C\u002Fa> to contribute.\u003C\u002Fp>\n","Toggle WordPress debug mode instantly. No wp-config.php editing needed. Features auto-save, admin bar quick toggle, and debug log viewer.",105,"2026-02-06T13:02:00.000Z","5.0",[19,88,20,89,22],"developer-tools","troubleshooting","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdeveloper-debug-mode.1.2.5.zip","2026-03-15T15:16:48.613Z",{"slug":94,"name":95,"version":96,"author":97,"author_profile":98,"description":99,"short_description":100,"active_installs":101,"downloaded":102,"rating":103,"num_ratings":104,"last_updated":105,"tested_up_to":14,"requires_at_least":106,"requires_php":16,"tags":107,"homepage":111,"download_link":112,"security_score":113,"vuln_count":114,"unpatched_count":11,"last_vuln_date":115,"fetched_at":27},"wp-crontrol","WP Crontrol","1.21.0","John Blackbourn","https:\u002F\u002Fprofiles.wordpress.org\u002Fjohnbillion\u002F","\u003Cp>WP Crontrol enables you to take control of the scheduled cron events on your WordPress website or WooCommerce store. From the admin screens you can:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>View all scheduled cron events along with their arguments, schedule, callback functions, and when they are next due.\u003C\u002Fli>\n\u003Cli>Edit, delete, pause, resume, and immediately run cron events.\u003C\u002Fli>\n\u003Cli>Add new cron events.\u003C\u002Fli>\n\u003Cli>Bulk delete cron events.\u003C\u002Fli>\n\u003Cli>Add and remove custom cron schedules.\u003C\u002Fli>\n\u003Cli>Export and download cron event lists as a CSV file.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>WP Crontrol is aware of timezones, will alert you to events that have no actions or that have missed their schedule, and will show you a helpful warning message if it detects any problems with your cron system.\u003C\u002Fp>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Go to the \u003Ccode>Tools \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Cron Events\u003C\u002Fcode> menu to manage cron events.\u003C\u002Fli>\n\u003Cli>Go to the \u003Ccode>Settings \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Cron Schedules\u003C\u002Fcode> menu to manage cron schedules.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>Documentation\u003C\u002Fh3>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwp-crontrol.com\u002Fdocs\u002Fhow-to-use\u002F\" rel=\"nofollow ugc\">Extensive documentation on how to use WP Crontrol and how to get help for error messages that it shows is available on the WP Crontrol website\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>For site owners\u003C\u002Fh3>\n\u003Cp>Owners of WordPress websites and WooCommerce stores use WP Crontrol to ensure that scheduled cron events run correctly and efficiently. By providing complete control over cron events, WP Crontrol helps you:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Improve reliability\u003C\u002Fstrong>: Address missed or failed cron events, ensuring your website or WooCommerce store continues to function as expected.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Enhance security\u003C\u002Fstrong>: Monitor and control cron events to ensure automatic update checks are performed as they should.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Simplify management\u003C\u002Fstrong>: Add, edit, delete, and pause cron events from a user-friendly interface, without needing to write any code.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Gain insights\u003C\u002Fstrong>: Export cron event data for analysis or reporting.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Action Scheduler compatibility\u003C\u002Fstrong>: Full support for the Action Scheduler system in WooCommerce, which is used to process recurring payments, subscriptions, and background orders.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Clarity of times and timezones\u003C\u002Fstrong>: All times are shown with a clear and accurate indication of which timezone applies. No more guesswork!\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>For developers\u003C\u002Fh3>\n\u003Cp>Developers use WP Crontrol to streamline and debug their WordPress development process:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Enhanced debugging\u003C\u002Fstrong>: Identify and troubleshoot issues with scheduled tasks, ensuring your scheduled events and their callbacks run as expected.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Custom schedules\u003C\u002Fstrong>: Create and manage custom cron schedules to fit the specific needs of your website, plugins, or themes, providing greater flexibility than just the core schedules.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Efficient workflow\u003C\u002Fstrong>: Add, edit, and delete cron events directly from the WordPress admin interface, saving time and reducing the need for manual coding.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Insightful monitoring\u003C\u002Fstrong>: Get insight into the performance and behavior of your scheduled tasks, allowing for optimization and better resource management.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Accurate debugging\u003C\u002Fstrong>: WP Crontrol goes to great lengths to ensure that running an event manually does so in a manner which exactly matches how WordPress core runs schdeuled events. This ensures that you can debug events accurately and with confidence.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Other Plugins\u003C\u002Fh3>\n\u003Cp>I maintain several other plugins for developers. Check them out:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fquery-monitor\u002F\" rel=\"ugc\">Query Monitor\u003C\u002Fa> is the developer tools panel for WordPress.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fuser-switching\u002F\" rel=\"ugc\">User Switching\u003C\u002Fa> provides instant switching between user accounts in WordPress.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Privacy Statement\u003C\u002Fh3>\n\u003Cp>WP Crontrol is private by default and always will be. It does not send data to any third party, nor does it include any third party resources. \u003Ca href=\"https:\u002F\u002Fwp-crontrol.com\u002Fprivacy\u002F\" rel=\"nofollow ugc\">WP Crontrol’s full privacy statement can be found here\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Accessibility Statement\u003C\u002Fh3>\n\u003Cp>WP Crontrol aims to be fully accessible to all of its users. \u003Ca href=\"https:\u002F\u002Fwp-crontrol.com\u002Faccessibility\u002F\" rel=\"nofollow ugc\">WP Crontrol’s full accessibility statement can be found here\u003C\u002Fa>.\u003C\u002Fp>\n","WP Crontrol enables you to take control of the cron events on your WordPress website.",300000,7676515,90,163,"2026-01-28T21:40:00.000Z","6.4",[18,108,19,109,110],"crontrol","woocommerce","wp-cron","https:\u002F\u002Fwp-crontrol.com","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-crontrol.1.21.0.zip",96,3,"2025-08-21 00:00:00",{"slug":117,"name":118,"version":119,"author":120,"author_profile":121,"description":122,"short_description":123,"active_installs":124,"downloaded":125,"rating":25,"num_ratings":126,"last_updated":127,"tested_up_to":128,"requires_at_least":15,"requires_php":129,"tags":130,"homepage":132,"download_link":133,"security_score":134,"vuln_count":32,"unpatched_count":11,"last_vuln_date":135,"fetched_at":27},"wp-debugging","WP Debugging","2.12.2","Andy Fragen","https:\u002F\u002Fprofiles.wordpress.org\u002Fafragen\u002F","\u003Cp>This plugin sets the following debug constants in \u003Ccode>wp-config.php\u003C\u002Fcode> on plugin activation and removes them on plugin deactivation. Any errors will result in a PHP Exception being thrown. Debug constants per \u003Ca href=\"https:\u002F\u002Fdeveloper.wordpress.org\u002Fadvanced-administration\u002Fdebug\u002Fdebug-wordpress\u002F\" rel=\"nofollow ugc\">Debugging in WordPress\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Default settings:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'WP_DEBUG_LOG', true );\ndefine( 'SCRIPT_DEBUG', true );\ndefine( 'SAVEQUERIES', true );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp> \u003Cbr \u002F>\n    @ini_set( ‘display_errors’, 1 ); is set when the plugin is active. \u003Ccode>WP_DEBUG\u003C\u002Fcode> is set to true when the plugin is first run, thereafter it can be turned off in the Settings.\u003C\u002Fp>\n\u003Cp>The Settings page allows the user to set the following.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'WP_DEBUG', true ); \u002F\u002F Default on initial plugin installation.\ndefine( 'WP_DEBUG_DISPLAY', false ); \u002F\u002F Default when not declared is true.\ndefine( 'WP_DISABLE_FATAL_ERROR_HANDLER', true ); \u002F\u002F WordPress 5.2 WSOD Override.\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>When the plugin is deactivated best efforts are made to re-add pre-existing constants to their former state. When the plugin is activated the default settings and any saved settings are restored.\u003C\u002Fp>\n\u003Cp>This plugin uses the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fwp-cli\u002Fwp-config-transformer\" rel=\"nofollow ugc\">wp-cli\u002Fwp-config-transformer\u003C\u002Fa> command for writing constants to \u003Ccode>wp-config.php\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fnorcross\u002Fdebug-quick-look\" rel=\"nofollow ugc\">Debug Quick Look\u003C\u002Fa> from Andrew Norcross is included with this plugin to assist in reading the debug.log file. If you already have this plugin installed you should delete it when WP Debugging is not active.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fquery-monitor\u002F\" rel=\"ugc\">Query Monitor\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdebug-bar\u002F\" rel=\"ugc\">Debug Bar\u003C\u002Fa> plugins are optional dependencies to aid in debugging and troubleshooting. The notice for installation will recur 45 days after being dismissed.\u003C\u002Fp>\n\u003Cp>If you have a non-standard location for your \u003Ccode>wp-config.php\u003C\u002Fcode> file you can use the filter \u003Ccode>wp_debugging_config_path\u003C\u002Fcode> to return the file path for your installation.\u003C\u002Fp>\n\u003Cp>The filter \u003Ccode>wp_debugging_add_constants\u003C\u002Fcode> allows the user to add constants to \u003Ccode>wp-config.php\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>The filter returns an array where the key is the name of the constant and the value is an array of data containing the value as a string and a boolean to indicate whether or not the value should be passed without quotes.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$my_constants = [\n    'my_test_constant' =>\n    [\n        'value' => 'abc123',\n        'raw' => false,\n    ],\n    'another_test_constant' => [ 'value' => 'true' ],\n];\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The \u003Ccode>value\u003C\u002Fcode> option contains the constant’s value as a string.\u003C\u002Fp>\n\u003Cp>The \u003Ccode>raw\u003C\u002Fcode> option means that instead of placing the value inside the config as a string it will become unquoted. The default is \u003Ccode>true\u003C\u002Fcode>. Set as \u003Ccode>false\u003C\u002Fcode> for non-boolean values.\u003C\u002Fp>\n\u003Cp>Example:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_filter(\n    'wp_debugging_add_constants',\n    function( $added_constants ) {\n        $my_constants = [\n            'my_test_constant'      => [\n                'value' => '124xyz',\n                'raw'   => false,\n            ],\n            'another_test_constant' => [ 'value' => 'true' ],\n        ];\n        return array_merge( $added_constants, $my_constants );\n    },\n    10,\n    1\n);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>This will create the following constants.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'MY_TEST_CONSTANT', '124xyz' );\ndefine( 'ANOTHER_TEST_CONSTANT', true );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3>Development\u003C\u002Fh3>\n\u003Cp>PRs are welcome against the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fafragen\u002Fwp-debugging\" rel=\"nofollow ugc\">develop branch on GitHub\u003C\u002Fa>.\u003C\u002Fp>\n","A support\u002Ftroubleshooting plugin for WordPress.",10000,434772,19,"2024-12-02T19:42:00.000Z","6.8.5","5.6",[19,131,22],"support","https:\u002F\u002Fgithub.com\u002Fafragen\u002Fwp-debugging","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-debugging.2.12.2.zip",91,"2022-01-24 00:00:00",{"attackSurface":137,"codeSignals":245,"taintFlows":286,"riskAssessment":314,"analyzedAt":322},{"hooks":138,"ajaxHandlers":195,"restRoutes":242,"shortcodes":243,"cronEvents":244,"entryPointCount":174,"unprotectedCount":11},[139,144,147,151,155,158,161,164,168,171,176,181,185,190,193],{"type":140,"name":141,"callback":141,"priority":55,"file":142,"line":143},"action","plugins_loaded","globus-debug-control.php",95,{"type":140,"name":145,"callback":146,"file":142,"line":113},"wp_loaded","on_wp_loaded",{"type":140,"name":148,"callback":149,"file":142,"line":150},"admin_init","register_settings",97,{"type":140,"name":152,"callback":153,"file":142,"line":154},"admin_menu","add_settings_page",98,{"type":140,"name":156,"callback":157,"priority":55,"file":142,"line":54},"after_setup_theme","early_body_class_filter",{"type":140,"name":159,"callback":160,"file":142,"line":25},"admin_enqueue_scripts","admin_enqueue_php_error_assets",{"type":140,"name":159,"callback":162,"file":142,"line":163},"admin_enqueue_settings_assets",101,{"type":140,"name":165,"callback":166,"file":142,"line":167},"wp_enqueue_scripts","frontend_enqueue_php_error_assets",102,{"type":140,"name":148,"callback":169,"file":142,"line":170},"handle_module_actions",103,{"type":140,"name":172,"callback":173,"priority":174,"file":142,"line":175},"http_api_debug","on_request",10,111,{"type":177,"name":178,"callback":179,"file":142,"line":180},"filter","body_class","filter_body_class",114,{"type":177,"name":182,"callback":183,"file":142,"line":184},"admin_body_class","filter_admin_body_class",115,{"type":177,"name":186,"callback":187,"priority":188,"file":142,"line":189},"enable_wp_debug_mode_checks","__return_false",999,117,{"type":177,"name":178,"callback":179,"file":191,"line":192},"include\u002Ftrait-admin-page.php",242,{"type":177,"name":182,"callback":183,"file":191,"line":194},243,[196,203,207,211,215,220,224,229,233,238],{"action":197,"nopriv":198,"callback":199,"hasNonce":200,"hasCapCheck":200,"file":201,"line":202},"gdc_cron_sources",false,"ajax_cron_sources",true,"include\u002Fcron-viewer.php",579,{"action":204,"nopriv":198,"callback":205,"hasNonce":200,"hasCapCheck":200,"file":201,"line":206},"gdc_cron_sources_stream","ajax_cron_sources_stream",580,{"action":208,"nopriv":198,"callback":209,"hasNonce":200,"hasCapCheck":200,"file":201,"line":210},"gdc_cron_run","ajax_cron_run",581,{"action":212,"nopriv":198,"callback":213,"hasNonce":200,"hasCapCheck":200,"file":201,"line":214},"gdc_cron_delete","ajax_cron_delete",582,{"action":216,"nopriv":198,"callback":217,"hasNonce":200,"hasCapCheck":200,"file":218,"line":219},"gdc_http_log_clear","ajax_clear","include\u002Fhttp-log.php",59,{"action":221,"nopriv":198,"callback":222,"hasNonce":200,"hasCapCheck":200,"file":218,"line":223},"gdc_http_log_toggle","ajax_toggle",60,{"action":225,"nopriv":198,"callback":226,"hasNonce":200,"hasCapCheck":200,"file":227,"line":228},"gdc_log_status","ajax_log_status","include\u002Flog-viewer.php",132,{"action":230,"nopriv":198,"callback":231,"hasNonce":200,"hasCapCheck":200,"file":227,"line":232},"gdc_generate_error","ajax_generate_error",133,{"action":234,"nopriv":198,"callback":235,"hasNonce":200,"hasCapCheck":200,"file":236,"line":237},"gdc_transient_delete","ajax_delete","include\u002Ftransient-viewer.php",28,{"action":239,"nopriv":198,"callback":240,"hasNonce":200,"hasCapCheck":200,"file":236,"line":241},"gdc_transient_purge","ajax_purge_expired",29,[],[],[],{"dangerousFunctions":246,"sqlUsage":264,"outputEscaping":267,"fileOperations":283,"externalRequests":11,"nonceChecks":283,"capabilityChecks":284,"bundledLibraries":285},[247,252,255,258,261],{"fn":248,"file":249,"line":250,"context":251},"ini_set","include\u002Ftrait-error-control.php",254,"ini_set( 'display_errors', $display );",{"fn":248,"file":249,"line":253,"context":254},256,"ini_set( 'display_startup_errors', $display );",{"fn":248,"file":249,"line":256,"context":257},266,"ini_set( 'log_errors', '0' ); \u002F\u002F phpcs:ignore Squiz.PHP.DiscouragedFunctions.Discouraged -- Required",{"fn":248,"file":249,"line":259,"context":260},279,"ini_set( 'log_errors', '1' ); \u002F\u002F phpcs:ignore Squiz.PHP.DiscouragedFunctions.Discouraged -- Required",{"fn":248,"file":249,"line":262,"context":263},280,"ini_set( 'error_log', $log_path ); \u002F\u002F phpcs:ignore Squiz.PHP.DiscouragedFunctions.Discouraged -- Req",{"prepared":265,"raw":11,"locations":266},5,[],{"escaped":268,"rawEcho":269,"locations":270},347,6,[271,274,276,278,279,281],{"file":201,"line":272,"context":273},62,"raw output",{"file":201,"line":275,"context":273},734,{"file":218,"line":277,"context":273},150,{"file":227,"line":250,"context":273},{"file":227,"line":280,"context":273},361,{"file":236,"line":282,"context":273},157,13,14,[],[287,305],{"entryPoint":288,"graph":289,"unsanitizedCount":114,"severity":304},"render (include\u002Flog-viewer.php:211)",{"nodes":290,"edges":302},[291,296],{"id":292,"type":293,"label":294,"file":227,"line":295},"n0","source","$_GET (x3)",213,{"id":297,"type":298,"label":299,"file":227,"line":300,"wp_function":301},"n1","sink","echo() [XSS]",377,"echo",[303],{"from":292,"to":297,"sanitized":198},"medium",{"entryPoint":306,"graph":307,"unsanitizedCount":11,"severity":313},"\u003Clog-viewer> (include\u002Flog-viewer.php:0)",{"nodes":308,"edges":311},[309,310],{"id":292,"type":293,"label":294,"file":227,"line":295},{"id":297,"type":298,"label":299,"file":227,"line":300,"wp_function":301},[312],{"from":292,"to":297,"sanitized":200},"low",{"summary":315,"deductions":316},"The \"globus-debug-control\" plugin v2.2.5 exhibits a generally strong security posture, with robust use of security best practices.  All identified AJAX handlers include authentication checks, and no shortcodes, cron events, or REST API routes were found, significantly limiting the plugin's attack surface. The code also demonstrates excellent SQL sanitation through the exclusive use of prepared statements and a very high percentage (98%) of properly escaped output. Furthermore, the presence of nonce and capability checks on all entry points and file operations indicates a deliberate effort to secure these areas. The plugin has no recorded vulnerability history, which is a very positive indicator.\n\nHowever, a few areas warrant attention. The presence of five instances of the `ini_set` function, while not inherently a vulnerability, can be a risk if misused to alter sensitive PHP configurations in a way that could be exploited. Additionally, the taint analysis revealed one flow with an unsanitized path. While no critical or high severity issues were flagged in the taint analysis, an unsanitized path represents a potential entry point for path traversal or file inclusion vulnerabilities. The absence of external HTTP requests is a positive aspect, reducing the risk of server-side request forgery (SSRF) or compromised external services.\n\nIn conclusion, the \"globus-debug-control\" plugin v2.2.5 is largely well-secured, with strong adherence to common WordPress security practices. The lack of historical vulnerabilities and the secure handling of SQL and output are significant strengths. The primary concerns are the potential risks associated with the use of `ini_set` and the single identified unsanitized path flow, which, though not rated as critical, should be addressed to further strengthen the plugin's security.",[317,320],{"reason":318,"points":319},"Unsanitized path flow found",7,{"reason":321,"points":265},"Use of dangerous function (ini_set)","2026-04-16T14:51:51.859Z",{"wat":324,"direct":353},{"assetPaths":325,"generatorPatterns":338,"scriptPaths":339,"versionParams":340},[326,327,328,329,330,331,332,333,334,335,336,337],"\u002Fwp-content\u002Fplugins\u002Fglobus-debug-control\u002Fassets\u002Fcss\u002Fadmin-error-log-viewer.css","\u002Fwp-content\u002Fplugins\u002Fglobus-debug-control\u002Fassets\u002Fcss\u002Fadmin-settings.css","\u002Fwp-content\u002Fplugins\u002Fglobus-debug-control\u002Fassets\u002Fcss\u002Ffrontend-php-error-display.css","\u002Fwp-content\u002Fplugins\u002Fglobus-debug-control\u002Fassets\u002Fcss\u002Fgdc-admin-page.css","\u002Fwp-content\u002Fplugins\u002Fglobus-debug-control\u002Fassets\u002Fjs\u002Fadmin-cron-viewer.js","\u002Fwp-content\u002Fplugins\u002Fglobus-debug-control\u002Fassets\u002Fjs\u002Fadmin-error-log-viewer.js","\u002Fwp-content\u002Fplugins\u002Fglobus-debug-control\u002Fassets\u002Fjs\u002Fadmin-http-log.js","\u002Fwp-content\u002Fplugins\u002Fglobus-debug-control\u002Fassets\u002Fjs\u002Fadmin-settings.js","\u002Fwp-content\u002Fplugins\u002Fglobus-debug-control\u002Fassets\u002Fjs\u002Fadmin-transient-viewer.js","\u002Fwp-content\u002Fplugins\u002Fglobus-debug-control\u002Fassets\u002Fjs\u002Fconstants-viewer.js","\u002Fwp-content\u002Fplugins\u002Fglobus-debug-control\u002Fassets\u002Fjs\u002Fgdc-admin-page.js","\u002Fwp-content\u002Fplugins\u002Fglobus-debug-control\u002Fassets\u002Fjs\u002Ffrontend-php-error-display.js",[],[330,331,332,333,334,335,336,337],[341,342,343,344,345,346,347,348,349,350,351,352],"globus-debug-control\u002Fassets\u002Fcss\u002Fadmin-error-log-viewer.css?ver=","globus-debug-control\u002Fassets\u002Fcss\u002Fadmin-settings.css?ver=","globus-debug-control\u002Fassets\u002Fcss\u002Ffrontend-php-error-display.css?ver=","globus-debug-control\u002Fassets\u002Fcss\u002Fgdc-admin-page.css?ver=","globus-debug-control\u002Fassets\u002Fjs\u002Fadmin-cron-viewer.js?ver=","globus-debug-control\u002Fassets\u002Fjs\u002Fadmin-error-log-viewer.js?ver=","globus-debug-control\u002Fassets\u002Fjs\u002Fadmin-http-log.js?ver=","globus-debug-control\u002Fassets\u002Fjs\u002Fadmin-settings.js?ver=","globus-debug-control\u002Fassets\u002Fjs\u002Fadmin-transient-viewer.js?ver=","globus-debug-control\u002Fassets\u002Fjs\u002Fconstants-viewer.js?ver=","globus-debug-control\u002Fassets\u002Fjs\u002Fgdc-admin-page.js?ver=","globus-debug-control\u002Fassets\u002Fjs\u002Ffrontend-php-error-display.js?ver=",{"cssClasses":354,"htmlComments":359,"htmlAttributes":360,"restEndpoints":362,"jsGlobals":363,"shortcodeOutput":364},[355,356,357,358],"gdc-debug-badge","gdc-debug-on","gdc-debug-off","gdc-tab-content",[],[361],"data-gdc-tab",[],[],[],{"error":200,"url":366,"statusCode":367,"statusMessage":368,"message":368},"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Fglobus-debug-control\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":32,"versions":370},[371,376],{"version":6,"download_url":24,"svn_tag_url":372,"released_at":26,"has_diff":198,"diff_files_changed":373,"diff_lines":26,"trac_diff_url":374,"vulnerabilities":375,"is_current":200},"https:\u002F\u002Fplugins.svn.wordpress.org\u002Fglobus-debug-control\u002Ftags\u002F2.2.5\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fglobus-debug-control%2Ftags%2F2.2.4&new_path=%2Fglobus-debug-control%2Ftags%2F2.2.5",[],{"version":377,"download_url":378,"svn_tag_url":379,"released_at":26,"has_diff":198,"diff_files_changed":380,"diff_lines":26,"trac_diff_url":26,"vulnerabilities":381,"is_current":198},"2.2.4","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fglobus-debug-control.2.2.4.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fglobus-debug-control\u002Ftags\u002F2.2.4\u002F",[],[]]