Countdown builder 2.4.5

Does Countdown builder work with WordPress 6.0.3 and PHP 7.4.8? A smoke test was performed on .

Summary

Errors
1PHP fatal errors
3PHP warnings
93PHP notices
No JavaScript exceptions
All test pages loaded successfully
No resource errors
Performance

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

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

Environment
WordPress version6.0.3
PHP version7.4.8
MySQL version8.0.21
PHP memory limit256M
Plugin Info
Last updated
Active installs 10,000+
WordPress.org page https://wordpress.org/plugins/countdown-builder/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 20

Countdown & Clock ‹ Test site — WordPress

Page screenshot: Countdown & Clock ‹ Test site — WordPress
URL /wp-admin/edit.php?post_type=ycdcountdown
Requested URL /wp-admin/plugins.php?action=activate&plugin=countdown-builder%2Fcountdown-builder.php&plugin_status=all&paged=1&s&_wpnonce=8a24a58eb4
Aspect after-activation
HTTP status 200
Load time 1.329 s
Memory usage 4.02 MiB
JS errors None
Resource errors None

Countdown & Clock

Page screenshot: Countdown & Clock
URL /wp-admin/edit.php?post_type=ycdcountdown
Aspect menu-item
HTTP status 200
Load time 0.488 s
Memory usage 4.02 MiB
JS errors None
Resource errors None

Countdown & Clock → Add New

Page screenshot: Countdown & Clock → Add New
URL /wp-admin/post-new.php?post_type=ycdcountdown
Aspect menu-item
HTTP status 200
Load time 1.644 s
Memory usage 4.7 MiB
JS errors None
Resource errors None

Countdown & Clock → Countdown Types

Page screenshot: Countdown & Clock → Countdown Types
URL /wp-admin/edit.php?post_type=ycdcountdown&page=ycdcountdown
Aspect menu-item
HTTP status 200
Load time 0.745 s
Memory usage 3.97 MiB
JS errors None
Resource errors None

Countdown & Clock → Countdown Types → Countdown

Page screenshot: Countdown & Clock → Countdown Types → Countdown
URL /wp-admin/edit.php?post_type=ycdcountdown&page=ycdcountdown&ycd_group_name=countdown
Aspect menu-item-tab
HTTP status 200
Load time 0.345 s
Memory usage 3.92 MiB
JS errors None
Resource errors None

Countdown & Clock → Countdown Types → Clock

Page screenshot: Countdown & Clock → Countdown Types → Clock
URL /wp-admin/edit.php?post_type=ycdcountdown&page=ycdcountdown&ycd_group_name=clock
Aspect menu-item-tab
HTTP status 200
Load time 0.465 s
Memory usage 3.92 MiB
JS errors None
Resource errors None

Countdown & Clock → Countdown Types → Other

Page screenshot: Countdown & Clock → Countdown Types → Other
URL /wp-admin/edit.php?post_type=ycdcountdown&page=ycdcountdown&ycd_group_name=other
Aspect menu-item-tab
HTTP status 200
Load time 0.344 s
Memory usage 3.92 MiB
JS errors None
Resource errors None

Countdown & Clock → Countdown Types → Timer

Page screenshot: Countdown & Clock → Countdown Types → Timer
URL /wp-admin/edit.php?post_type=ycdcountdown&page=ycdcountdown&ycd_group_name=timer
Aspect menu-item-tab
HTTP status 200
Load time 0.557 s
Memory usage 3.92 MiB
JS errors None
Resource errors None

Countdown & Clock → Countdown Types → Popup

Page screenshot: Countdown & Clock → Countdown Types → Popup
URL /wp-admin/edit.php?post_type=ycdcountdown&page=ycdcountdown&ycd_group_name=popup
Aspect menu-item-tab
HTTP status 200
Load time 0.343 s
Memory usage 3.92 MiB
JS errors None
Resource errors None

Countdown & Clock → Newsletter Pro

Page screenshot: Countdown & Clock → Newsletter Pro
URL /wp-admin/edit.php?post_type=ycdcountdown&page=ycdNewsletter
Aspect menu-item
HTTP status 200
Load time 0.263 s
Memory usage 3.92 MiB
JS errors None
Resource errors None

Countdown & Clock → Coming Soon

Page screenshot: Countdown & Clock → Coming Soon
URL /wp-admin/edit.php?post_type=ycdcountdown&page=ycdComingSoon
Aspect menu-item
HTTP status 200
Load time 1.087 s
Memory usage 4.14 MiB
JS errors None
Resource errors None

Countdown & Clock → Support

