WP Cloud Gallery 1.2

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

Summary

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

Memory usage: -1.88 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.3.2
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 23

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=2a0eecce64
Aspect after-activation
HTTP status 200
Load time 0.346 s
Memory usage 3.58 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 4.782 s
Memory usage 3.47 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 0.448 s
Memory usage 3.47 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.442 s
Memory usage 3.47 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.155 s
Memory usage 3.47 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.141 s
Memory usage 3.47 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.47 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.667 s
Memory usage 3.47 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.418 s
Memory usage 3.47 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.418 s
Memory usage 3.47 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.143 s
Memory usage 3.47 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.094 s
Memory usage 3.47 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 1.305 s
Memory usage 3.47 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.258 s
Memory usage 3.47 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.129 s
Memory usage 3.47 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 0.921 s
Memory usage 3.47 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.431 s
Memory usage 3.47 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.367 s
Memory usage 3.47 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.140 s
Memory usage 3.47 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.122 s
Memory usage 3.47 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.126 s
Memory usage 3.47 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.134 s
Memory usage 3.47 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.298 s
Memory usage 3.25 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.282 s0.221 s-0.061 s3.61 MiB3.63 MiB+ 13.34 KiB
/wp-admin/edit.php0.205 s0.312 s+0.107 s3.64 MiB3.66 MiB+ 13.34 KiB
/wp-admin/post-new.php1.128 s1.337 s+0.209 s5.36 MiB5.38 MiB+ 20.11 KiB
/wp-admin/upload.php0.497 s0.392 s-0.105 s3.48 MiB3.49 MiB+ 12.81 KiB
/wp-admin/options-writing.php0.153 s0.150 s-0.003 s3.56 MiB3.48 MiB- 80.63 KiB
/wp-admin/media-new.php0.208 s0.190 s-0.018 s3.46 MiB3.47 MiB+ 12.98 KiB
/wp-admin/edit-tags.php?taxonomy=category0.188 s0.159 s-0.029 s3.56 MiB3.58 MiB+ 13.89 KiB
/wp-admin/post-new.php?post_type=page1.156 s0.952 s-0.204 s5.35 MiB5.36 MiB+ 13.29 KiB
/wp-admin/options-discussion.php0.244 s0.490 s+0.246 s3.46 MiB3.48 MiB+ 13.3 KiB
/wp-admin/edit-comments.php0.206 s0.189 s-0.017 s3.57 MiB3.58 MiB+ 12.23 KiB
/0.302 s0.208 s-0.094 s3.32 MiB3.25 MiB- 65.34 KiB
Average 0.415 s0.418 s+0.003 s3.85 MiB3.85 MiB- 1.88 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 57 lines

[24-Dec-2019 06:53: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 4986
[24-Dec-2019 06:53: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 4986
[24-Dec-2019 06:53: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 4986
[24-Dec-2019 06:53: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://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 4986
[24-Dec-2019 06:53:59 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 4986
[24-Dec-2019 06:54: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://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 4986
[24-Dec-2019 06:54:00 UTC] PHP Notice:  Undefined variable: confirmSave in /wp-content/plugins/wp-cloud-gallery/wpcl-main.php on line 150
[24-Dec-2019 06:54: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://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 4986
[24-Dec-2019 06:54: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://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 4986
[24-Dec-2019 06:54: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://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 4986
[24-Dec-2019 06:54: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://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 4986
[24-Dec-2019 06:54: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://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 4986
[24-Dec-2019 06:54: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://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 4986
[24-Dec-2019 06:54: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://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 4986
[24-Dec-2019 06:54: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://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 4986
[24-Dec-2019 06:54:09 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 4986
[24-Dec-2019 06:54:10 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 4986
[24-Dec-2019 06:54:10 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 4986
[24-Dec-2019 06:54:12 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 4986
[24-Dec-2019 06:54:13 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 4986
[24-Dec-2019 06:54:14 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 4986
[24-Dec-2019 06:54:14 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 4986
[24-Dec-2019 06:54:14 UTC] PHP Notice:  Undefined variable: wpcloudgallery_active_tab in /wp-content/plugins/wp-cloud-gallery/wpcl-apikey.php on line 18
[24-Dec-2019 06:54:14 UTC] PHP Notice:  Undefined variable: wpcloudgallery_active_tab in /wp-content/plugins/wp-cloud-gallery/wpcl-apikey.php on line 19
[24-Dec-2019 06:54:14 UTC] PHP Notice:  Undefined variable: confirmSave in /wp-content/plugins/wp-cloud-gallery/wpcl-apikey.php on line 57
[24-Dec-2019 06:54:14 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 4986
[24-Dec-2019 06:54:14 UTC] PHP Notice:  Undefined variable: wpcloudgallery_active_tab in /wp-content/plugins/wp-cloud-gallery/wpcl-apikey.php on line 18
[24-Dec-2019 06:54:14 UTC] PHP Notice:  Undefined variable: wpcloudgallery_active_tab in /wp-content/plugins/wp-cloud-gallery/wpcl-apikey.php on line 19
[24-Dec-2019 06:54:14 UTC] PHP Notice:  Undefined variable: confirmSave in /wp-content/plugins/wp-cloud-gallery/wpcl-apikey.php on line 57
[24-Dec-2019 06:54:15 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 4986
[24-Dec-2019 06:54:15 UTC] PHP Notice:  Undefined variable: wpcloudgallery_active_tab in /wp-content/plugins/wp-cloud-gallery/wpcl-apikey.php on line 18
[24-Dec-2019 06:54:15 UTC] PHP Notice:  Undefined variable: wpcloudgallery_active_tab in /wp-content/plugins/wp-cloud-gallery/wpcl-apikey.php on line 19
[24-Dec-2019 06:54:15 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 4986
[24-Dec-2019 06:54:16 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 4986
[24-Dec-2019 06:54:16 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 4986
[24-Dec-2019 06:54:16 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 4986
[24-Dec-2019 06:54:17 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 4986
[24-Dec-2019 06:54:18 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 4986
[24-Dec-2019 06:54:18 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 4986
[24-Dec-2019 06:54:18 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 4986
[24-Dec-2019 06:54:18 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 4986
[24-Dec-2019 06:54:18 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 4986
[24-Dec-2019 06:54:18 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 4986
[24-Dec-2019 06:54:19 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 4986
[24-Dec-2019 06:54:19 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 4986
[24-Dec-2019 06:54:19 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 4986
[24-Dec-2019 06:54:19 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 4986
[24-Dec-2019 06:54: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 4986
[24-Dec-2019 06:54: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 4986
[24-Dec-2019 06:54: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 4986
[24-Dec-2019 06:54: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 4986
[24-Dec-2019 06:54: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 4986
[24-Dec-2019 06:54:21 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 4986
[24-Dec-2019 06:54:21 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 4986
[24-Dec-2019 06:54:21 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 4986
[24-Dec-2019 06:54:21 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 4986
[24-Dec-2019 06:54:22 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 4986
See also: All tests for this plugin, How to Hide WP Cloud Gallery Admin Menus