ARVE Advanced Responsive Video Embedder 9.7.10

Does "ARVE Advanced Responsive Video Embedder" work with WordPress 6.0.1 and PHP 7.4.8? A smoke test was performed on .

Summary

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

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

Page speed impact: 0.022 seconds
The average page load time increased by this amount after activating the plugin.

Environment
WordPress version6.0.1
PHP version7.4.8
MySQL version8.0.21
PHP memory limit256M
Plugin Info
Last updated
Active installs 40,000+
WordPress.org page https://wordpress.org/plugins/advanced-responsive-video-embedder/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 7

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=advanced-responsive-video-embedder%2Fadvanced-responsive-video-embedder.php&plugin_status=all&paged=1&s&_wpnonce=f7c719b050
Aspect after-activation
HTTP status 200
Load time 0.760 s
Memory usage 3.9 MiB
JS errors None
Resource errors None

Settings → ARVE

Page screenshot: Settings → ARVE
URL /wp-admin/options-general.php?page=nextgenthemes_arve
Aspect menu-item
HTTP status 200
Load time 0.687 s
Memory usage 3.94 MiB
JS errors None
Resource errors None

Settings → ARVE → All Options

Page screenshot: Settings → ARVE → All Options
URL /wp-admin/options-general.php?page=nextgenthemes_arve
Aspect menu-item-tab
HTTP status 200
Load time 0.492 s
Memory usage 3.94 MiB
JS errors None
Resource errors None

Settings → ARVE → Debug Info

Page screenshot: Settings → ARVE → 
					Debug Info
URL /wp-admin/options-general.php?page=nextgenthemes_arve
Aspect menu-item-tab
HTTP status 200
Load time 0.529 s
Memory usage 3.94 MiB
JS errors None
Resource errors None

Settings → NextGenThemes Settings

Page screenshot: Settings → NextGenThemes Settings
URL /wp-admin/options-general.php?page=nextgenthemes
Aspect menu-item
HTTP status 200
Load time 0.274 s
Memory usage 3.87 MiB
JS errors None
Resource errors None

Settings → NextGenThemes Settings → All Options

Page screenshot: Settings → NextGenThemes Settings → All Options
URL /wp-admin/options-general.php?page=nextgenthemes
Aspect menu-item-tab
HTTP status 200
Load time 0.202 s
Memory usage 3.87 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 3.74 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.332 s0.437 s+0.105 s3.72 MiB3.94 MiB+ 221.98 KiB
/wp-admin/edit.php0.203 s0.220 s+0.017 s3.75 MiB3.96 MiB+ 211.09 KiB
/wp-admin/post-new.php0.786 s1.086 s+0.300 s5.55 MiB5.76 MiB+ 224.1 KiB
/wp-admin/upload.php0.390 s0.414 s+0.024 s3.68 MiB3.9 MiB+ 219.72 KiB
/wp-admin/options-writing.php0.149 s0.165 s+0.016 s3.62 MiB3.87 MiB+ 260.37 KiB
/wp-admin/media-new.php0.430 s0.223 s-0.207 s3.66 MiB3.87 MiB+ 214.76 KiB
/wp-admin/edit-tags.php?taxonomy=category0.186 s0.219 s+0.033 s3.69 MiB3.9 MiB+ 215.04 KiB
/wp-admin/post-new.php?post_type=page0.968 s0.831 s-0.137 s5.54 MiB5.75 MiB+ 215.06 KiB
/wp-admin/options-discussion.php0.238 s0.360 s+0.122 s3.6 MiB3.87 MiB+ 281.26 KiB
/wp-admin/edit-comments.php0.220 s0.258 s+0.038 s3.69 MiB3.9 MiB+ 211.47 KiB
/0.298 s0.225 s-0.073 s3.6 MiB3.74 MiB+ 136.99 KiB
Average 0.382 s0.403 s+0.022 s4.01 MiB4.22 MiB+ 219.26 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
Markdown
Language % Lines of code Comment lines Files
PHP86.2%5,70365142
Markdown12.9%85501
HTML0.7%4905
JavaScript0.1%505
CSS0.0%303
Total 6,615 651 56

PHP Code Analysis | More results »

Lines of code 4,970
Total complexity 922
Median class complexity 43.0
Median method complexity 2.0
Most complex class Nextgenthemes\ARVE\Common\Admin\EDD\PluginUpdater
Most complex function all_settings()
Classes 4
Methods 63
Functions 179

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.

Options wp_options 5

PHP Error Log 46 lines

[10-Aug-2022 16:11:27 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:29 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:29 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:31 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:33 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:35 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:36 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:38 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:39 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:39 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:39 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:39 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:41 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:41 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:41 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:41 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:41 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:41 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:41 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:41 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:41 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:41 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:42 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:42 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:42 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:42 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:42 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:43 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:43 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:44 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:44 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:44 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:44 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:44 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:45 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:45 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:45 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:45 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:45 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:45 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:45 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:46 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:46 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:46 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:46 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
[10-Aug-2022 16:11:47 UTC] PHP Notice:  Function WP_Block_Type_Registry::register was called <strong>incorrectly</strong>. Block type names must contain a namespace prefix. Example: my-plugin/my-custom-block-type 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.0.0.) in /wp-includes/functions.php on line 5831
See also: All tests for this plugin, How to Hide ARVE Advanced Responsive Video Embedder Admin Menus