Page screenshot: Countdown & Clock → Support
URL /wp-admin/edit.php?post_type=ycdcountdown&page=supports
Aspect menu-item
HTTP status 200
Load time 0.504 s
Memory usage 3.97 MiB
JS errors None
Resource errors None

Countdown & Clock → Tutorials

Page screenshot: Countdown & Clock → Tutorials
URL /wp-admin/edit.php?post_type=ycdcountdown&page=ycdTutorials
Aspect menu-item
HTTP status 200
Load time 11.132 s
Memory usage 3.95 MiB
JS errors None
Resource errors None

Countdown & Clock → More Ideas?

Page screenshot: Countdown & Clock → More Ideas?
URL /wp-admin/edit.php?post_type=ycdcountdown&page=ycdIdeas
Aspect menu-item
HTTP status 200
Load time 1.388 s
Memory usage 3.92 MiB
JS errors None
Resource errors None

Countdown & Clock → Subscribers Pro

Page screenshot: Countdown & Clock → Subscribers Pro
URL /wp-admin/edit.php?post_type=ycdcountdown&page=ycdSubscribers
Aspect menu-item
HTTP status 200
Load time 0.371 s
Memory usage N/A
JS errors None
Resource errors None

Countdown & Clock → More Plugins

Page screenshot: Countdown & Clock → More Plugins
URL /wp-admin/edit.php?post_type=ycdcountdown&page=ycdPlugins
Aspect menu-item
HTTP status 200
Load time 0.362 s
Memory usage 3.96 MiB
JS errors None
Resource errors None

Countdown & Clock → Settings

Page screenshot: Countdown & Clock → Settings
URL /wp-admin/edit.php?post_type=ycdcountdown&page=ycdSettings
Aspect menu-item
HTTP status 200
Load time 0.275 s
Memory usage 3.98 MiB
JS errors None
Resource errors None

Coming Soon

Page screenshot: Coming Soon
URL /wp-admin/admin.php?page=ycdComingSoon
Aspect menu-item
HTTP status 200
Load time 0.955 s
Memory usage 4.13 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.285 s
Memory usage 3.78 MiB
JS errors None
Resource errors None

Widgets ‹ Test site — WordPress

Page screenshot: Widgets ‹ Test site — WordPress
URL /wp-admin/widgets.php
Aspect new-sidebar-widgets
HTTP status 200
Load time 2.112 s
Memory usage 5.77 MiB
JS errors
External errors: The following JavaScript errors were probably triggered by WordPress itself, or by compatibility issues in the test runner. They are not related to the plugin.
[
    {
        "message": "TypeError: Cannot read properties of null (reading 'offsetHeight')\n    at t (/wp-includes/js/dist/widgets.min.js?ver=80e98954519d1dad7a91a2248dbc2cc9:7:10419)\n    at IntersectionObserver.n.threshold (/wp-includes/js/dist/widgets.min.js?ver=80e98954519d1dad7a91a2248dbc2cc9:7:10591)",
        "trace": null,
        "code": null
    }
]
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.374 s0.409 s+0.035 s3.73 MiB3.98 MiB+ 256.52 KiB
/wp-admin/edit.php0.219 s0.238 s+0.019 s3.76 MiB4.01 MiB+ 249.55 KiB
/wp-admin/post-new.php1.158 s1.370 s+0.212 s5.55 MiB5.82 MiB+ 272.48 KiB
/wp-admin/upload.php0.467 s0.431 s-0.036 s3.69 MiB3.93 MiB+ 251.59 KiB
/wp-admin/options-writing.php0.310 s0.168 s-0.142 s3.62 MiB3.91 MiB+ 294.88 KiB
/wp-admin/media-new.php0.297 s0.226 s-0.071 s3.67 MiB3.91 MiB+ 251.77 KiB
/wp-admin/edit-tags.php?taxonomy=category0.198 s0.216 s+0.018 s3.69 MiB3.94 MiB+ 252.71 KiB
/wp-admin/post-new.php?post_type=page0.971 s1.631 s+0.660 s5.55 MiB5.82 MiB+ 277.34 KiB
/wp-admin/options-discussion.php0.237 s0.317 s+0.080 s3.6 MiB3.91 MiB+ 315.45 KiB
/wp-admin/edit-comments.php0.233 s0.249 s+0.016 s3.7 MiB3.94 MiB+ 250.27 KiB
/0.316 s0.240 s-0.076 s3.57 MiB3.78 MiB+ 219.27 KiB
Average 0.435 s0.500 s+0.065 s4.01 MiB4.27 MiB+ 262.89 KiB

Code Statistics

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

PHP
JavaScript
CSS
Language % Lines of code Comment lines Files
PHP44.8%11,40127680
JavaScript40.1%10,21551319
CSS15.1%3,8523010
SVG0.0%101
Total 25,469 819 110

