Popup Builder 3.77

Does Popup Builder work with WordPress 5.7 and PHP 7.4.8? A smoke test was performed on .

Summary

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

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

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

Environment
WordPress version5.7
PHP version7.4.8
MySQL version8.0.21
PHP memory limit256M
Plugin Info
Last updated
Active installs 200,000+
WordPress.org page https://wordpress.org/plugins/popup-builder/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 8

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=popup-builder%2Fpopup-builder.php&plugin_status=all&paged=1&s&_wpnonce=a0c9f2f6c1
Aspect after-activation
HTTP status 200
Load time 1.377 s
Memory usage 3.59 MiB
JS errors None
Resource errors None

Popup Builder0

Page screenshot: Popup Builder0
URL /wp-admin/edit.php?post_type=popupbuilder
Aspect menu-item
HTTP status 200
Load time 0.535 s
Memory usage 3.24 MiB
JS errors None
Resource errors None

Popup Builder0 → Categories

Page screenshot: Popup Builder0 → Categories
URL /wp-admin/edit-tags.php?taxonomy=popup-categories&post_type=popupbuilder
Aspect menu-item
HTTP status 200
Load time 0.323 s
Memory usage 3.17 MiB
JS errors None
Resource errors None

Popup Builder0 → Add New

Page screenshot: Popup Builder0 → Add New
URL /wp-admin/edit.php?post_type=popupbuilder&page=popupbuilder
Aspect menu-item
HTTP status 200
Load time 0.614 s
Memory usage 3.2 MiB
JS errors None
Resource errors None

Popup Builder0 → All Subscribers

Page screenshot: Popup Builder0 → All Subscribers
URL /wp-admin/edit.php?post_type=popupbuilder&page=sgpbSubscribers
Aspect menu-item
HTTP status 200
Load time 0.498 s
Memory usage 3.21 MiB
JS errors None
Resource errors None

Popup Builder0 → Newsletter

Page screenshot: Popup Builder0 → Newsletter
URL /wp-admin/edit.php?post_type=popupbuilder&page=sgpbNewsletter
Aspect menu-item
HTTP status 200
Load time 0.948 s
Memory usage 3.21 MiB
JS errors None
Resource errors None

Popup Builder0 → Settings

Page screenshot: Popup Builder0 → Settings
URL /wp-admin/edit.php?post_type=popupbuilder&page=sgpbSettings
Aspect menu-item
HTTP status 200
Load time 0.498 s
Memory usage 3.19 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.230 s
Memory usage 2.97 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.269 s0.475 s+0.206 s2.82 MiB3.28 MiB+ 473.86 KiB
/wp-admin/edit.php0.182 s0.617 s+0.435 s2.86 MiB3.32 MiB+ 465.4 KiB
/wp-admin/post-new.php0.952 s1.685 s+0.733 s5.02 MiB5.69 MiB+ 683.53 KiB
/wp-admin/upload.php0.508 s0.496 s-0.012 s2.7 MiB3.14 MiB+ 455.02 KiB
/wp-admin/options-writing.php0.256 s0.289 s+0.033 s2.71 MiB3.14 MiB+ 444.8 KiB
/wp-admin/media-new.php0.220 s0.583 s+0.363 s2.67 MiB3.14 MiB+ 483.74 KiB
/wp-admin/edit-tags.php?taxonomy=category0.188 s0.339 s+0.151 s2.77 MiB3.18 MiB+ 418.49 KiB
/wp-admin/post-new.php?post_type=page1.253 s0.893 s-0.360 s5.01 MiB5.68 MiB+ 688.49 KiB
/wp-admin/options-discussion.php0.310 s0.358 s+0.048 s2.67 MiB3.14 MiB+ 480.85 KiB
/wp-admin/edit-comments.php0.227 s0.471 s+0.244 s2.78 MiB3.24 MiB+ 479.65 KiB
/0.273 s0.269 s-0.004 s2.71 MiB2.97 MiB+ 270.16 KiB
Average 0.422 s0.589 s+0.167 s3.16 MiB3.63 MiB+ 485.82 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
Language % Lines of code Comment lines Files
PHP77.1%19,8341,93181
JavaScript12.5%3,2149915
CSS7.2%1,84706
SVG2.5%64203
HTML0.8%197111
Total 25,734 2,041 106

