FV Player 7.4.41.727

Does FV Player work with WordPress 5.7 and PHP 7.4.8? A smoke test was performed on .

Summary

Errors
11PHP notices
No JavaScript exceptions
All test pages loaded successfully
No resource errors
Performance

Memory usage: 368.25 KiB
The average PHP memory usage increased by this amount after activating by the plugin.

Page speed impact: insignificant.
The plugin didn't make the site noticeably slower.

Environment
WordPress version5.7
PHP version7.4.8
MySQL version8.0.21
PHP memory limit256M
Plugin Info
Last updated
Active installs 20,000+
WordPress.org page https://wordpress.org/plugins/fv-wordpress-flowplayer/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 11

Plugins ‹ Test site — WordPress

Page screenshot: Plugins ‹ Test site — WordPress
URL /wp-admin/plugins.php?plugin_status=all&paged=1&s
Requested URL /wp-admin/plugins.php?action=activate&plugin=fv-wordpress-flowplayer%2Fflowplayer.php&plugin_status=all&paged=1&s&_wpnonce=ec0c62a474
Aspect after-activation
HTTP status 200
Load time 0.368 s
Memory usage 3.24 MiB
JS errors None
Resource errors None

FV Player

Page screenshot: FV Player
URL /wp-admin/admin.php?page=fv_player
Aspect menu-item
HTTP status 200
Load time 1.123 s
Memory usage 4.27 MiB
JS errors None
Resource errors None

FV Player → Settings

Page screenshot: FV Player → Settings
URL /wp-admin/options-general.php?page=fvplayer
Aspect menu-item
HTTP status 200
Load time 0.965 s
Memory usage 3.93 MiB
JS errors None
Resource errors None

FV Player → Settings → Skin

Page screenshot: FV Player → Settings → Skin
URL /wp-admin/options-general.php?page=fvplayer
Aspect menu-item-tab
HTTP status 200
Load time 0.506 s
Memory usage 3.2 MiB
JS errors None
Resource errors None

FV Player → Settings → Hosting

Page screenshot: FV Player → Settings → Hosting
URL /wp-admin/options-general.php?page=fvplayer
Aspect menu-item-tab
HTTP status 200
Load time 0.640 s
Memory usage 3.2 MiB
JS errors None
Resource errors None

FV Player → Settings → Actions

Page screenshot: FV Player → Settings → Actions
URL /wp-admin/options-general.php?page=fvplayer
Aspect menu-item-tab
HTTP status 200
Load time 0.583 s
Memory usage 3.2 MiB
JS errors None
Resource errors None

FV Player → Settings → Tools

Page screenshot: FV Player → Settings → Tools
URL /wp-admin/options-general.php?page=fvplayer
Aspect menu-item-tab
HTTP status 200
Load time 0.480 s
Memory usage 3.2 MiB
JS errors None
Resource errors None

FV Player → Settings → Help

Page screenshot: FV Player → Settings → Help
URL /wp-admin/options-general.php?page=fvplayer
Aspect menu-item-tab
HTTP status 200
Load time 0.610 s
Memory usage 3.2 MiB
JS errors None
Resource errors None

FV Player → Settings → vi Ads

Page screenshot: FV Player → Settings → vi Ads
URL /wp-admin/options-general.php?page=fvplayer
Aspect menu-item-tab
HTTP status 200
Load time 0.532 s
Memory usage 3.2 MiB
JS errors None
Resource errors None

Test site – Just another WordPress site

Page screenshot: Test site – Just another WordPress site
URL /
Aspect front-page
HTTP status 200
Load time 0.257 s
Memory usage 2.87 MiB
JS errors None
Resource errors None

Widgets ‹ Test site — WordPress

