10% vavavoos-wp-expert

Code Review | VAVAVOOS - Wordpress Expert

WordPress plugin VAVAVOOS - Wordpress Expert scored10%from 54 tests.

About plugin

  • Plugin page: vavavoos-wp-expert
  • Plugin version: 0.0.9
  • PHP version: 7.4.16
  • WordPress version: 6.3.1
  • First release: May 5, 2015
  • Latest release: Jun 25, 2015
  • Number of updates: 22
  • Update frequency: every 2.4 days
  • Top authors: scottund (100%)

Code review

54 tests

User reviews

2 reviews

Install metrics

10+ active /785 total downloads

Benchmarks

Plugin footprint 40% from 16 tests

Installer 0% from 1 test

🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
The following installer errors require your attention
  • Install procedure had errors
    • > Warning in wp-content/plugins/vavavoos-wp-expert/global.php+4
    Use of undefined constant VAORIGIN - assumed 'VAORIGIN' (this will throw an Error in a future version of PHP)

Server metrics [RAM: ▼1.88MB] [CPU: ▼54.58ms] Passed 4 tests

An overview of server-side resources used by VAVAVOOS - Wordpress Expert
This plugin does not affect your website's performance
PageMemory (MB)CPU Time (ms)
Home /2.10 ▼1.365.08 ▼35.59
Dashboard /wp-admin2.12 ▼1.187.52 ▼49.15
Posts /wp-admin/edit.php2.12 ▼1.237.16 ▼41.21
Add New Post /wp-admin/post-new.php2.12 ▼3.767.19 ▼92.36
Media Library /wp-admin/upload.php2.12 ▼1.116.26 ▼31.88
Find WP Experts /wp-admin/admin.php?page=Virtual_Assistant2.126.80
Manage My Expert/s /wp-admin/admin.php?page=Manage_Assistant2.126.41
Temporary Access Rights Admin /wp-admin/admin.php?page=permission2.127.37

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

A short overview of filesystem and database impact
These are issues you should consider
  • Illegal file modification found: 1 file (4.00KB) outside of "wp-content/plugins/vavavoos-wp-expert/" and "wp-content/uploads/"
    • (new file) wp-content/mgd_mirror/mgd_maximinodotpy-gitdown-test-repository
Filesystem: 46 new files
Database: no new tables, 6 new options
New WordPress options
widget_theysaidso_widget
can_compress_scripts
db_upgraded
widget_recent-posts
theysaidso_admin_options
widget_recent-comments

Browser metrics Passed 4 tests

VAVAVOOS - Wordpress Expert: an overview of browser usage
This plugin renders optimally with no browser resource issues detected
PageNodesMemory (MB)Script (ms)Layout (ms)
Home /3,082 ▲32114.55 ▲0.028.26 ▲6.4436.74 ▼5.00
Dashboard /wp-admin2,291 ▲885.24 ▼0.67107.86 ▲3.7958.20 ▲14.88
Posts /wp-admin/edit.php2,152 ▲522.37 ▲0.3537.58 ▲2.7637.53 ▲3.97
Add New Post /wp-admin/post-new.php1,744 ▲21221.69 ▼1.62686.86 ▲62.1639.33 ▼15.22
Media Library /wp-admin/upload.php1,470 ▲674.56 ▲0.29107.53 ▲5.3948.55 ▲2.23
Find WP Experts /wp-admin/admin.php?page=Virtual_Assistant9182.1331.2730.17
Manage My Expert/s /wp-admin/admin.php?page=Manage_Assistant9212.1528.9427.36
Temporary Access Rights Admin /wp-admin/admin.php?page=permission8562.1630.7529.27

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

🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
These items require your attention
  • Uninstall procedure validation failed for this plugin
    • > Warning in wp-content/plugins/vavavoos-wp-expert/global.php+4
    Use of undefined constant VAORIGIN - assumed 'VAORIGIN' (this will throw an Error in a future version of PHP)
  • This plugin did not uninstall successfully, leaving 6 options in the database
    • widget_recent-comments
    • db_upgraded
    • widget_recent-posts
    • can_compress_scripts
    • widget_theysaidso_widget
    • theysaidso_admin_options

Smoke tests 25% from 4 tests

Server-side errors 0% from 1 test

🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Almost there, just fix the following server-side errors
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > Warning in wp-content/plugins/vavavoos-wp-expert/global.php+4
    Use of undefined constant VAORIGIN - assumed 'VAORIGIN' (this will throw an Error in a future version of PHP)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > Warning in wp-content/plugins/vavavoos-wp-expert/global.php+5
    Use of undefined constant VABASEURL - assumed 'VABASEURL' (this will throw an Error in a future version of PHP)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > Warning in wp-content/plugins/vavavoos-wp-expert/global.php+6
    Use of undefined constant VAFIXIESBASEURL - assumed 'VAFIXIESBASEURL' (this will throw an Error in a future version of PHP)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > Warning in wp-content/plugins/vavavoos-wp-expert/global.php+7
    Use of undefined constant VAVAVOOS_PLUGINURL - assumed 'VAVAVOOS_PLUGINURL' (this will throw an Error in a future version of PHP)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > Warning in wp-content/plugins/vavavoos-wp-expert/global.php+8
    Use of undefined constant VAMENUPAGE - assumed 'VAMENUPAGE' (this will throw an Error in a future version of PHP)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > Warning in wp-content/plugins/vavavoos-wp-expert/global.php+9
    Use of undefined constant VACURRENTURL - assumed 'VACURRENTURL' (this will throw an Error in a future version of PHP)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > User notice in wp-includes/functions.php+5905
    Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the jquery handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > User notice in wp-includes/functions.php+5905
    Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the jquery-ui-widget handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > User notice in wp-includes/functions.php+5905
    Function wp_register_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the wpe_file_upload handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > User notice in wp-includes/functions.php+5905
    Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the wpe_file_upload handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > User notice in wp-includes/functions.php+5905
    Function wp_register_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the wpe_master handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > User notice in wp-includes/functions.php+5905
    Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the wpe_master handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > User notice in wp-includes/functions.php+5905
    Function wp_register_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the wpe_deserialize handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > User notice in wp-includes/functions.php+5905
    Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the wpe_deserialize handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > User notice in wp-includes/functions.php+5905
    Function wp_register_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the wpe_iframe handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > User notice in wp-includes/functions.php+5905
    Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the wpe_iframe handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > User notice in wp-includes/functions.php+5905
    Function wp_register_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the wpe_bootstrap handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > User notice in wp-includes/functions.php+5905
    Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the wpe_bootstrap handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > User notice in wp-includes/functions.php+5905
    Function wp_register_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the wpe_momentjs handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > User notice in wp-includes/functions.php+5905
    Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the wpe_momentjs handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > User notice in wp-includes/functions.php+5905
    Function wp_register_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the wpe_bootstrapdatetimepicker handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > User notice in wp-includes/functions.php+5905
    Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the wpe_bootstrapdatetimepicker handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > User notice in wp-includes/functions.php+5905
    Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the wpe_html5shiv handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > User notice in wp-includes/functions.php+5905
    Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the wpe_respond handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > User notice in wp-includes/functions.php+5905
    Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the wpe_bootstrap handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > User notice in wp-includes/functions.php+5905
    Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the wpe_bootstraptheme handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > User notice in wp-includes/functions.php+5905
    Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the wpe_style handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > User notice in wp-includes/functions.php+5905
    Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the wpe_fontawesome handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > User notice in wp-includes/functions.php+5905
    Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the wpe_bootstrapdatepicker handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > User notice in wp-includes/functions.php+5905
    Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the wpe_customdesign handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > User notice in wp-includes/functions.php+5905
    Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the wpe_fixies handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > Warning in wp-content/plugins/vavavoos-wp-expert/vavavoos_wpexpert.php+27
    Use of undefined constant vavavoos_plugin_page - assumed 'vavavoos_plugin_page' (this will throw an Error in a future version of PHP)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > Warning in wp-content/plugins/vavavoos-wp-expert/vavavoos_wpexpert.php+28
    Use of undefined constant vavavoos_pluginmanageassistant_page - assumed 'vavavoos_pluginmanageassistant_page' (this will throw an Error in a future version of PHP)
  • 3 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=permission
    • > Warning in wp-content/plugins/vavavoos-wp-expert/vavavoos_wpexpert.php+29
    Use of undefined constant vavavoos_permission_page - assumed 'vavavoos_permission_page' (this will throw an Error in a future version of PHP)
  • 4 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=Manage_Assistant
    • > Notice in wp-content/plugins/vavavoos-wp-expert/layout.phtml+27
    Undefined index: menu
  • 2 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=Manage_Assistant
    • > Notice in wp-content/plugins/vavavoos-wp-expert/layout.phtml+104
    Undefined variable: VA

SRP 50% from 2 tests

🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Please take a closer look at the following
  • 6× GET requests to PHP files have triggered server-side errors or warnings:
    • > PHP Warning
      Use of undefined constant VABASEURL - assumed 'VABASEURL' (this will throw an Error in a future version of PHP) in wp-content/plugins/vavavoos-wp-expert/global.php on line 5
    • > PHP Warning
      Use of undefined constant VAFIXIESBASEURL - assumed 'VAFIXIESBASEURL' (this will throw an Error in a future version of PHP) in wp-content/plugins/vavavoos-wp-expert/global.php on line 6
    • > PHP Warning
      Use of undefined constant VAVAVOOS_PLUGINURL - assumed 'VAVAVOOS_PLUGINURL' (this will throw an Error in a future version of PHP) in wp-content/plugins/vavavoos-wp-expert/global.php on line 7
    • > PHP Warning
      Use of undefined constant VAORIGIN - assumed 'VAORIGIN' (this will throw an Error in a future version of PHP) in wp-content/plugins/vavavoos-wp-expert/global.php on line 4
    • > PHP Fatal error
      Uncaught Error: Call to undefined function add_action() in wp-content/plugins/vavavoos-wp-expert/vavavoos_wpexpert.php:11
    • > PHP Fatal error
      Uncaught Error: Call to undefined function plugin_dir_url() in wp-content/plugins/vavavoos-wp-expert/global.php:7

User-side errors 0% from 1 test

🔹 Test weight: 20 | This is a shallow check for browser errors
Please fix the following user-side errors
  • 2 occurences, only the last one shown
    • > GET request to /wp-admin/admin.php?page=Manage_Assistant
    • > Network (severe)
    http://app.vavavoos.com/app/index/getview - Failed to load resource: net::ERR_NAME_NOT_RESOLVED
    • > GET request to /wp-admin/admin.php?page=permission
    • > Network (severe)
    http://app.vavavoos.com/app/index/wppem - Failed to load resource: net::ERR_NAME_NOT_RESOLVED

Optimizations

Plugin configuration 83% from 29 tests

readme.txt 75% from 16 tests

The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
Please fix the following attributes:
  • Screenshots: Add images for these screenshots: #1 (Search and Filter all wordress experts.), #2 (Post a new wordpress job.), #3 (List of all jobs with job details.)
  • Requires at least: Invalid plugin version format
  • Donate link: Invalid URI ("Vavavoos.com")
  • Tested up to: Invalid plugin version format
You can look at the official readme.txt

vavavoos-wp-expert/vavavoos_wpexpert.php 92% from 13 tests

The main PHP file in "VAVAVOOS - Wordpress Expert" ver. 0.0.9 adds more information about the plugin and also serves as the entry point for this plugin
The following require your attention:
  • Main file name: Please rename the main PHP file in this plugin to the plugin slug ("vavavoos-wp-expert.php" instead of "vavavoos_wpexpert.php")

Code Analysis Passed 3 tests

File types Passed 1 test

🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
No dangerous file extensions were detected11,121 lines of code in 26 files:
LanguageFilesBlank linesComment linesLines of code
CSS91,182367,134
JavaScript106757082,930
SVG200643
PHP45931413
Markdown1001

PHP code Passed 2 tests

This is a very shot review of cyclomatic complexity and code structure
No complexity issues detected
Cyclomatic complexity
Average complexity per logical line of code0.25
Average class complexity0.00
▷ Minimum class complexity0.00
▷ Maximum class complexity0.00
Average method complexity0.00
▷ Minimum method complexity0.00
▷ Maximum method complexity0.00
Code structure
Namespaces0
Interfaces0
Traits0
Classes0
▷ Abstract classes00.00%
▷ Concrete classes00.00%
▷ Final classes00.00%
Methods0
▷ Static methods00.00%
▷ Public methods00.00%
▷ Protected methods00.00%
▷ Private methods00.00%
Functions11
▷ Named functions1090.91%
▷ Anonymous functions19.09%
Constants6
▷ Global constants6100.00%
▷ Class constants00.00%
▷ Public constants00.00%

Plugin size 50% from 2 tests

Image compression 50% from 2 tests

Often times overlooked, PNG files can occupy unnecessary space in your plugin
9 PNG files occupy 1.17MB with 0.69MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant
FileSize - originalSize - compressedSavings
screenshot-2.png90.88KB37.25KB▼ 59.01%
screenshot-3.png86.04KB34.65KB▼ 59.73%
assets/img/shortlogo.png7.98KB3.26KB▼ 59.13%
assets/img/logo.png6.89KB2.88KB▼ 58.16%
assets/img/fixiesonvavavoos.png9.96KB3.98KB▼ 60.08%