PHP Code Analysis | More results »

Lines of code 16,552
Total complexity 3,166
Median class complexity 32.0
Median method complexity 2.0
Most complex class sgpb\AdminHelper
Most complex function sgpb\WP_Import::process_posts()
Classes 51
Methods 825
Functions 1

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 2

Options wp_options 9

Custom Post Types 1

ID Name
popupbuilderPopup Builder

Meta Boxes

{
    "popupbuilder": {
        "targetMetaboxView": {
            "title": "Popup Display Rules",
            "context": "normal"
        },
        "eventsMetaboxView": {
            "title": "Popup Events",
            "context": "normal"
        },
        "conditionsMetaboxView": {
            "title": "Popup Conditions",
            "context": "normal"
        },
        "behaviorAfterSpecialEventsMetaboxView": {
            "title": "Behavior After Special Events",
            "context": "normal"
        },
        "popupDesignMetaBoxView": {
            "title": "Design",
            "context": "normal"
        },
        "closeSettings": {
            "title": "Close Settings",
            "context": "normal"
        },
        "spgdimension": {
            "title": "Dimensions",
            "context": "normal"
        },
        "optionsMetaboxView": {
            "title": "Popup Options",
            "context": "normal"
        },
        "otherConditionsMetaBoxView": {
            "title": "Popup Additional ConditionsUNLOCK OPTION",
            "context": "normal"
        },
        "customCssJs": {
            "title": "Custom JS or CSS",
            "context": "normal"
        },
        "floatingButton": {
            "title": "Floating Button",
            "context": "side"
        },
        "popupOpeningCounter": {
            "title": "Popup statistics",
            "context": "side"
        }
    }
}

Capabilities 15

PHP Error Log 27 lines

[09-Mar-2021 22:24:57 UTC] PHP Notice:  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 5313
[09-Mar-2021 22:24:58 UTC] PHP Notice:  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 5313
[09-Mar-2021 22:24:58 UTC] PHP Notice:  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 5313
[09-Mar-2021 22:24:58 UTC] PHP Notice:  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 5313
[09-Mar-2021 22:24:59 UTC] PHP Notice:  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 5313
[09-Mar-2021 22:25:00 UTC] PHP Notice:  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 5313
[09-Mar-2021 22:25:00 UTC] PHP Notice:  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 5313
[09-Mar-2021 22:25:01 UTC] PHP Notice:  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 5313
[09-Mar-2021 22:25:02 UTC] PHP Notice:  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 5313
[09-Mar-2021 22:25:02 UTC] PHP Notice:  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 5313
[09-Mar-2021 22:25:02 UTC] PHP Notice:  Trying to access array offset on value of type bool in /wp-content/plugins/popup-builder/public/views/newsletter.php on line 90
[09-Mar-2021 22:25:03 UTC] PHP Notice:  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 5313
[09-Mar-2021 22:25:03 UTC] PHP Notice:  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 5313
[09-Mar-2021 22:25:04 UTC] PHP Notice:  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 5313
[09-Mar-2021 22:25:05 UTC] PHP Notice:  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 5313
[09-Mar-2021 22:25:06 UTC] PHP Notice:  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 5313
[09-Mar-2021 22:25:06 UTC] PHP Notice:  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 5313
[09-Mar-2021 22:25:08 UTC] PHP Notice:  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 5313
[09-Mar-2021 22:25:09 UTC] PHP Notice:  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 5313
[09-Mar-2021 22:25:09 UTC] PHP Notice:  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 5313
[09-Mar-2021 22:25:10 UTC] PHP Notice:  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 5313
[09-Mar-2021 22:25:11 UTC] PHP Notice:  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 5313
[09-Mar-2021 22:25:11 UTC] PHP Notice:  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 5313
[09-Mar-2021 22:25:12 UTC] PHP Notice:  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 5313
[09-Mar-2021 22:25:13 UTC] PHP Notice:  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 5313
[09-Mar-2021 22:25:13 UTC] PHP Notice:  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 5313
[09-Mar-2021 22:25:14 UTC] PHP Notice:  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 5313
See also: All tests for this plugin, How to Hide Popup Builder Admin Menus and Meta Boxes