Page screenshot: Widgets ‹ Test site — WordPress
URL /wp-admin/widgets.php
Aspect new-sidebar-widgets
HTTP status 200
Load time 1.234 s
Memory usage 3.2 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.255 s0.333 s+0.078 s2.82 MiB3.16 MiB+ 343.2 KiB
/wp-admin/edit.php0.178 s0.231 s+0.053 s2.86 MiB3.26 MiB+ 407.7 KiB
/wp-admin/post-new.php0.862 s1.358 s+0.496 s5.02 MiB5.45 MiB+ 434.33 KiB
/wp-admin/upload.php0.458 s0.277 s-0.181 s2.7 MiB3.09 MiB+ 402.27 KiB
/wp-admin/options-writing.php0.262 s0.170 s-0.092 s2.71 MiB3.07 MiB+ 372.44 KiB
/wp-admin/media-new.php0.229 s0.180 s-0.049 s2.67 MiB3.07 MiB+ 404.58 KiB
/wp-admin/edit-tags.php?taxonomy=category0.175 s0.287 s+0.112 s2.77 MiB3.11 MiB+ 343.21 KiB
/wp-admin/post-new.php?post_type=page1.141 s0.768 s-0.373 s5.01 MiB5.43 MiB+ 429.69 KiB
/wp-admin/options-discussion.php0.298 s0.301 s+0.003 s2.67 MiB3.07 MiB+ 404.95 KiB
/wp-admin/edit-comments.php0.234 s0.224 s-0.010 s2.78 MiB3.11 MiB+ 343.2 KiB
/0.251 s0.287 s+0.036 s2.71 MiB2.87 MiB+ 165.17 KiB
Average 0.395 s0.401 s+0.007 s3.16 MiB3.52 MiB+ 368.25 KiB

Code Statistics

Note: Third-party libraries and minified JS/CSS files are excluded from these statistics where possible, so the numbers you see here may be lower than those reported by other tools.

PHP
JavaScript
PO File
CSS
Language % Lines of code Comment lines Files
PHP45.6%16,3292,54761
JavaScript20.3%7,28794849
PO File13.9%4,9642,4314
CSS9.7%3,48011911
HTML7.4%2,66673
JSON1.3%47505
SVG0.6%20305
XSLT0.5%19202
Markdown0.5%16402
XML0.2%6213
Bourne Shell0.0%1101
Total 35,833 6,053 146

PHP Code Analysis | More results »

Lines of code 16,647
Total complexity 4,379
Median class complexity 28.0
Median method complexity 2.0
Most complex class flowplayer
Most complex function flowplayer_frontend::build_min_player()
Classes 49
Methods 549
Functions 148

Additions

Things that the plugin adds to the site. This section is not intended to be comprehensive. The test tool only looks for a few specific types of added content.

Database Tables 3

Options wp_options 5

Sidebar Widgets 1

ID Name
widget_fvplayerFV Player

Meta Boxes

{
    "fv_flowplayer_settings_actions": {
        "fv_flowplayer_email_lists": {
            "title": "Email Popups",
            "context": "normal"
        },
        "fv_flowplayer_email_integration": {
            "title": "Email Integration",
            "context": "normal"
        },
        "fv_flowplayer_video_intelligence_revival": {
            "title": "Free video intelligence ads",
            "context": "normal"
        }
    },
    "fv_flowplayer_settings_video_intelligence": {
        "fv_flowplayer_video_intelligence": {
            "title": "video intelligence",
            "context": "normal"
        },
        "fv_flowplayer_video_intelligence_account": {
            "title": "Account",
            "context": "normal"
        },
        "fv_flowplayer_video_intelligence_hide": {
            "title": "Hide vi Ads",
            "context": "normal"
        }
    },
    "fv_flowplayer_settings_tools": {
        "fv_flowplayer_system_information": {
            "title": "System Info",
            "context": "normal"
        }
    },
    "fv_flowplayer_settings_hosting": {
        "fv_player_digitalocean_spaces": {
            "title": "DigitalOcean Spaces",
            "context": "normal"
        }
    },
    "fv_flowplayer_settings": {
        "fv_flowplayer_conversion": {
            "title": "Conversion",
            "context": "normal"
        }
    }
}

PHP Error Log 11 lines

[10-Mar-2021 02:36:37 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 02:36:38 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 02:36:40 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 02:36:42 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 02:36:44 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 02:36:45 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 02:36:47 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 02:36:49 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 02:36:52 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 02:36:56 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 02:36:59 UTC] PHP Notice:  WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
See also: All tests for this plugin, How to Hide FV Player Admin Menus and Meta Boxes