[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f0h7uM0Zqv3AI4TR1Ziu5bKQVT5S4XLZygM9YB0sXzkM":3,"$friFNdEKPgc2SRoreCw2VPLHAw7bZSyPXYaWuQ0fCqC0":442,"$fi7WT-Yua6VLsLQxD5VW-DAP33N2CpvlhSiI1VsflXBA":446},{"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":22,"download_link":23,"security_score":24,"vuln_count":11,"unpatched_count":11,"last_vuln_date":25,"fetched_at":26,"discovery_status":27,"vulnerabilities":28,"developer":29,"crawl_stats":25,"alternatives":35,"analysis":128,"fingerprints":419},"user-id","User ID","2.0.0","Aditya Shah","https:\u002F\u002Fprofiles.wordpress.org\u002Fethicaladitya\u002F","\u003Cp>User ID has evolved from a simple column displaying user IDs into the \u003Cstrong>most comprehensive Support and Debug Toolkit\u003C\u002Fstrong> for WordPress available. Whether you are a site administrator, support staff, or developer, this plugin equips you with everything needed to inspect, track, impersonate, and debug WordPress users efficiently.\u003C\u002Fp>\n\u003Cp>While preserving the core lightweight “User ID” column in the Users table and the \u003Ccode>[user-id]\u003C\u002Fcode> shortcode for complete backward compatibility, the 2.0.0 update introduces powerful, modular features designed to supercharge your WordPress user management workflow.\u003C\u002Fp>\n\u003Ch3>Core Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>User ID Column\u003C\u002Fstrong>: Instantly see and copy User IDs directly from the WordPress Users table. Stop searching for ways to find WordPress user IDs.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Deep User Search\u003C\u002Fstrong>: Stop relying on basic wp-admin search. Our advanced search interface is capable of searching users by ID, email, username, and even hidden user meta values inside the \u003Ccode>wp_usermeta\u003C\u002Fcode> table.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WordPress User Inspector\u003C\u002Fstrong>: A detailed view of any user account exhibiting basic information, a full list of their capabilities, and a raw User Meta table viewer to debug exactly what custom fields a user has attached.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Secure User Impersonation\u003C\u002Fstrong>: Need to test what a specific user is experiencing? Securely log in as any user (impersonate user) with a single click, without needing their password. Includes a persistent return-to-admin button and logs the action for security.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>User Activity Log & Login Tracker\u003C\u002Fstrong>: Keep track of user history. View log entries of when users log in, log out, update their profiles, or change passwords. View the last 10 logins directly on their User Debug pane.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Support Mode\u003C\u002Fstrong>: An optional setting that enables a quick-access “User Debug” dropdown in the WordPress Admin Bar, improving support agent efficiency.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Developer Extensibility\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>WP-CLI Support\u003C\u002Fstrong>: Use \u003Ccode>wp user-id inspect \u003Cid>\u003C\u002Fcode> to instantly retrieve user data and capabilities from the command line without opening the dashboard.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>REST API Endpoints\u003C\u002Fstrong>: Integrates seamlessly with the wp-json endpoints via \u003Ccode>\u002Fwp-json\u002Fuser-id\u002Fv1\u002Finspect\u002F\u003Cid>\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Filters & Actions\u003C\u002Fstrong>: Leverage hooks like \u003Ccode>user_id_activity\u003C\u002Fcode> and \u003Ccode>apply_filters('user_id_meta_keys')\u003C\u002Fcode> to extend the toolkit tracker functionality with your own custom events.\u003C\u002Fli>\n\u003C\u002Ful>\n","A powerful WordPress user manager to impersonate users, track activity logs, debug meta, and find user IDs. The ultimate user support toolkit.",0,1532,"2026-03-16T05:50:00.000Z","6.9.5","6.0","8.0",[18,19,20,21,4],"activity-log","debug","developer-tools","impersonate","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fuser-id\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fuser-id.2.0.0.zip",100,null,"2026-07-22T17:31:50.256Z","no_bundle",[],{"slug":30,"display_name":7,"profile_url":8,"plugin_count":31,"total_installs":11,"avg_security_score":24,"avg_patch_time_days":32,"trust_score":33,"computed_at":34},"ethicaladitya",2,30,94,"2026-08-29T02:10:27.283Z",[36,61,79,95,112],{"slug":37,"name":38,"version":39,"author":40,"author_profile":41,"description":42,"short_description":43,"active_installs":44,"downloaded":45,"rating":46,"num_ratings":47,"last_updated":48,"tested_up_to":49,"requires_at_least":50,"requires_php":51,"tags":52,"homepage":56,"download_link":57,"security_score":58,"vuln_count":59,"unpatched_count":11,"last_vuln_date":60,"fetched_at":26},"debug-log-viewer","Debug Log Viewer","2.4","Oleksandr Lysyi","https:\u002F\u002Fprofiles.wordpress.org\u002Flysyiweb\u002F","\u003Ch4>Debug Log Viewer: Your Essential WordPress Debugging Tool\u003C\u002Fh4>\n\u003Cp>Tired of struggling to access and understand your WordPress debug.log\u003Cbr \u002F>\nfile?\u003C\u002Fp>\n\u003Cp>Debug Log Viewer simplifies WordPress debugging by providing a\u003Cbr \u002F>\nuser-friendly interface to view, search, and manage your debug.log\u003Cbr \u002F>\ndirectly within your WordPress admin area.\u003C\u002Fp>\n\u003Cp>It is designed for WordPress developers, site administrators,\u003Cbr \u002F>\nfreelancers, and anyone who needs to quickly identify and resolve\u003Cbr \u002F>\nwebsite issues.\u003C\u002Fp>\n\u003Cp>Debug Log Viewer helps you find errors faster without using FTP, hosting\u003Cbr \u002F>\npanels, or manually opening log files.\u003C\u002Fp>\n\u003Ch4>Gain Real-Time Insights into Your WordPress Site Health\u003C\u002Fh4>\n\u003Cp>Monitor errors, warnings, and deprecated function notices in real-time.\u003Cbr \u002F>\nDebug Log Viewer helps you identify problems early and maintain a more\u003Cbr \u002F>\nstable WordPress environment.\u003C\u002Fp>\n\u003Ch4>Key Features for Efficient WordPress Debugging\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Real-Time Log Viewer: Monitor your WordPress debug.log file in\u003Cbr \u002F>\nreal-time, directly from your WordPress dashboard. No more hunting\u003Cbr \u002F>\nfor files via FTP or cPanel!\u003C\u002Fli>\n\u003Cli>Easy Debug Log Access: Access and view your full debug log within a\u003Cbr \u002F>\nclean and intuitive interface.\u003C\u002Fli>\n\u003Cli>Search and Filtering: Quickly find specific log entries with\u003Cbr \u002F>\npowerful search and filtering options. Filter by error type,\u003Cbr \u002F>\nkeywords, and date range (Pro).\u003C\u002Fli>\n\u003Cli>Pagination: Navigate through large debug logs with ease using\u003Cbr \u002F>\npagination, ensuring smooth performance even with extensive logs.\u003C\u002Fli>\n\u003Cli>Email Alerts for Errors: Get email alerts when new errors are\u003Cbr \u002F>\nlogged. Pro users can customize error severity levels and\u003Cbr \u002F>\nrecipients.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Flexible Settings Panel\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Control WP_DEBUG Constants: Enable or disable WP_DEBUG and\u003Cbr \u002F>\nWP_DEBUG_LOG constants directly from the plugin settings.\u003C\u002Fli>\n\u003Cli>Customize Logging Options: Configure your debug log settings to\u003Cbr \u002F>\nmatch your needs.\u003C\u002Fli>\n\u003Cli>Custom Log Path Support: Automatically detect and read custom\u003Cbr \u002F>\ndebug.log locations.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Benefits of Using Debug Log Viewer\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Save Time and Effort: Stop manually accessing and parsing your debug\u003Cbr \u002F>\nlog file.\u003C\u002Fli>\n\u003Cli>Faster Error Detection: Monitor errors as they happen and reduce\u003Cbr \u002F>\ntroubleshooting time.\u003C\u002Fli>\n\u003Cli>Simplified Troubleshooting: Quickly identify the source of errors\u003Cbr \u002F>\nand warnings.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Debug Log Viewer Pro Features\u003C\u002Fh4>\n\u003Cp>Upgrade to Pro and get advanced tools for professional WordPress\u003Cbr \u002F>\ndebugging and site maintenance:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Advanced Email Alerts: Choose error levels and send notifications to\u003Cbr \u002F>\nmultiple recipients.\u003C\u002Fli>\n\u003Cli>CSV Export: Export debug log entries for analysis, reporting, or\u003Cbr \u002F>\nsharing.\u003C\u002Fli>\n\u003Cli>Custom Date Range Filtering: Analyze logs from specific time\u003Cbr \u002F>\nperiods.\u003C\u002Fli>\n\u003Cli>Infinite Scroll Log Viewer: Browse large log files smoothly without\u003Cbr \u002F>\npagination interruptions.\u003C\u002Fli>\n\u003Cli>Advanced Log Cleanup Controls: Manage debug.log size with custom\u003Cbr \u002F>\nlimits, schedules, cleanup methods, and retention settings.\u003C\u002Fli>\n\u003Cli>Cleanup History: Review previous cleanup actions and track log\u003Cbr \u002F>\nmaintenance.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Why choose Debug Log Viewer Pro?\u003C\u002Fh4>\n\u003Cp>Managing WordPress errors is not only about viewing logs.\u003C\u002Fp>\n\u003Cp>Large debug files can consume disk space, become difficult to analyze,\u003Cbr \u002F>\nand slow down troubleshooting.\u003C\u002Fp>\n\u003Cp>Pro gives you automation tools to monitor, export, filter, and maintain\u003Cbr \u002F>\nyour debug logs efficiently.\u003C\u002Fp>\n\u003Ch4>Who is Debug Log Viewer For?\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>WordPress developers\u003C\u002Fli>\n\u003Cli>Website administrators\u003C\u002Fli>\n\u003Cli>Freelancers managing client sites\u003C\u002Fli>\n\u003Cli>Agencies maintaining WordPress websites\u003C\u002Fli>\n\u003Cli>Anyone who wants an easy way to monitor WordPress errors\u003C\u002Fli>\n\u003C\u002Ful>\n","Effortlessly view, search, filter and manage your WordPress debug.log in the admin dashboard. Real-time monitoring and email alerts",1000,16436,80,3,"2026-06-25T05:59:00.000Z","7.0.2","5.8","7.2",[19,53,54,20,55],"debug-log","debugging","error-log","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-log-viewer.2.4.zip",99,1,"2025-10-29 00:00:00",{"slug":62,"name":63,"version":64,"author":65,"author_profile":66,"description":67,"short_description":68,"active_installs":69,"downloaded":70,"rating":11,"num_ratings":11,"last_updated":71,"tested_up_to":49,"requires_at_least":72,"requires_php":73,"tags":74,"homepage":56,"download_link":78,"security_score":24,"vuln_count":11,"unpatched_count":11,"last_vuln_date":25,"fetched_at":26},"postmeta-viewer","PostMeta Viewer – Custom Fields Inspector","1.1","wpwebguru","https:\u002F\u002Fprofiles.wordpress.org\u002Fwpwebguru\u002F","\u003Cp>\u003Cstrong>PostMeta Viewer\u003C\u002Fstrong> is an essential utility for WordPress developers who work with custom fields and post meta. Whether you’re using Advanced Custom Fields (ACF), Pods, Toolset, or custom-coded meta fields, this plugin provides a clean and developer-friendly interface to explore, search, and analyze meta data across your entire WordPress site.\u003C\u002Fp>\n\u003Cp>It is designed strictly as a \u003Cstrong>read-only inspection tool\u003C\u002Fstrong>, making it safe for production environments.\u003C\u002Fp>\n\u003Ch4>Key Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Complete Meta Overview\u003C\u002Fstrong>\u003Cbr \u002F>\nBrowse all posts, pages, and custom post types with total custom field counts.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Detailed Meta Inspection\u003C\u002Fstrong>\u003Cbr \u002F>\nView all meta keys and values for any individual post, taxonomy term, user, or comment.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Powerful Search & Filtering\u003C\u002Fstrong>\u003Cbr \u002F>\n– Search across post titles, content, meta keys, and meta values\u003Cbr \u002F>\n– Filter by post type, post status, and date range\u003Cbr \u002F>\n– Filter by specific meta key existence\u003Cbr \u002F>\n– Filter by meta value type (string, array, JSON, numeric, empty)\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Meta Inspector Everywhere\u003C\u002Fstrong>\u003Cbr \u002F>\n– Post edit screen meta box (configurable per post type)\u003Cbr \u002F>\n– Taxonomy term edit screens (categories, tags, custom taxonomies)\u003Cbr \u002F>\n– User profile edit screens\u003Cbr \u002F>\n– Comment edit screen\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Developer-Friendly Data Display\u003C\u002Fstrong>\u003Cbr \u002F>\n– Proper formatting for serialized, array, and JSON meta values\u003Cbr \u002F>\n– One‑click “beautify” toggle to expand complex data structures\u003Cbr \u002F>\n– Dark‑style pre‑formatted output for readability\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Post Statistics\u003C\u002Fstrong>\u003Cbr \u002F>\nQuick insights into total posts and filtered results.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Extensive Settings Page\u003C\u002Fstrong>\u003Cbr \u002F>\n– Choose which roles can access the inspector\u003Cbr \u002F>\n– Toggle visibility on post types, taxonomies, users, and comments\u003Cbr \u002F>\n– Hide internal meta keys (those starting with an underscore)\u003Cbr \u002F>\n– Adjust items per page\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Responsive Admin UI\u003C\u002Fstrong>\u003Cbr \u002F>\nWorks smoothly across all screen sizes.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Ideal For\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>ACF Developers\u003C\u002Fstrong> – Debug and verify stored ACF field data  \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Plugin Developers\u003C\u002Fstrong> – Inspect custom meta added by plugins  \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Theme Developers\u003C\u002Fstrong> – Validate custom field implementations  \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Site Debugging\u003C\u002Fstrong> – Identify and resolve metadata issues  \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Migration Projects\u003C\u002Fstrong> – Analyze existing meta structures  \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Learning WordPress\u003C\u002Fstrong> – Understand how post meta works internally\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Ch4>Getting Started\u003C\u002Fh4>\n\u003Col>\n\u003Cli>After activation, go to \u003Cstrong>PostMeta Viewer\u003C\u002Fstrong> (top-level menu)\u003C\u002Fli>\n\u003Cli>View a list of all posts along with their custom field counts\u003C\u002Fli>\n\u003Cli>Use search and filter options to narrow results\u003C\u002Fli>\n\u003Cli>Click \u003Cstrong>View Details\u003C\u002Fstrong> to inspect meta for a specific post\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Using Search & Filters\u003C\u002Fh4>\n\u003Col>\n\u003Cli>\u003Cstrong>Search Box\u003C\u002Fstrong> – Search across post titles, content, meta keys, and values  \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Post Type Filter\u003C\u002Fstrong> – Filter posts, pages, or custom post types  \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Meta Key Filter\u003C\u002Fstrong> – Filter by existing meta keys  \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Date Range\u003C\u002Fstrong> – Filter posts by creation date  \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Post Status\u003C\u002Fstrong> – Published, draft, pending, etc.  \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Value Type Filter\u003C\u002Fstrong> – String, array, JSON, numeric, or empty  \u003C\u002Fli>\n\u003Cli>Click \u003Cstrong>Apply Filters\u003C\u002Fstrong> to update results\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Viewing Meta Details\u003C\u002Fh4>\n\u003Col>\n\u003Cli>Click \u003Cstrong>View Details\u003C\u002Fstrong> from the main list\u003C\u002Fli>\n\u003Cli>View a table of all meta keys and values\u003C\u002Fli>\n\u003Cli>Serialized and complex data is displayed in a readable, beautified format\u003C\u002Fli>\n\u003Cli>Use \u003Cstrong>Back to List\u003C\u002Fstrong> to return\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Inspecting Meta on Other Screens\u003C\u002Fh4>\n\u003Col>\n\u003Cli>\u003Cstrong>Post Edit Screen\u003C\u002Fstrong> – The \u003Cstrong>Custom Fields Inspector\u003C\u002Fstrong> meta box appears below the content editor (for enabled post types)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Taxonomy Term Edit Screen\u003C\u002Fstrong> – A similar box appears on category, tag, and custom taxonomy edit pages\u003C\u002Fli>\n\u003Cli>\u003Cstrong>User Profile Edit Screen\u003C\u002Fstrong> – The inspector is shown on user profile pages\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Comment Edit Screen\u003C\u002Fstrong> – The inspector is shown on the single comment edit page\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>All boxes respect the role and visibility settings.\u003C\u002Fp>\n\u003Ch4>Configuring the Plugin\u003C\u002Fh4>\n\u003Col>\n\u003Cli>Go to \u003Cstrong>PostMeta Viewer \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Settings\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Adjust:\n\u003Cul>\n\u003Cli>\u003Cstrong>Items Per Page\u003C\u002Fstrong> – number of posts shown in the main list\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Access Roles\u003C\u002Fstrong> – checkboxes for every registered user role; only checked roles can view post, term, user, and comment meta data (Administrator is always enabled and cannot be unchecked, to prevent accidental lockout)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Hide Internal Keys\u003C\u002Fstrong> – toggle visibility of meta keys starting with \u003Ccode>_\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Enabled Post Types\u003C\u002Fstrong> – checkboxes for every public post type, controlling which post-type edit screens show the Custom Fields Inspector meta box\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Inspector Locations\u003C\u002Fstrong> – enable\u002Fdisable meta boxes on taxonomies, users, and comments\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Save your changes\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>License\u003C\u002Fh3>\n\u003Cp>This plugin is licensed under the GPL v2 or later.\u003C\u002Fp>\n\u003Cp>This program is free software; you can redistribute it and\u002For modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or any later version.\u003C\u002Fp>\n\u003Cp>This program is distributed without any warranty; without even the implied warranty of merchantability or fitness for a particular purpose.\u003C\u002Fp>\n","A powerful debugging tool for WordPress developers to inspect and analyze post meta (custom fields) across posts, pages, custom post types, taxonomy t …",70,1186,"2026-06-21T07:45:00.000Z","5.6","7.4",[75,76,54,20,77],"acf","custom-fields","post-meta","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpostmeta-viewer.1.1.zip",{"slug":80,"name":81,"version":82,"author":83,"author_profile":84,"description":85,"short_description":86,"active_installs":32,"downloaded":87,"rating":24,"num_ratings":59,"last_updated":88,"tested_up_to":14,"requires_at_least":89,"requires_php":90,"tags":91,"homepage":56,"download_link":94,"security_score":24,"vuln_count":11,"unpatched_count":11,"last_vuln_date":25,"fetched_at":26},"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.",381,"2026-02-06T13:02:00.000Z","5.0","7.0",[19,20,55,92,93],"troubleshooting","wp-config","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdeveloper-debug-mode.1.2.5.zip",{"slug":96,"name":97,"version":98,"author":99,"author_profile":100,"description":101,"short_description":102,"active_installs":103,"downloaded":104,"rating":24,"num_ratings":59,"last_updated":105,"tested_up_to":14,"requires_at_least":106,"requires_php":73,"tags":107,"homepage":56,"download_link":111,"security_score":24,"vuln_count":11,"unpatched_count":11,"last_vuln_date":25,"fetched_at":26},"mcp-tracker","MCP Tracker","1.0.1","WPVibes","https:\u002F\u002Fprofiles.wordpress.org\u002Fwpvibes\u002F","\u003Cp>MCP Tracker is an admin-only WordPress plugin designed to monitor and log MCP (Model Context Protocol) requests made to the Abilities API on your WordPress site.\u003Cbr \u002F>\nIf you are using the Abilities API to power AI-driven tools or MCP-based integrations, MCP Tracker gives you complete visibility into how those tools interact with your REST endpoints — without modifying or interfering with request flow.\u003Cbr \u002F>\nThe plugin automatically detects MCP requests (identified via the \u003Ccode>Mcp-Session-Id\u003C\u002Fcode> header), records detailed request and response data, and presents everything in a structured, filterable interface inside WordPress Admin.\u003Cbr \u002F>\nWhether you’re debugging Abilities API integrations, auditing MCP tool usage, or analyzing response behavior, MCP Tracker provides the observability layer you need.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Automatic MCP Detection\u003C\u002Fstrong>\u003Cbr \u002F>\nIdentifies MCP requests related to Abilities API using the \u003Ccode>Mcp-Session-Id\u003C\u002Fcode> header.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Comprehensive Logging\u003C\u002Fstrong>\u003Cbr \u002F>\nLogs route, method, headers, request payload, response status, and response body.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>User Attribution\u003C\u002Fstrong>\u003Cbr \u002F>\nDisplays which WordPress user (or guest) initiated the MCP request.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Advanced Filtering\u003C\u002Fstrong>\u003Cbr \u002F>\nFilter logs by date range, tool name, and user for targeted analysis.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Formatted JSON Inspection\u003C\u002Fstrong>\u003Cbr \u002F>\nView complete request and response data in a structured format.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Privacy Focused\u003C\u002Fstrong>\u003Cbr \u002F>\nAll logs remain stored in your WordPress database. No external transmission or telemetry.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Performance Optimized\u003C\u002Fstrong>\u003Cbr \u002F>\nEfficient logging using native WordPress REST hooks and optimized queries.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Use Cases\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Debug Abilities API integrations  \u003C\u002Fli>\n\u003Cli>Monitor MCP-based AI tool usage  \u003C\u002Fli>\n\u003Cli>Analyze REST response patterns  \u003C\u002Fli>\n\u003Cli>Audit MCP activity on production sites  \u003C\u002Fli>\n\u003Cli>Investigate failed or unexpected tool executions  \u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Technical Details\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Uses WordPress REST API hooks for non-intrusive logging  \u003C\u002Fli>\n\u003Cli>Custom indexed database table for efficient storage  \u003C\u002Fli>\n\u003Cli>Admin-only access with capability checks  \u003C\u002Fli>\n\u003Cli>Nonce verification for secure actions  \u003C\u002Fli>\n\u003Cli>Prepared SQL statements for database safety  \u003C\u002Fli>\n\u003Cli>Self-healing table creation on activation\u003C\u002Fli>\n\u003C\u002Ful>\n","Records and displays MCP-related REST API requests made to your WordPress site.",20,561,"2026-04-27T11:05:00.000Z","6.9",[54,20,108,109,110],"logging","mcp","rest-api","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmcp-tracker.1.0.1.zip",{"slug":113,"name":114,"version":115,"author":116,"author_profile":117,"description":118,"short_description":119,"active_installs":120,"downloaded":121,"rating":11,"num_ratings":11,"last_updated":122,"tested_up_to":123,"requires_at_least":50,"requires_php":73,"tags":124,"homepage":126,"download_link":127,"security_score":24,"vuln_count":11,"unpatched_count":11,"last_vuln_date":25,"fetched_at":26},"log-iq","LogIQ – Intelligent Debug Log Viewer","1.2.0","akmelias","https:\u002F\u002Fprofiles.wordpress.org\u002Fakmelias\u002F","\u003Cp>\u003Cstrong>Debugging WordPress shouldn’t be painful.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Most developers deal with debug logs the hard way: SSH into the server, \u003Ccode>tail -f debug.log\u003C\u002Fcode>, squint at wall-of-text output, scroll endlessly to find the one error that matters. It’s slow, it’s fragile, and it pulls you out of your flow.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>LogIQ fixes that.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>LogIQ is an intelligent debug log viewer built for WordPress developers. It lives in your admin dashboard, parses your log file automatically, and surfaces exactly what you need — with search, filters, collapsible stack traces, and one-click editor access. No config files. No terminal. No wasted time.\u003C\u002Fp>\n\u003Ch4>What Makes LogIQ Different\u003C\u002Fh4>\n\u003Cp>Most log plugins just dump raw text into a \u003Ccode>\u003Ctextarea>\u003C\u002Fcode>. LogIQ actually understands your logs.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Categorizes every entry by level (Fatal, Error, Warning, Notice, Deprecated, Info, Debug, DB Error)\u003C\u002Fli>\n\u003Cli>Detects duplicate\u002Frepeated errors and groups them with a count badge\u003C\u002Fli>\n\u003Cli>Collapses multi-line stack traces so your screen isn’t buried in noise\u003C\u002Fli>\n\u003Cli>Highlights your search term inline across all matching entries\u003C\u002Fli>\n\u003Cli>Shows relative timestamps (“3 minutes ago”) with the full timestamp on hover\u003C\u002Fli>\n\u003Cli>Lets you copy any entry to clipboard in one click\u003C\u002Fli>\n\u003Cli>Opens the exact file and line in VS Code, PhpStorm, or Sublime Text — no copy-pasting paths\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Core Features\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>Smart Log Parsing\u003C\u002Fstrong>\u003Cbr \u002F>\nAutomatically detects PHP Fatal errors, Warnings, Notices, Deprecated calls, Database errors, and custom \u003Ccode>error_log()\u003C\u002Fcode> output. No setup required.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Full-Text Search\u003C\u002Fstrong>\u003Cbr \u002F>\nSearch across message content, file paths, and timestamps instantly. Matches are highlighted in-place with a count of results.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Level Filters\u003C\u002Fstrong>\u003Cbr \u002F>\nFilter by Fatal, Error, Warning, Notice, Deprecated, Info, Debug, or DB Error with a single click. Counts update live with each filter.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Collapsible Stack Traces\u003C\u002Fstrong>\u003Cbr \u002F>\nLong stack traces are collapsed by default. Expand only the ones you care about — keeping your view clean and focused.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Duplicate Detection\u003C\u002Fstrong>\u003Cbr \u002F>\nConsecutive identical log entries are automatically grouped into a single entry with a \u003Ccode>×N\u003C\u002Fcode> badge. Stop scrolling past 200 copies of the same warning.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Relative Timestamps\u003C\u002Fstrong>\u003Cbr \u002F>\nLog timestamps show as “2 minutes ago”, “1 hour ago” etc. Hover to see the full timestamp. Great for spotting when errors started.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Copy to Clipboard\u003C\u002Fstrong>\u003Cbr \u002F>\nOne-click copy on every log entry. Paste directly into Slack, a bug report, or a support ticket.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Log Export\u003C\u002Fstrong>\u003Cbr \u002F>\nDownload your current filtered view as a \u003Ccode>.log\u003C\u002Fcode> file or structured \u003Ccode>.json\u003C\u002Fcode> — perfect for sharing with your team or attaching to issue trackers.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Editor Integration\u003C\u002Fstrong>\u003Cbr \u002F>\nClick any file path in a log entry to jump directly to that file and line in:\u003Cbr \u002F>\n* Visual Studio Code\u003Cbr \u002F>\n* PhpStorm\u003Cbr \u002F>\n* Sublime Text\u003Cbr \u002F>\n* Falls back to \u003Ccode>file:\u002F\u002F\u003C\u002Fcode> if no supported editor is detected\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Auto-Refresh\u003C\u002Fstrong>\u003Cbr \u002F>\nThe log viewer refreshes automatically every 30 seconds so you can watch logs update in real time without touching the page.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Secure by Default\u003C\u002Fstrong>\u003Cbr \u002F>\nOnly users with \u003Ccode>manage_options\u003C\u002Fcode> capability can access LogIQ. All AJAX requests are nonce-verified. Sensitive values (passwords, API keys, auth tokens) are masked automatically before display.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Pagination\u003C\u002Fstrong>\u003Cbr \u002F>\nHandles large log files gracefully — reads up to 5 MB from the end of the file, paginates entries, and never loads more than needed.\u003C\u002Fp>\n\u003Ch4>Perfect For\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>WordPress plugin and theme developers\u003C\u002Fli>\n\u003Cli>Agencies managing multiple client sites\u003C\u002Fli>\n\u003Cli>Developers debugging WooCommerce, REST APIs, and third-party integrations\u003C\u002Fli>\n\u003Cli>Anyone who’s tired of \u003Ccode>tail -f debug.log\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>How to Use error_log() with LogIQ\u003C\u002Fh4>\n\u003Cp>LogIQ reads from WordPress’s standard debug log. Write to it from anywhere in your code:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>error_log( 'Something happened' );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>For arrays and objects:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>error_log( print_r( $my_array, true ) );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>For exceptions:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>error_log( $exception->getMessage() . ' in ' . $exception->getFile() . ':' . $exception->getLine() );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3>Privacy Policy\u003C\u002Fh3>\n\u003Cp>LogIQ does not collect, transmit, or store any personal data outside of your own server. All log data remains local. The plugin does not make any external HTTP requests.\u003C\u002Fp>\n\u003Ch3>Credits\u003C\u002Fh3>\n\u003Cp>Developed by \u003Ca href=\"https:\u002F\u002Fakmelias.com\" rel=\"nofollow ugc\">AKM Elias\u003C\u002Fa>. If LogIQ saves you time, consider leaving a review on WordPress.org — it helps more developers find it.\u003C\u002Fp>\n","Stop digging through raw log files. LogIQ gives WordPress developers a smart, searchable, and beautiful debug log viewer — right inside the admin.",10,830,"2026-03-20T05:54:00.000Z","6.8.6",[53,54,20,55,125],"log-viewer","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Flog-iq\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flog-iq.1.2.0.zip",{"attackSurface":129,"codeSignals":289,"taintFlows":333,"riskAssessment":408,"analyzedAt":418},{"hooks":130,"ajaxHandlers":281,"restRoutes":282,"shortcodes":283,"cronEvents":287,"entryPointCount":59,"unprotectedCount":11},[131,137,141,145,149,153,157,161,165,169,173,177,181,185,189,193,197,201,206,209,213,216,218,222,226,230,234,237,241,244,246,250,252,255,257,261,264,266,270,274,277],{"type":132,"name":133,"callback":134,"priority":120,"file":135,"line":136},"action","user_id_activity","log_activity","includes\\class-activity-logger.php",19,{"type":132,"name":138,"callback":139,"priority":120,"file":135,"line":140},"wp_login","log_login",22,{"type":132,"name":142,"callback":143,"file":135,"line":144},"wp_logout","log_logout",23,{"type":132,"name":146,"callback":147,"priority":120,"file":135,"line":148},"profile_update","log_profile_update",24,{"type":132,"name":150,"callback":151,"priority":120,"file":135,"line":152},"set_user_role","log_set_user_role",25,{"type":132,"name":154,"callback":155,"file":135,"line":156},"after_password_reset","log_password_reset",26,{"type":132,"name":158,"callback":159,"file":135,"line":160},"user_id_daily_cleanup","cleanup_old_logs",29,{"type":132,"name":162,"callback":163,"priority":120,"file":135,"line":164},"transition_post_status","log_post_transition",35,{"type":132,"name":166,"callback":167,"priority":120,"file":135,"line":168},"deleted_post","log_post_deleted",36,{"type":132,"name":170,"callback":171,"file":135,"line":172},"add_attachment","log_attachment_added",37,{"type":132,"name":174,"callback":175,"file":135,"line":176},"delete_attachment","log_attachment_deleted",38,{"type":132,"name":178,"callback":179,"priority":120,"file":135,"line":180},"activated_plugin","log_plugin_activated",41,{"type":132,"name":182,"callback":183,"priority":120,"file":135,"line":184},"deactivated_plugin","log_plugin_deactivated",42,{"type":132,"name":186,"callback":187,"priority":120,"file":135,"line":188},"switch_theme","log_theme_switched",43,{"type":132,"name":190,"callback":191,"priority":120,"file":135,"line":192},"upgrader_process_complete","log_upgrader_process",44,{"type":132,"name":194,"callback":195,"priority":120,"file":135,"line":196},"updated_option","log_option_updated",47,{"type":132,"name":198,"callback":199,"priority":103,"file":135,"line":200},"user_id_debug_user_panes","render_activity_log_pane",50,{"type":202,"name":203,"callback":204,"file":205,"line":136},"filter","manage_users_columns","add_user_id_column","includes\\class-admin.php",{"type":202,"name":207,"callback":208,"priority":120,"file":205,"line":103},"manage_users_custom_column","show_user_id_column_content",{"type":202,"name":210,"callback":211,"file":205,"line":212},"manage_users_sortable_columns","make_user_id_column_sortable",21,{"type":132,"name":214,"callback":215,"file":205,"line":148},"show_user_profile","display_user_id_on_profile",{"type":132,"name":217,"callback":215,"file":205,"line":152},"edit_user_profile",{"type":132,"name":219,"callback":220,"file":205,"line":221},"admin_enqueue_scripts","enqueue_assets",28,{"type":132,"name":223,"callback":224,"file":205,"line":225},"admin_menu","add_settings_page",31,{"type":132,"name":227,"callback":228,"file":205,"line":229},"admin_init","register_settings",32,{"type":132,"name":231,"callback":232,"priority":233,"file":205,"line":164},"admin_bar_menu","add_support_mode_admin_bar",999,{"type":132,"name":235,"callback":236,"file":205,"line":176},"pre_get_users","handle_user_id_column_sorting",{"type":202,"name":238,"callback":239,"priority":120,"file":240,"line":144},"user_row_actions","add_impersonate_row_action","includes\\class-impersonation.php",{"type":132,"name":242,"callback":243,"file":240,"line":148},"user_id_debug_user_actions","add_impersonate_button_inspector",{"type":132,"name":227,"callback":245,"file":240,"line":156},"handle_impersonation_request",{"type":132,"name":247,"callback":248,"file":240,"line":249},"init","handle_return_request",27,{"type":132,"name":231,"callback":251,"priority":233,"file":240,"line":160},"add_impersonation_notice_admin_bar",{"type":132,"name":253,"callback":254,"file":240,"line":32},"wp_footer","impersonation_warning_banner",{"type":132,"name":256,"callback":254,"file":240,"line":225},"admin_notices",{"type":132,"name":138,"callback":258,"priority":120,"file":259,"line":260},"record_login","includes\\class-login-tracker.php",18,{"type":132,"name":198,"callback":262,"priority":263,"file":259,"line":103},"render_login_history_pane",15,{"type":132,"name":158,"callback":265,"file":259,"line":144},"cleanup_old_logins",{"type":132,"name":227,"callback":267,"file":268,"line":269},"check_db_version","includes\\class-plugin.php",61,{"type":132,"name":271,"callback":272,"file":273,"line":212},"rest_api_init","register_routes","includes\\class-rest-api.php",{"type":132,"name":223,"callback":275,"file":276,"line":260},"register_debug_page","includes\\class-user-debug.php",{"type":132,"name":278,"callback":279,"file":280,"line":164},"plugins_loaded","user_id_init","user-id.php",[],[],[284],{"tag":4,"callback":285,"file":280,"line":286},"user_id_legacy_shortcode",53,[288],{"hook":158,"callback":158,"file":135,"line":225},{"dangerousFunctions":290,"sqlUsage":291,"outputEscaping":298,"fileOperations":11,"externalRequests":11,"nonceChecks":31,"capabilityChecks":331,"bundledLibraries":332},[],{"prepared":103,"raw":31,"locations":292},[293,296],{"file":135,"line":294,"context":295},138,"$wpdb->query() with variable interpolation",{"file":259,"line":297,"context":295},68,{"escaped":299,"rawEcho":300,"locations":301},63,14,[302,305,307,309,311,313,315,317,319,321,323,325,327,329],{"file":240,"line":303,"context":304},98,"raw output",{"file":276,"line":306,"context":304},60,{"file":276,"line":308,"context":304},72,{"file":276,"line":310,"context":304},75,{"file":276,"line":312,"context":304},170,{"file":276,"line":314,"context":304},174,{"file":276,"line":316,"context":304},177,{"file":276,"line":318,"context":304},178,{"file":276,"line":320,"context":304},179,{"file":276,"line":322,"context":304},180,{"file":276,"line":324,"context":304},181,{"file":276,"line":326,"context":304},192,{"file":276,"line":328,"context":304},293,{"file":276,"line":330,"context":304},298,5,[],[334,381],{"entryPoint":335,"graph":336,"unsanitizedCount":31,"severity":380},"render_page (includes\\class-user-debug.php:37)",{"nodes":337,"edges":371},[338,342,346,352,355,358,363,365,368],{"id":339,"type":340,"label":341,"file":276,"line":200},"n0","source","$_GET",{"id":343,"type":344,"label":345,"file":276,"line":200},"n1","transform","→ perform_deep_search()",{"id":347,"type":348,"label":349,"file":276,"line":350,"wp_function":351},"n2","sink","get_col() [SQLi]",124,"get_col",{"id":353,"type":340,"label":341,"file":276,"line":354},"n3",62,{"id":356,"type":344,"label":357,"file":276,"line":354},"n4","→ render_search_form()",{"id":359,"type":348,"label":360,"file":276,"line":361,"wp_function":362},"n5","echo() [XSS]",149,"echo",{"id":364,"type":340,"label":341,"file":276,"line":69},"n6",{"id":366,"type":344,"label":367,"file":276,"line":69},"n7","→ render_user_inspector()",{"id":369,"type":348,"label":360,"file":276,"line":370,"wp_function":362},"n8",239,[372,374,376,377,378,379],{"from":339,"to":343,"sanitized":373},false,{"from":343,"to":347,"sanitized":375},true,{"from":353,"to":356,"sanitized":373},{"from":356,"to":359,"sanitized":373},{"from":364,"to":366,"sanitized":373},{"from":366,"to":369,"sanitized":373},"medium",{"entryPoint":382,"graph":383,"unsanitizedCount":31,"severity":380},"\u003Cclass-user-debug> (includes\\class-user-debug.php:0)",{"nodes":384,"edges":400},[385,387,389,390,391,392,393,394,395,396,398],{"id":339,"type":340,"label":386,"file":276,"line":188},"$_GET (x6)",{"id":343,"type":348,"label":360,"file":276,"line":388,"wp_function":362},215,{"id":347,"type":340,"label":341,"file":276,"line":200},{"id":353,"type":344,"label":345,"file":276,"line":200},{"id":356,"type":348,"label":349,"file":276,"line":350,"wp_function":351},{"id":359,"type":340,"label":341,"file":276,"line":354},{"id":364,"type":344,"label":357,"file":276,"line":354},{"id":366,"type":348,"label":360,"file":276,"line":361,"wp_function":362},{"id":369,"type":340,"label":341,"file":276,"line":69},{"id":397,"type":344,"label":367,"file":276,"line":69},"n9",{"id":399,"type":348,"label":360,"file":276,"line":370,"wp_function":362},"n10",[401,402,403,404,405,406,407],{"from":339,"to":343,"sanitized":375},{"from":347,"to":353,"sanitized":373},{"from":353,"to":356,"sanitized":375},{"from":359,"to":364,"sanitized":373},{"from":364,"to":366,"sanitized":373},{"from":369,"to":397,"sanitized":373},{"from":397,"to":399,"sanitized":373},{"summary":409,"deductions":410},"The \"user-id\" plugin v2.0.0 exhibits a generally strong security posture based on the provided static analysis and vulnerability history.  The code demonstrates good practices by utilizing prepared statements for a high percentage of SQL queries and properly escaping a majority of its outputs.  The absence of file operations, external HTTP requests, and dangerous functions further contributes to a lower-risk profile.  The plugin also incorporates nonce and capability checks, indicating an awareness of common WordPress security vulnerabilities.  The lack of any recorded CVEs, past or present, is a significant positive indicator of its security history and ongoing maintenance.",[411,413,416],{"reason":412,"points":263},"Flows with unsanitized paths",{"reason":414,"points":415},"Partially unescaped outputs",4,{"reason":417,"points":31},"SQL queries not using prepared statements","2026-03-17T07:14:49.499Z",{"wat":420,"direct":429},{"assetPaths":421,"generatorPatterns":424,"scriptPaths":425,"versionParams":426},[422,423],"\u002Fwp-content\u002Fplugins\u002Fuser-id\u002Fassets\u002Fadmin.css","\u002Fwp-content\u002Fplugins\u002Fuser-id\u002Fassets\u002Fadmin.js",[],[],[427,428],"user-id\u002Fassets\u002Fadmin.css?ver=","user-id\u002Fassets\u002Fadmin.js?ver=",{"cssClasses":430,"htmlComments":434,"htmlAttributes":435,"restEndpoints":437,"jsGlobals":438,"shortcodeOutput":440},[431,432,433],"user-id-value","user-id-copy-btn","user-id-settings",[],[436],"data-clipboard-text",[],[439],"userIdOpts",[441],"\u003Cp id='UID'>",{"error":375,"url":443,"statusCode":444,"statusMessage":445,"message":445},"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Fuser-id\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":59,"versions":447},[448],{"version":6,"download_url":23,"svn_tag_url":449,"released_at":25,"has_diff":373,"diff_files_changed":450,"diff_lines":25,"trac_diff_url":25,"vulnerabilities":451,"is_current":375},"https:\u002F\u002Fplugins.svn.wordpress.org\u002Fuser-id\u002Ftags\u002F2.0.0\u002F",[],[]]