1. Home
2. Easy Google Adsense and Banner Ads Manager – AdsforWP
3. 1.9.21

Google Adsense & Banner Ads by AdsforWP 1.9.21

Does "Google Adsense & Banner Ads by AdsforWP" work with WordPress 6.0.1 and PHP 7.4.8? A smoke test was performed on 2022-07-15 04:12:54 UTC.

Summary

×

Badges

Image

HTML

Markdown

Image

HTML

Markdown

Close

Pages 11

Ads ‹ Test site — WordPress

URL	/wp-admin/edit.php?post_type=adsforwp
Requested URL	/wp-admin/plugins.php?action=activate&plugin=ads-for-wp%2Fads-for-wp.php&plugin_status=all&paged=1&s&_wpnonce=3b3a01724d
Aspect	after-activation
HTTP status	200
Load time	0.688 s
Memory usage	4.94 MiB
JS errors	None
Resource errors	None

Ads

URL	/wp-admin/edit.php?post_type=adsforwp
Aspect	menu-item
HTTP status	200
Load time	0.425 s
Memory usage	4.94 MiB
JS errors	None
Resource errors	None

Ads → Groups

URL	/wp-admin/edit.php?post_type=adsforwp-groups
Aspect	menu-item
HTTP status	200
Load time	0.529 s
Memory usage	4.94 MiB
JS errors	None
Resource errors	None

Ads → Settings

URL	/wp-admin/edit.php?post_type=adsforwp&page=adsforwp
Aspect	menu-item
HTTP status	200
Load time	0.332 s
Memory usage	4.88 MiB
JS errors	None
Resource errors	None

Ads → Settings → Tools

URL	/wp-admin/admin.php?page=adsforwp&tab=tools
Aspect	menu-item-tab
HTTP status	200
Load time	0.294 s
Memory usage	4.88 MiB
JS errors	None
Resource errors	None

Ads → Settings → Advanced

URL	/wp-admin/admin.php?page=adsforwp&tab=advance
Aspect	menu-item-tab
HTTP status	200
Load time	0.274 s
Memory usage	4.88 MiB
JS errors	None
Resource errors	None

Ads → Settings → Support

URL	/wp-admin/admin.php?page=adsforwp&tab=support
Aspect	menu-item-tab
HTTP status	200
Load time	0.246 s
Memory usage	4.88 MiB
JS errors	None
Resource errors	None

Ads → Analytics

URL	/wp-admin/edit.php?post_type=adsforwp&page=adsforwp-analytics
Aspect	menu-item
HTTP status	200
Load time	0.238 s
Memory usage	4.86 MiB
JS errors	None
Resource errors	None

Test site – Just another WordPress site

URL	/
Aspect	front-page
HTTP status	200
Load time	0.240 s
Memory usage	3.83 MiB
JS errors	None
Resource errors	None

Add New Post ‹ Test site — WordPress

URL	/wp-admin/post-new.php
Aspect	new-meta-boxes
HTTP status	200
Load time	0.769 s
Memory usage	6.63 MiB
JS errors	None
Resource errors	None

Widgets ‹ Test site — WordPress

URL	/wp-admin/widgets.php
Aspect	new-sidebar-widgets
HTTP status	200
Load time	2.101 s
Memory usage	6.59 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

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 Code Analysis | More results »

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

• wp_adsforwp_stats

Options wp_options 4

• adsforwp_activation_date
• adsforwp_ip_request_2022-07-15
• adsforwp-database-on-first-load
• widget_adsforwp_ads_widget

Custom Post Types 2

Sidebar Widgets 1

Meta Boxes

{
    "post": {
        "showadsforcurrentpag": {
            "title": "Show Ads for Current Page?",
            "context": "side"
        }
    },
    "adsforwp": {
        "adtype": {
            "title": "Ad Type",
            "context": "normal"
        },
        "display-metabox": {
            "title": "Display",
            "context": "normal"
        },
        "adsforwp_placement_metabox": {
            "title": "Advanced Display Conditions",
            "context": "normal"
        },
        "adsforwp_visitor_condition_metabox": {
            "title": "User Targeting",
            "context": "normal"
        },
        "setexpiredate": {
            "title": "Set Expire Date",
            "context": "side"
        },
        "adsforwp-location": {
            "title": "AMP",
            "context": "side"
        }
    },
    "adsforwp-groups": {
        "display-metabox": {
            "title": "Display",
            "context": "normal"
        },
        "adsforwp_placement_metabox": {
            "title": "Advanced Display Conditions",
            "context": "normal"
        },
        "adsforwp_visitor_condition_metabox": {
            "title": "User Targeting",
            "context": "normal"
        },
        "adgroup": {
            "title": "Ad Group",
            "context": "advanced"
        },
        "setexpiredate": {
            "title": "Set Expire Date",
            "context": "side"
        },
        "adsforwp-location": {
            "title": "AMP",
            "context": "side"
        }
    }
}

PHP Error Log 1 lines

[15-Jul-2022 04:13:31 UTC] PHP Notice:  Function wp_enqueue_script() was called <strong>incorrectly</strong>. "wp-editor" script should not be enqueued together with the new widgets editor (wp-edit-widgets or wp-customize-widgets). 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.8.0.) in /wp-includes/functions.php on line 5831