WP Cloud Gallery 1.1

Does WP Cloud Gallery work with WordPress 5.0.3 and PHP 7.0.16? A smoke test was performed on .

Summary

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

Memory usage: 13.9 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.0.3
PHP version7.0.16
MySQL version5.7.17
PHP memory limit256M
Plugin Info
Last updated
Active installs 60+
WordPress.org page https://wordpress.org/plugins/wp-cloud-gallery/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 22

Plugins ‹ Test site — WordPress

Page screenshot: Plugins ‹ Test site — WordPress
URL /wp-admin/plugins.php?charsout=6&plugin=wp-cloud-gallery%2Fwpcloudgallery.php&plugin_status=all&paged=1&s
Requested URL /wp-admin/plugins.php?action=activate&plugin=wp-cloud-gallery%2Fwpcloudgallery.php&plugin_status=all&paged=1&s&_wpnonce=2c07ff5cb5
Aspect after-activation
HTTP status 200
Load time 0.333 s
Memory usage 3.19 MiB
JS errors None
Resource errors None

CloudGallery

Page screenshot: CloudGallery
URL /wp-admin/admin.php?page=wpcloudgallery_settings_page
Aspect menu-item
HTTP status 200
Load time 12.074 s
Memory usage 3.08 MiB
JS errors None
Resource errors None

CloudGallery → Themes

Page screenshot: CloudGallery → Themes
URL /wp-admin/admin.php?page=wpcloudgallery_settings_page&tab=themes
Aspect menu-item-tab
HTTP status 200
Load time 1.312 s
Memory usage 3.08 MiB
JS errors None
Resource errors None

CloudGallery → Shortcodes

Page screenshot: CloudGallery → Shortcodes
URL /wp-admin/admin.php?page=wpcloudgallery_settings_page&tab=shortcodes
Aspect menu-item-tab
HTTP status 200
Load time 0.993 s
Memory usage 3.08 MiB
JS errors None
Resource errors None

CloudGallery → API Key

Page screenshot: CloudGallery → API Key
URL /wp-admin/admin.php?page=wpcloudgallery_settings_page&tab=apikey
Aspect menu-item-tab
HTTP status 200
Load time 0.139 s
Memory usage 3.08 MiB
JS errors None
Resource errors None

CloudGallery → About / FAQ

Page screenshot: CloudGallery → About / FAQ
URL /wp-admin/admin.php?page=wpcloudgallery_settings_page&tab=about
Aspect menu-item-tab
HTTP status 200
Load time 0.174 s
Memory usage 3.08 MiB
JS errors None
Resource errors None

CloudGallery → SmugMug

Page screenshot: CloudGallery → SmugMug
URL /wp-admin/admin.php?page=wpcloudgallery_settings_page_smugmug
Aspect menu-item
HTTP status 200
Load time 3.598 s
Memory usage 3.08 MiB
JS errors None
Resource errors None

CloudGallery → SmugMug → Themes

Page screenshot: CloudGallery → SmugMug → Themes
URL /wp-admin/admin.php?page=wpcloudgallery_settings_page_smugmug&tab=themes
Aspect menu-item-tab
HTTP status 200
Load time 0.848 s
Memory usage 3.08 MiB
JS errors None
Resource errors None

CloudGallery → SmugMug → Shortcodes

Page screenshot: CloudGallery → SmugMug → Shortcodes
URL /wp-admin/admin.php?page=wpcloudgallery_settings_page_smugmug&tab=shortcodes
Aspect menu-item-tab
HTTP status 200
Load time 0.697 s
Memory usage 3.08 MiB
JS errors None
Resource errors None

CloudGallery → SmugMug → About

Page screenshot: CloudGallery → SmugMug → About
URL /wp-admin/admin.php?page=wpcloudgallery_settings_page_smugmug&tab=about
Aspect menu-item-tab
HTTP status 200
Load time 0.185 s
Memory usage 3.08 MiB
JS errors None
Resource errors None

CloudGallery → Instagram

