[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fHSwvf5CK6w0M6-GhdGefl1J2m_89HzaCxX5D1P67Ph4":3},{"slug":4,"display_name":5,"profile_url":6,"plugin_count":7,"total_installs":8,"avg_security_score":9,"avg_patch_time_days":10,"trust_score":11,"computed_at":12,"plugins":13},"lumiblog","Patrick Lumumba","https:\u002F\u002Fprofiles.wordpress.org\u002Flumiblog\u002F",3,2080,99,17,93,"2026-04-04T13:08:47.083Z",[14,40,60],{"slug":15,"name":16,"version":17,"author":5,"author_profile":6,"description":18,"short_description":19,"active_installs":20,"downloaded":21,"rating":22,"num_ratings":23,"last_updated":24,"tested_up_to":25,"requires_at_least":26,"requires_php":27,"tags":28,"homepage":33,"download_link":34,"security_score":35,"vuln_count":36,"unpatched_count":37,"last_vuln_date":38,"fetched_at":39},"footnotes-made-easy","Footnotes Made Easy","3.1.0","\u003Cp>Footnotes Made Easy is a simple, but powerful, method of adding footnotes to your posts and pages.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Key features include…\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Simple footnote insertion via double parentheses\u003C\u002Fli>\n\u003Cli>Combine identical notes\u003C\u002Fli>\n\u003Cli>Solution for paginated posts\u003C\u002Fli>\n\u003Cli>Suppress Footnotes on specific page types\u003C\u002Fli>\n\u003Cli>Option to display ‘pretty’ tooltips using jQuery\u003C\u002Fli>\n\u003Cli>Lots of configuration options\u003C\u002Fli>\n\u003Cli>And much, much more!\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Footnotes Made Easy is a fork of \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdrzax\u002Fwp-footnotes\" title=\"Github - wp-footnotes\" rel=\"nofollow ugc\">WP Footnotes\u003C\u002Fa>, a plugin by Simon Elvery which was abandoned some years ago\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Please visit the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Flumumbapl\u002Ffootnotes-made-easy\u002F\" title=\"Github\" rel=\"nofollow ugc\">Github page\u003C\u002Fa> for the latest code development, planned enhancements and known issues\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Ch3>Getting Started\u003C\u002Fh3>\n\u003Cspan class=\"embed-youtube\" style=\"text-align:center; display: block;\">\u003Ciframe loading=\"lazy\" class=\"youtube-player\" width=\"750\" height=\"422\" src=\"https:\u002F\u002Fwww.youtube.com\u002Fembed\u002FLuXMb8Hz4tc?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent\" allowfullscreen=\"true\" style=\"border:0;\" sandbox=\"allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox\">\u003C\u002Fiframe>\u003C\u002Fspan>\n\u003Cp>Creating a footnote is incredibly simple – you just need to include your footnote in double parentheses, such as this…\u003C\u002Fp>\n\u003Cp>This is a sentence ((and this is your footnote)).\u003C\u002Fp>\n\u003Cp>The footnote will then appear at the bottom of your post\u002Fpage.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Important note:\u003C\u002Fstrong> Make sure you include a space before your opening double parentheses or the footnote won’t work!\u003C\u002Fp>\n\u003Ch3>Options\u003C\u002Fh3>\n\u003Cp>You have a fair few options on how the identifier links, footnotes and back-links look which can be found in the WordPress admin area under ‘Settings -> Footnotes’.\u003C\u002Fp>\n\u003Ch3>Paginated Posts\u003C\u002Fh3>\n\u003Cp>Some of you seem to like the paginating post, which is kind of problematic. By default, each page of your post will have its own set of footnotes at the bottom and the numbering will start again from 1 for each page.\u003C\u002Fp>\n\u003Cp>The only way to get around this is to know how many posts are on each page and tell Footnotes Made Easy what number you want the list to start at for each of the pages. So at some point on each page (that is, between each \u003Ccode>\u003C!--nextpage-->\u003C\u002Fcode> tag) you need to add a tag to let the plugin know what number the footnotes on this page should start at. The tag should look like this \u003Ccode>\u003C!--startnum=5-->\u003C\u002Fcode> where “5” is the number you want the footnotes for this page to start at.\u003C\u002Fp>\n\u003Ch3>Referencing\u003C\u002Fh3>\n\u003Cp>Sometimes it’s useful to be able to refer to a previous footnote a second (or third, or fourth…) time. To do this, you can either simply insert the exact same text as you did the first time and the identifier should simply reference the previous note. Alternatively, if you don’t want to do all that typing again, you can construct a footnote like this: \u003Ccode>((ref:1))\u003C\u002Fcode> and the identifier will reference the footnote with the given number.\u003C\u002Fp>\n\u003Cp>Even though it’s a little more typing, using the exact text method is much more robust. The number referencing will not work across multiple pages in a paged post (but will work within the page). Also, if you use the number referencing system you risk them identifying the incorrect footnote if you go back and insert a new footnote and forget to change the referenced number.\u003C\u002Fp>\n\u003Ch3>Available in 8 Languages\u003C\u002Fh3>\n\u003Cp>Footnotes Made Easy is fully internationalized, and ready for translations.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Many thanks to the following translators for their contributions:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fdartiss\u002F\" rel=\"nofollow ugc\">David Artiss\u003C\u002Fa>, English (UK)\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fmarkscottrobson\u002F\" rel=\"nofollow ugc\">Mark Robson\u003C\u002Fa>, English (UK)\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fyayannabelle\u002F\" rel=\"nofollow ugc\">Annabelle W\u003C\u002Fa>, English (UK)\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fmaboroshin\u002F\" rel=\"nofollow ugc\">maboroshin\u003C\u002Fa>, Japanese\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fwplmillet\u002F\" rel=\"nofollow ugc\">Laurent MILLET\u003C\u002Fa>, French (France)\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fcansmile\u002F\" rel=\"nofollow ugc\">B. Cansmile Cha\u003C\u002Fa>, Korean \u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fdanbilabs\u002F\" rel=\"nofollow ugc\">danbilabs\u003C\u002Fa>, Korean\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fdanbilabs\u002F\" rel=\"nofollow ugc\">denelan\u003C\u002Fa>, Dutch \u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fpsmits1567\u002F\" rel=\"nofollow ugc\">Peter Smits\u003C\u002Fa>, Dutch\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fnekojonez\u002F\" rel=\"nofollow ugc\">Pieterjan Deneys\u003C\u002Fa>, Dutch (Belgium)\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Falexvgrey\u002F\" rel=\"nofollow ugc\">Alex Grey\u003C\u002Fa>, Russian\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>If you would like to add a translation to this plugin then please head to our \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Fprojects\u002Fwp-plugins\u002Ffootnotes-made-easy\" title=\"Translating WordPress\" rel=\"nofollow ugc\">Translating WordPress\u003C\u002Fa> page\u003C\u002Fstrong>\u003C\u002Fp>\n","Allows post authors to easily add and manage footnotes in posts.",2000,55299,92,38,"2025-11-29T18:04:00.000Z","6.9.4","4.6","7.4",[29,30,31,32],"bibliography","footnotes","formatting","reference","https:\u002F\u002Flumumbas.blog\u002Fplugins\u002Ffootnotes-made-easy\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffootnotes-made-easy.3.1.0.zip",97,1,0,"2025-11-03 16:03:22","2026-03-15T15:16:48.613Z",{"slug":41,"name":42,"version":43,"author":5,"author_profile":6,"description":44,"short_description":45,"active_installs":46,"downloaded":47,"rating":37,"num_ratings":37,"last_updated":48,"tested_up_to":25,"requires_at_least":49,"requires_php":27,"tags":50,"homepage":56,"download_link":57,"security_score":58,"vuln_count":37,"unpatched_count":37,"last_vuln_date":59,"fetched_at":39},"page-categorizer","Page Categorizer","1.4.0","\u003Cp>The \u003Cstrong>“Page Categorizer”\u003C\u002Fstrong> plugin is a simple yet powerful solution that enables WordPress users to categorize their Pages using the existing Category and Tag taxonomies. By default, WordPress only allows categorizing Posts, but this plugin extends the functionality to include Pages as well.\u003C\u002Fp>\n\u003Cp>With this plugin activated, users can easily assign Categories and Tags to their Pages, just like they would for Posts. This feature enhances the organization and structure of website content, making it easier for visitors to navigate and find relevant information.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Assign Categories to Pages\u003C\u002Fstrong>: Users can associate one or more Categories with their Pages, providing better content organization and hierarchical structure.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Add Tags to Pages\u003C\u002Fstrong>: Similar to Posts, users can add relevant Tags to their Pages, allowing for improved searchability and content discovery.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Integrated into the WordPress Admin\u003C\u002Fstrong>: The plugin seamlessly integrates with the WordPress admin interface, providing a familiar user experience. Users can assign Categories and Tags to Pages directly from the Page editing screen, just like they do for Posts.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Category and Tag Archives\u003C\u002Fstrong>: The plugin automatically includes Pages in the category and tag archive pages (archive.php and tag.php templates), making it easy for visitors to browse and discover relevant Pages based on their assigned Categories and Tags.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Compatibility\u003C\u002Fstrong>: The plugin is compatible with the latest versions of WordPress and follows the WordPress coding standards, ensuring a smooth integration with other plugins and themes.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>What are the benefits?\u003C\u002Fh4>\n\u003Cp>There are various benefits of adding categories to Pages. You can:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Embed a Category Based List of Pages \u003C\u002Fli>\n\u003Cli>Create a Tag-based archive for Pages\u003C\u002Fli>\n\u003Cli>Create a Category based Archive for Pages\u003C\u002Fli>\n\u003Cli>Hide Pages belonging to certain Categories. \u003C\u002Fli>\n\u003Cli>and so much more.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>In case of any issues with the plugin, get support via the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fadd-category-to-pages\u002F\" rel=\"ugc\">Forums\u003C\u002Fa>.\u003C\u002Fp>\n","Easily add Categories to WordPress Pages.",80,1628,"2025-11-29T17:22:00.000Z","6.0",[51,52,53,54,55],"add","category","page","page-archive","tag","https:\u002F\u002Flumumbas.blog\u002Fplugins\u002Fpage-categorizer\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpage-categorizer.1.4.0.zip",100,null,{"slug":61,"name":62,"version":63,"author":5,"author_profile":6,"description":64,"short_description":65,"active_installs":37,"downloaded":66,"rating":37,"num_ratings":37,"last_updated":67,"tested_up_to":25,"requires_at_least":68,"requires_php":69,"tags":70,"homepage":76,"download_link":77,"security_score":58,"vuln_count":37,"unpatched_count":37,"last_vuln_date":59,"fetched_at":39},"lumiblog-debug-log-inspector","Lumiblog Debug Log Inspector","1.1.0","\u003Cp>Lumiblog Debug Log Inspector is a powerful quality assurance and debugging tool that monitors your WordPress debug.log file for plugin-specific errors. Unlike other debug tools, it allows you to \u003Cstrong>monitor ANY WordPress plugin\u003C\u002Fstrong> through an easy-to-use settings interface – no coding required!\u003C\u002Fp>\n\u003Ch4>Key Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Universal Plugin Monitoring\u003C\u002Fstrong>: Add any WordPress plugin to monitor through a simple settings page\u003C\u002Fli>\n\u003Cli>\u003Cstrong>No Code Editing\u003C\u002Fstrong>: Add\u002Fedit\u002Fdelete monitored plugins through the WordPress admin interface\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Real-time Monitoring\u003C\u002Fstrong>: Automatically scans your debug.log file for errors\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Visual Status Indicators\u003C\u002Fstrong>: Color-coded admin bar display (Green = OK, Red = Errors Found, Gray = Debug Logging Disabled)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Auto-Detection\u003C\u002Fstrong>: Option to only monitor plugins that are currently active\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Plugin-Specific Tracking\u003C\u002Fstrong>: Individual status for each monitored plugin\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Last Error Display\u003C\u002Fstrong>: Shows the most recent error message for quick diagnosis\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Duplicate Prevention\u003C\u002Fstrong>: Smart validation prevents adding the same plugin twice\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Enable\u002FDisable Plugins\u003C\u002Fstrong>: Toggle monitoring for specific plugins without deleting them\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Lightweight\u003C\u002Fstrong>: Minimal performance impact with efficient log reading\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Well-Organized Code\u003C\u002Fstrong>: Modular file structure for easy maintenance and customization\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Perfect For\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>QA Teams testing multiple plugins\u003C\u002Fli>\n\u003Cli>Plugin Developers debugging their own plugins\u003C\u002Fli>\n\u003Cli>WordPress Developers monitoring client sites\u003C\u002Fli>\n\u003Cli>Agency Teams managing multiple WordPress installations\u003C\u002Fli>\n\u003Cli>Anyone who wants to keep track of plugin errors\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>How It Works\u003C\u002Fh4>\n\u003Col>\n\u003Cli>Install and activate the plugin\u003C\u002Fli>\n\u003Cli>Go to Settings > Log Inspector\u003C\u002Fli>\n\u003Cli>Add any plugin you want to monitor by providing:\n\u003Cul>\n\u003Cli>Plugin Name (e.g., “WooCommerce”)\u003C\u002Fli>\n\u003Cli>Plugin File Path (e.g., “woocommerce\u002Fwoocommerce.php”)\u003C\u002Fli>\n\u003Cli>Search Terms (e.g., “woocommerce, wc-“)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Check the admin bar for real-time error status\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Requirements\u003C\u002Fh4>\n\u003Cp>To use this plugin effectively, you need to enable WordPress debug logging by adding these constants to your \u003Ccode>wp-config.php\u003C\u002Fcode> file:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'WP_DEBUG', true );\ndefine( 'WP_DEBUG_LOG', true );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3>Testing the Plugin\u003C\u002Fh3>\n\u003Cp>To verify Lumiblog Debug Log Inspector is working correctly, follow these steps:\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Step 1: Enable Debug Logging\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Add to your \u003Ccode>wp-config.php\u003C\u002Fcode>:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'WP_DEBUG', true );\ndefine( 'WP_DEBUG_LOG', true );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Step 2: Add a Plugin to Monitor\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Col>\n\u003Cli>Go to Settings > Log Inspector\u003C\u002Fli>\n\u003Cli>Click “Add New Plugin to Monitor”\u003C\u002Fli>\n\u003Cli>Fill in the form with a plugin you have installed (e.g., WooCommerce)\n\u003Cul>\n\u003Cli>Plugin Name: \u003Ccode>WooCommerce\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Plugin File Path: \u003Ccode>woocommerce\u002Fwoocommerce.php\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Search Terms: \u003Ccode>woocommerce, wc-\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Click “Add Plugin”\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>\u003Cstrong>Step 3: Generate a Test Error\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Note: Ensure that the test site is running on PHP 8.4+\u003C\u002Fp>\n\u003Col>\n\u003Cli>\n\u003Cp>Add this code snippet inside of any active plugin’s main file:\u003C\u002Fp>\n\u003Cp>\u002F**\u003C\u002Fp>\n\u003Cul>\n\u003Cli>DEBUG LOG INSPECTOR DEMO – PHP 8.4 Warning Trigger\u003C\u002Fli>\n\u003Cli>REMOVE AFTER DEMO\u002FTESTING!\u003Cbr \u002F>\n*\u002F\u003Cbr \u002F>\nadd_action( ‘load-index.php’, function() {\u003Cbr \u002F>\nif ( version_compare( PHP_VERSION, ‘8.4.0’, ‘>=’ ) ) {\u003Cbr \u002F>\n    $test_array = array( ‘name’ => ‘Debug Log Inspector’ );\u003Cbr \u002F>\n    $undefined_value = $test_array[’email’]; \u002F\u002F Triggers warning\u003Cbr \u002F>\n    error_log( ‘[DLI-DEMO-PHP84] PHP 8.4 warning triggered!’ );\u003Cbr \u002F>\n}\u003Cbr \u002F>\n});\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Reload the site’s admin dashboard to trigger the error\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>Check your admin bar – it should turn RED\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>\u003Cstrong>Step 4: View the Debug Log (Optional)\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Navigate to \u003Ccode>wp-content\u002Fdebug.log\u003C\u002Fcode> to see the actual error entries that were logged.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Clean Up:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Col>\n\u003Cli>Remove the test code you added\u003C\u002Fli>\n\u003Cli>Either delete \u003Ccode>wp-content\u002Fdebug.log\u003C\u002Fcode> or clear its contents\u003C\u002Fli>\n\u003Cli>The admin bar should return to GREEN\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>Additional Information\u003C\u002Fh3>\n\u003Ch4>Debug Constants\u003C\u002Fh4>\n\u003Cp>For enhanced debugging, you can also add these optional constants to your \u003Ccode>wp-config.php\u003C\u002Fcode>:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'SCRIPT_DEBUG', true );\ndefine( 'SAVEQUERIES', true );\ndefine( 'WP_DEBUG_DISPLAY', false ); \u002F\u002F Set to false on production sites\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>For Developers\u003C\u002Fh4>\n\u003Cp>The plugin is designed to be easily extendable. All classes are well-documented and follow WordPress coding standards. Feel free to fork and customize for your specific needs.\u003C\u002Fp>\n\u003Ch4>Support\u003C\u002Fh4>\n\u003Cp>For support, feature requests, or bug reports, please visit the WordPress.org support forums for this plugin.\u003C\u002Fp>\n\u003Ch4>Contributing\u003C\u002Fh4>\n\u003Cp>Contributions are welcome! Please visit the plugin’s \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Flumumbapl\u002Flumiblog-debug-log-inspector\" rel=\"nofollow ugc\">Github Repo\u003C\u002Fa> for more information.\u003C\u002Fp>\n","Monitor debug logs for any WordPress plugin errors and display real-time status in the WordPress admin bar.",143,"2026-02-15T16:49:00.000Z","5.0","7.0",[71,72,73,74,75],"debug","error-tracking","log","monitor","testing","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Flumiblog-debug-log-inspector\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flumiblog-debug-log-inspector.1.1.0.zip"]