PHP Code Analysis | More results »

Lines of code 6,794
Total complexity 951
Median class complexity 16.0
Median method complexity 1.0
Most complex class ycd\Countdown
Most complex function ycd\AdminHelper::defaultData()
Classes 37
Methods 467
Functions 0

Additions

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

Database Tables 1

Options wp_options 6

Custom Post Types 1

ID Name
ycdcountdownCountdown & Clock

Sidebar Widgets 1

ID Name
ycd_countdown_widgetCountdown & Clock

Meta Boxes

{
    "ycdcountdown": {
        "ycdFeatureRequest": {
            "title": "Feature Request",
            "context": "side"
        },
        "ycdUpgrade": {
            "title": "Upgrade",
            "context": "side"
        },
        "ycdSupport": {
            "title": "Support",
            "context": "side"
        },
        "ycdShortcodeMetabox": {
            "title": "Info",
            "context": "side"
        },
        "advancedOptions": {
            "title": "Advanced Options",
            "context": "normal"
        },
        "displayRules": {
            "title": "Display Rules",
            "context": "normal"
        },
        "generalOptions": {
            "title": "General Options",
            "context": "normal"
        },
        "subscription": {
            "title": "Subscription Section",
            "context": "normal"
        },
        "afterCountdownExpire": {
            "title": "After Expire",
            "context": "normal"
        },
        "countdownButton": {
            "title": "Countdown Button Extension",
            "context": "normal"
        },
        "ycdMetaboxProgress": {
            "title": "Progress Bar",
            "context": "normal"
        },
        "ycdMainOptions": {
            "title": "Countdown options",
            "context": "normal"
        }
    }
}

Capabilities 13

PHP Error Log 97 lines

