1. Home
  2. WordPress Cloud Gallery – Responsive Photo and Video Galleries with CDN
  3. 1.3

WP Cloud Gallery 1.3

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

Summary

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

Memory usage: -5.75 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.4
PHP version7.2.16
MySQL version8.0.15
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 19

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=wp-cloud-gallery%2Fwpcloudgallery.php&plugin_status=all&paged=1&s&_wpnonce=799f6e07ef
Aspect after-activation
HTTP status 200
Load time 0.355 s
Memory usage 3.59 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 7.731 s
Memory usage 3.49 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 2.066 s
Memory usage 3.49 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.525 s
Memory usage 3.49 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.143 s
Memory usage 3.49 MiB
JS errors None
Resource errors None

CloudGallery → Import

Page screenshot: CloudGallery → Import
URL /wp-admin/admin.php?page=wpcloudgallery_settings_page&tab=import
Aspect menu-item-tab
HTTP status 200
Load time 0.133 s
Memory usage 3.49 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.137 s
Memory usage 3.49 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 2.270 s
Memory usage 3.49 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.402 s
Memory usage 3.49 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.424 s
Memory usage 3.49 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.136 s
Memory usage 3.49 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 4.090 s
Memory usage 3.49 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.397 s
Memory usage 3.49 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.368 s
Memory usage 3.49 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.146 s
Memory usage 3.49 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.124 s
Memory usage 3.49 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.124 s
Memory usage 3.49 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.131 s
Memory usage 3.49 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.246 s
Memory usage 3.33 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.352 s0.255 s-0.097 s3.64 MiB3.65 MiB+ 16.41 KiB
/wp-admin/edit.php0.192 s0.204 s+0.012 s3.66 MiB3.68 MiB+ 11.66 KiB
/wp-admin/post-new.php1.658 s1.520 s-0.138 s5.43 MiB5.45 MiB+ 22.42 KiB
/wp-admin/upload.php0.772 s0.477 s-0.295 s3.5 MiB3.51 MiB+ 11.13 KiB
/wp-admin/options-writing.php0.172 s0.163 s-0.009 s3.58 MiB3.5 MiB- 82.31 KiB
/wp-admin/media-new.php0.215 s0.188 s-0.027 s3.48 MiB3.49 MiB+ 11.3 KiB
/wp-admin/edit-tags.php?taxonomy=category0.183 s0.181 s-0.002 s3.58 MiB3.6 MiB+ 12.2 KiB
/wp-admin/post-new.php?post_type=page1.158 s1.052 s-0.106 s5.42 MiB5.43 MiB+ 15.6 KiB
/wp-admin/options-discussion.php0.313 s0.489 s+0.176 s3.48 MiB3.5 MiB+ 11.61 KiB
/wp-admin/edit-comments.php0.201 s0.190 s-0.011 s3.59 MiB3.6 MiB+ 10.55 KiB
/0.315 s0.211 s-0.104 s3.43 MiB3.33 MiB- 103.77 KiB
Average 0.503 s0.448 s-0.055 s3.89 MiB3.88 MiB- 5.75 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 51 lines

[06-Apr-2020 10:58:20 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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58:20 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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58:20 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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58:29 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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58:31 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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58:32 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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58:32 UTC] PHP Notice:  Undefined variable: confirmSave in /wp-content/plugins/wp-cloud-gallery/wpcl-main.php on line 150
[06-Apr-2020 10:58:33 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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58:33 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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58:34 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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58:37 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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58:37 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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58:38 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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58: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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58: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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58:44 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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58:45 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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58:45 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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58:45 UTC] PHP Notice:  Undefined variable: wpcloudgallery_active_tab in /wp-content/plugins/wp-cloud-gallery/wpcl-apikey.php on line 18
[06-Apr-2020 10:58:45 UTC] PHP Notice:  Undefined variable: wpcloudgallery_active_tab in /wp-content/plugins/wp-cloud-gallery/wpcl-apikey.php on line 19
[06-Apr-2020 10:58:45 UTC] PHP Notice:  Undefined variable: confirmSave in /wp-content/plugins/wp-cloud-gallery/wpcl-apikey.php on line 57
[06-Apr-2020 10:58:46 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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58:46 UTC] PHP Notice:  Undefined variable: wpcloudgallery_active_tab in /wp-content/plugins/wp-cloud-gallery/wpcl-apikey.php on line 18
[06-Apr-2020 10:58:46 UTC] PHP Notice:  Undefined variable: wpcloudgallery_active_tab in /wp-content/plugins/wp-cloud-gallery/wpcl-apikey.php on line 19
[06-Apr-2020 10:58:46 UTC] PHP Notice:  Undefined variable: confirmSave in /wp-content/plugins/wp-cloud-gallery/wpcl-apikey.php on line 57
[06-Apr-2020 10:58:46 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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58:46 UTC] PHP Notice:  Undefined variable: wpcloudgallery_active_tab in /wp-content/plugins/wp-cloud-gallery/wpcl-apikey.php on line 18
[06-Apr-2020 10:58:46 UTC] PHP Notice:  Undefined variable: wpcloudgallery_active_tab in /wp-content/plugins/wp-cloud-gallery/wpcl-apikey.php on line 19
[06-Apr-2020 10:58: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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58: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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58:48 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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58:48 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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58:48 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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58: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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58: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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58: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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58: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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58: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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58: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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58: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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58: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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58:51 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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58:51 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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58:51 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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58: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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58: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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58: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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58: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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58: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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58: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://wordpress.org/support/article/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 5167
[06-Apr-2020 10:58: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://wordpress.org/support/article/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 5167
See also: All tests for this plugin, How to Hide WP Cloud Gallery Admin Menus