73% debug-log-parser

Code Review | Debug Log Parser

WordPress plugin Debug Log Parser scored73%from 54 tests.

About plugin

  • Plugin page: debug-log-parser
  • Plugin version: 1.0
  • PHP version: 7.4.16
  • WordPress compatibility: 2.3.1-3.9
  • WordPress version: 6.3.1
  • First release: May 10, 2014
  • Latest release: May 10, 2014
  • Number of updates: 3
  • Update frequency: every 0.3 days
  • Top authors: filme-blog (100%)

Code review

54 tests

User reviews

2 reviews

Install metrics

10+ active /1,121 total downloads

Benchmarks

Plugin footprint 65% from 16 tests

Installer Passed 1 test

🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Install script ran successfully

Server metrics [RAM: ▼1.12MB] [CPU: ▼45.62ms] Passed 4 tests

This is a short check of server-side resources used by Debug Log Parser
Server-side resource usage in normal parameters
PageMemory (MB)CPU Time (ms)
Home /2.85 ▼0.6115.28 ▼26.49
Dashboard /wp-admin2.91 ▼0.4424.70 ▼37.77
Posts /wp-admin/edit.php2.91 ▼0.4520.36 ▼30.49
Add New Post /wp-admin/post-new.php2.91 ▼2.9819.20 ▼87.72
Media Library /wp-admin/upload.php2.91 ▼0.3219.23 ▼16.18

Server storage [IO: ▲0.02MB] [DB: ▲0.00MB] 67% from 3 tests

A short overview of filesystem and database impact
These are issues you should consider
  • The plugin illegally modified 1 file (4.44KB) outside of "wp-content/plugins/debug-log-parser/" and "wp-content/uploads/"
    • (modified) wp-config.php
Filesystem: 10 new files
Database: no new tables, 6 new options
New WordPress options
can_compress_scripts
db_upgraded
widget_recent-posts
theysaidso_admin_options
widget_theysaidso_widget
widget_recent-comments

Browser metrics Passed 4 tests

Debug Log Parser: an overview of browser usage
This plugin renders optimally with no browser resource issues detected
PageNodesMemory (MB)Script (ms)Layout (ms)
Home /2,842 ▲8114.27 ▼0.081.72 ▲0.0340.84 ▲1.64
Dashboard /wp-admin2,248 ▲675.60 ▼0.1195.22 ▼5.8640.79 ▲2.23
Posts /wp-admin/edit.php2,116 ▲162.03 ▲0.0733.07 ▼6.0434.12 ▼3.28
Add New Post /wp-admin/post-new.php1,544 ▲1623.32 ▲0.17662.57 ▼44.0767.27 ▲11.42
Media Library /wp-admin/upload.php1,419 ▲224.18 ▼0.0599.07 ▼7.8245.91 ▼1.48

Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests

🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
You still need to fix the following
  • This plugin cannot be uninstalled
    • > Notice in wp-config.php+132
    Constant WP_DEBUG already defined
  • This plugin did not uninstall successfully, leaving 6 options in the database
    • can_compress_scripts
    • theysaidso_admin_options
    • widget_recent-posts
    • widget_recent-comments
    • db_upgraded
    • widget_theysaidso_widget

Smoke tests 75% from 4 tests

Server-side errors Passed 1 test

🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Even though no errors were found, this is by no means an exhaustive test

SRP 50% from 2 tests

🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
The following issues need your attention
  • 1× GET requests to PHP files have triggered server-side errors or warnings:
    • > PHP Fatal error
      Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/debug-log-parser/debug-log-parser.php:14

User-side errors Passed 1 test

🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser errors were detected

Optimizations

Plugin configuration 93% from 29 tests

readme.txt 94% from 16 tests

It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
These attributes need your attention:
  • Donate link: Invalid URI ("")
You can look at the official readme.txt

debug-log-parser/debug-log-parser.php 92% from 13 tests

The main file in "Debug Log Parser" v. 1.0 serves as a complement to information provided in readme.txt and as the entry point to the plugin
The following require your attention:
  • Text Domain: The text domain is optional since WordPress version 4.6; if you do specify it, it must be the same as the plugin slug

Code Analysis Passed 3 tests

File types Passed 1 test

🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
There were no executable files found in this plugin463 lines of code in 8 files:
LanguageFilesBlank linesComment linesLines of code
PHP799144404
PO File1204259

PHP code Passed 2 tests

This is a short overview of cyclomatic complexity and code structure for this plugin
This plugin has no cyclomatic complexity issues
Cyclomatic complexity
Average complexity per logical line of code0.22
Average class complexity6.67
▷ Minimum class complexity1.00
▷ Maximum class complexity15.00
Average method complexity2.36
▷ Minimum method complexity1.00
▷ Maximum method complexity9.00
Code structure
Namespaces0
Interfaces0
Traits0
Classes6
▷ Abstract classes00.00%
▷ Concrete classes6100.00%
▷ Final classes00.00%
Methods25
▷ Static methods00.00%
▷ Public methods25100.00%
▷ Protected methods00.00%
▷ Private methods00.00%
Functions0
▷ Named functions00.00%
▷ Anonymous functions00.00%
Constants0
▷ Global constants00.00%
▷ Class constants00.00%
▷ Public constants00.00%

Plugin size Passed 2 tests

Image compression Passed 2 tests

It is recommended to compress PNG files in your plugin to minimize bandwidth usage
There were not PNG files found in your plugin