[18-Oct-2022 17:10:47 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:10:47 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:10:49 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:10:49 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:10:50 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:10:50 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:10:51 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:10:51 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:10:51 UTC] PHP Notice:  Undefined index: idAndDates in /wp-content/plugins/countdown-builder/assets/views/generalOptions.php on line 64
[18-Oct-2022 17:10:51 UTC] PHP Notice:  Trying to access array offset on value of type null in /wp-content/plugins/countdown-builder/assets/views/generalOptions.php on line 64
[18-Oct-2022 17:10:51 UTC] PHP Notice:  Undefined index: language in /wp-content/plugins/countdown-builder/classes/translation/AbstractTranslationManager.php on line 56
[18-Oct-2022 17:10:51 UTC] PHP Notice:  Undefined index: Years in /wp-content/plugins/countdown-builder/classes/translation/AbstractTranslationManager.php on line 64
[18-Oct-2022 17:10:51 UTC] PHP Notice:  Undefined index: Months in /wp-content/plugins/countdown-builder/classes/translation/AbstractTranslationManager.php on line 64
[18-Oct-2022 17:10:51 UTC] PHP Notice:  Undefined index: Days in /wp-content/plugins/countdown-builder/classes/translation/AbstractTranslationManager.php on line 64
[18-Oct-2022 17:10:51 UTC] PHP Notice:  Undefined index: Hours in /wp-content/plugins/countdown-builder/classes/translation/AbstractTranslationManager.php on line 64
[18-Oct-2022 17:10:51 UTC] PHP Notice:  Undefined index: Minutes in /wp-content/plugins/countdown-builder/classes/translation/AbstractTranslationManager.php on line 64
[18-Oct-2022 17:10:51 UTC] PHP Notice:  Undefined index: Seconds in /wp-content/plugins/countdown-builder/classes/translation/AbstractTranslationManager.php on line 64
[18-Oct-2022 17:10:52 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:10:52 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:10:52 UTC] PHP Notice:  Undefined index: idAndDates in /wp-content/plugins/countdown-builder/assets/views/generalOptions.php on line 64
[18-Oct-2022 17:10:52 UTC] PHP Notice:  Trying to access array offset on value of type null in /wp-content/plugins/countdown-builder/assets/views/generalOptions.php on line 64
[18-Oct-2022 17:10:52 UTC] PHP Notice:  Undefined index: language in /wp-content/plugins/countdown-builder/classes/translation/AbstractTranslationManager.php on line 56
[18-Oct-2022 17:10:52 UTC] PHP Notice:  Undefined index: Years in /wp-content/plugins/countdown-builder/classes/translation/AbstractTranslationManager.php on line 64
[18-Oct-2022 17:10:52 UTC] PHP Notice:  Undefined index: Months in /wp-content/plugins/countdown-builder/classes/translation/AbstractTranslationManager.php on line 64
[18-Oct-2022 17:10:52 UTC] PHP Notice:  Undefined index: Days in /wp-content/plugins/countdown-builder/classes/translation/AbstractTranslationManager.php on line 64
[18-Oct-2022 17:10:52 UTC] PHP Notice:  Undefined index: Hours in /wp-content/plugins/countdown-builder/classes/translation/AbstractTranslationManager.php on line 64
[18-Oct-2022 17:10:52 UTC] PHP Notice:  Undefined index: Minutes in /wp-content/plugins/countdown-builder/classes/translation/AbstractTranslationManager.php on line 64
[18-Oct-2022 17:10:52 UTC] PHP Notice:  Undefined index: Seconds in /wp-content/plugins/countdown-builder/classes/translation/AbstractTranslationManager.php on line 64
[18-Oct-2022 17:10:57 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:10:57 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:10:58 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:10:58 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:10:59 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:10:59 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:11:00 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:11:00 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:11:01 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:11:01 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:11:03 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:11:03 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:11:04 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:11:04 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:11:04 UTC] PHP Warning:  Cannot modify header information - headers already sent by (output started at /wp-includes/script-loader.php:2750) in /wp-includes/pluggable.php on line 1416
[18-Oct-2022 17:11:04 UTC] PHP Warning:  Cannot modify header information - headers already sent by (output started at /wp-includes/script-loader.php:2750) in /wp-includes/pluggable.php on line 1419
[18-Oct-2022 17:11:05 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:11:05 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:11:07 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:11:07 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:11:08 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:11:08 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:11:22 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:11:22 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:11:24 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:11:24 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:11:24 UTC] PHP Warning:  require_once(/wp-content/plugins/countdown-builder//assets/views/subscribers.php): failed to open stream: No such file or directory in /wp-content/plugins/countdown-builder/classes/RegisterPostType.php on line 242
[18-Oct-2022 17:11:24 UTC] PHP Fatal error:  require_once(): Failed opening required '/wp-content/plugins/countdown-builder//assets/views/subscribers.php' (include_path='.:/opt/bitnami/php/lib/php') in /wp-content/plugins/countdown-builder/classes/RegisterPostType.php on line 242
[18-Oct-2022 17:11:25 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:11:25 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:11:26 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:11:26 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:11:27 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:11:27 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:11:30 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:11:30 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:11:30 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:11:30 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:11:31 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:11:31 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:11:33 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:11:33 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:11:34 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:11:34 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:11:34 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:11:34 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:11:34 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:11:34 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:11:35 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:11:35 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:11:38 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:11:38 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:11:38 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:11:38 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:11:39 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:11:39 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:11:39 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:11:39 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
[18-Oct-2022 17:11:43 UTC] PHP Notice:  Trying to get property 'ID' of non-object in /wp-content/plugins/countdown-builder/classes/DisplayRuleChecker.php on line 54
[18-Oct-2022 17:11:43 UTC] PHP Notice:  Trying to get property 'ID' of non-object in /wp-content/plugins/countdown-builder/classes/DisplayRuleChecker.php on line 54
[18-Oct-2022 17:11:43 UTC] PHP Notice:  Trying to get property 'ID' of non-object in /wp-content/plugins/countdown-builder/classes/DisplayRuleChecker.php on line 54
[18-Oct-2022 17:11:44 UTC] PHP Notice:  Trying to get property 'ID' of non-object in /wp-content/plugins/countdown-builder/classes/DisplayRuleChecker.php on line 54
[18-Oct-2022 17:11:44 UTC] PHP Notice:  Trying to get property 'ID' of non-object in /wp-content/plugins/countdown-builder/classes/DisplayRuleChecker.php on line 54
[18-Oct-2022 17:11:44 UTC] PHP Notice:  Trying to get property 'ID' of non-object in /wp-content/plugins/countdown-builder/classes/DisplayRuleChecker.php on line 54
[18-Oct-2022 17:11:44 UTC] PHP Notice:  Trying to get property 'ID' of non-object in /wp-content/plugins/countdown-builder/classes/DisplayRuleChecker.php on line 54
[18-Oct-2022 17:11:44 UTC] PHP Notice:  Trying to get property 'ID' of non-object in /wp-content/plugins/countdown-builder/classes/DisplayRuleChecker.php on line 54
[18-Oct-2022 17:11:44 UTC] PHP Notice:  Trying to get property 'ID' of non-object in /wp-content/plugins/countdown-builder/classes/DisplayRuleChecker.php on line 54
[18-Oct-2022 17:11:46 UTC] PHP Notice:  Array to string conversion in /wp-includes/formatting.php on line 1098
[18-Oct-2022 17:11:46 UTC] PHP Notice:  Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5833
See also: All tests for this plugin, How to Hide Countdown builder Admin Menus and Meta Boxes