Page screenshot: CloudGallery → Instagram
URL /wp-admin/admin.php?page=wpcloudgallery_settings_page_instagram
Aspect menu-item
HTTP status 200
Load time 1.412 s
Memory usage 3.08 MiB
JS errors None
Resource errors None

CloudGallery → Instagram → Themes

Page screenshot: CloudGallery → Instagram → Themes
URL /wp-admin/admin.php?page=wpcloudgallery_settings_page_instagram&tab=themes
Aspect menu-item-tab
HTTP status 200
Load time 0.636 s
Memory usage 3.08 MiB
JS errors None
Resource errors None

CloudGallery → Instagram → Shortcodes

Page screenshot: CloudGallery → Instagram → Shortcodes
URL /wp-admin/admin.php?page=wpcloudgallery_settings_page_instagram&tab=shortcodes
Aspect menu-item-tab
HTTP status 200
Load time 0.417 s
Memory usage 3.08 MiB
JS errors None
Resource errors None

CloudGallery → Instagram → About

Page screenshot: CloudGallery → Instagram → About
URL /wp-admin/admin.php?page=wpcloudgallery_settings_page_instagram&tab=about
Aspect menu-item-tab
HTTP status 200
Load time 0.226 s
Memory usage 3.08 MiB
JS errors None
Resource errors None

CloudGallery → YouTube

Page screenshot: CloudGallery → YouTube
URL /wp-admin/admin.php?page=wpcloudgallery_settings_page_youtube
Aspect menu-item
HTTP status 200
Load time 1.707 s
Memory usage 3.08 MiB
JS errors None
Resource errors None

CloudGallery → YouTube → Themes

Page screenshot: CloudGallery → YouTube → Themes
URL /wp-admin/admin.php?page=wpcloudgallery_settings_page_youtube&tab=themes
Aspect menu-item-tab
HTTP status 200
Load time 0.807 s
Memory usage 3.08 MiB
JS errors None
Resource errors None

CloudGallery → YouTube → Shortcodes

Page screenshot: CloudGallery → YouTube → Shortcodes
URL /wp-admin/admin.php?page=wpcloudgallery_settings_page_youtube&tab=shortcodes
Aspect menu-item-tab
HTTP status 200
Load time 0.700 s
Memory usage 3.08 MiB
JS errors None
Resource errors None

CloudGallery → YouTube → About

Page screenshot: CloudGallery → YouTube → About
URL /wp-admin/admin.php?page=wpcloudgallery_settings_page_youtube&tab=about
Aspect menu-item-tab
HTTP status 200
Load time 0.233 s
Memory usage 3.08 MiB
JS errors None
Resource errors None

CloudGallery → API Key

Page screenshot: CloudGallery → API Key
URL /wp-admin/admin.php?page=wpcloudgallery_settings_page_apikey
Aspect menu-item
HTTP status 200
Load time 0.202 s
Memory usage 3.08 MiB
JS errors None
Resource errors None

CloudGallery → API Key → API Key

Page screenshot: CloudGallery → API Key → API Key
URL /wp-admin/admin.php?page=wpcloudgallery_settings_page_apikey&tab=apikey
Aspect menu-item-tab
HTTP status 200
Load time 0.217 s
Memory usage 3.08 MiB
JS errors None
Resource errors None

CloudGallery → API Key → About / FAQ

Page screenshot: CloudGallery → API Key → About / FAQ
URL /wp-admin/admin.php?page=wpcloudgallery_settings_page_apikey&tab=about
Aspect menu-item-tab
HTTP status 200
Load time 0.229 s
Memory usage 3.08 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.327 s
Memory usage 2.92 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.295 s0.254 s-0.041 s3.22 MiB3.23 MiB+ 14.01 KiB
/wp-admin/edit.php0.198 s0.205 s+0.007 s3.25 MiB3.27 MiB+ 13.98 KiB
/wp-admin/post-new.php1.043 s1.254 s+0.211 s4.92 MiB4.94 MiB+ 21.15 KiB
/wp-admin/upload.php0.465 s0.369 s-0.096 s3.15 MiB3.16 MiB+ 14.09 KiB
/wp-admin/options-writing.php0.228 s0.128 s-0.100 s3.14 MiB3.15 MiB+ 14.49 KiB
/wp-admin/media-new.php0.224 s0.178 s-0.046 s3.07 MiB3.08 MiB+ 14.49 KiB
/wp-admin/edit-tags.php?taxonomy=category0.234 s0.192 s-0.042 s3.17 MiB3.18 MiB+ 14.49 KiB
/wp-admin/post-new.php?post_type=page1.019 s0.830 s-0.189 s4.9 MiB4.92 MiB+ 13.89 KiB
/wp-admin/options-discussion.php0.226 s0.224 s-0.002 s3.07 MiB3.09 MiB+ 14.49 KiB
/wp-admin/edit-comments.php0.220 s0.205 s-0.015 s3.18 MiB3.19 MiB+ 13.93 KiB
/0.403 s0.190 s-0.213 s2.92 MiB2.93 MiB+ 3.91 KiB
Average 0.414 s0.366 s-0.048 s3.45 MiB3.47 MiB+ 13.9 KiB

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.

No new entries found.

PHP Error Log 54 lines

[23-Jan-2019 01:06:25 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:06:26 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:06:26 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:06:39 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:06:40 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:06:42 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:06:42 UTC] PHP Notice:  Undefined variable: confirmSave in /wp-content/plugins/wp-cloud-gallery/wpcl-main.php on line 148
[23-Jan-2019 01:06:42 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:06:43 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:06:47 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:06:49 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:06:50 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:06:50 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:06:52 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:06:53 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:06:54 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:06:55 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:06:57 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:06:58 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:07:00 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:07:00 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:07:00 UTC] PHP Notice:  Undefined variable: wpcloudgallery_active_tab in /wp-content/plugins/wp-cloud-gallery/wpcl-apikey.php on line 17
[23-Jan-2019 01:07:00 UTC] PHP Notice:  Undefined variable: wpcloudgallery_active_tab in /wp-content/plugins/wp-cloud-gallery/wpcl-apikey.php on line 18
[23-Jan-2019 01:07:00 UTC] PHP Notice:  Undefined variable: confirmSave in /wp-content/plugins/wp-cloud-gallery/wpcl-apikey.php on line 56
[23-Jan-2019 01:07:01 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:07:01 UTC] PHP Notice:  Undefined variable: wpcloudgallery_active_tab in /wp-content/plugins/wp-cloud-gallery/wpcl-apikey.php on line 17
[23-Jan-2019 01:07:01 UTC] PHP Notice:  Undefined variable: wpcloudgallery_active_tab in /wp-content/plugins/wp-cloud-gallery/wpcl-apikey.php on line 18
[23-Jan-2019 01:07:01 UTC] PHP Notice:  Undefined variable: confirmSave in /wp-content/plugins/wp-cloud-gallery/wpcl-apikey.php on line 56
[23-Jan-2019 01:07:01 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:07:01 UTC] PHP Notice:  Undefined variable: wpcloudgallery_active_tab in /wp-content/plugins/wp-cloud-gallery/wpcl-apikey.php on line 17
[23-Jan-2019 01:07:01 UTC] PHP Notice:  Undefined variable: wpcloudgallery_active_tab in /wp-content/plugins/wp-cloud-gallery/wpcl-apikey.php on line 18
[23-Jan-2019 01:07:02 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:07:03 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:07:03 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:07:04 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:07:04 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:07:05 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:07:05 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:07:05 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:07:05 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:07:05 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:07:05 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:07:05 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:07:06 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:07:06 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:07:07 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:07:07 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:07:07 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:07:07 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:07:07 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:07:07 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:07:07 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:07:08 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
[23-Jan-2019 01:07:08 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.0.) in /wp-includes/functions.php on line 4231
See also: All tests for this plugin, How to Hide WP Cloud Gallery Admin Menus