ACTUS Xfields 1.0.3

Does ACTUS Xfields work with WordPress 7.1 and PHP 8.1.12? A smoke test was performed on .

Summary

Errors
8PHP warnings
4PHP notices
No JavaScript exceptions
All test pages loaded successfully
No resource errors
Performance

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

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

Environment
WordPress version7.1
PHP version8.1.12
MySQL version10.6.10
PHP memory limit512M
Plugin Info
Last updated
Active installs <10
WordPress.org page https://wordpress.org/plugins/actus-xfields/
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=actus-xfields%2Factus-xfields.php&plugin_status=all&paged=1&s&_wpnonce=588311c17d
Aspect after-activation
HTTP status 200
Load time 0.930 s
Memory usage 4.35 MiB
JS errors None
Resource errors None

Test site

Page screenshot: Test site
URL /wp-admin/admin.php?page=actus-global-options
Aspect menu-item
HTTP status 200
Load time 0.805 s
Memory usage 4.3 MiB
JS errors None
Resource errors None

ACTUS

Page screenshot: ACTUS
URL /wp-admin/admin.php?page=actus-plugins
Aspect menu-item
HTTP status 200
Load time 0.642 s
Memory usage 4.3 MiB
JS errors None
Resource errors None

ACTUS → ACTUS Xfields

Page screenshot: ACTUS → ACTUS Xfields
URL /wp-admin/admin.php?page=actus-xfields
Aspect menu-item
HTTP status 200
Load time 0.650 s
Memory usage 4.32 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.252 s
Memory usage 4.62 MiB
JS errors None
Resource errors None

Dashboard ‹ Test site — WordPress

Page screenshot: Dashboard ‹ Test site — WordPress
URL /wp-admin/index.php
Aspect new-meta-boxes
HTTP status 200
Load time 1.003 s
Memory usage 4.31 MiB
JS errors None
Resource errors None

Add Post ‹ Test site — WordPress

Page screenshot: Add Post ‹ Test site — WordPress
URL /wp-admin/post-new.php
Aspect new-meta-boxes
HTTP status 200
Load time 1.750 s
Memory usage 6.89 MiB
JS errors None
Resource errors None

Add Page ‹ Test site — WordPress

Page screenshot: Add Page ‹ Test site — WordPress
URL /wp-admin/post-new.php?post_type=page
Aspect new-meta-boxes
HTTP status 200
Load time 1.821 s
Memory usage 6.86 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php1.303 s0.800 s-0.503 s4.23 MiB4.31 MiB+ 90.35 KiB
/wp-admin/edit.php0.516 s0.593 s+0.077 s4.28 MiB4.38 MiB+ 96.01 KiB
/wp-admin/post-new.php2.016 s1.794 s-0.222 s6.78 MiB6.89 MiB+ 109.33 KiB
/wp-admin/upload.php0.958 s0.981 s+0.023 s4.25 MiB4.3 MiB+ 58.7 KiB
/wp-admin/options-writing.php0.541 s1.093 s+0.552 s4.22 MiB4.3 MiB+ 82.12 KiB
/wp-admin/media-new.php0.557 s0.616 s+0.059 s4.21 MiB4.3 MiB+ 90.32 KiB
/wp-admin/edit-tags.php?taxonomy=category0.766 s0.565 s-0.201 s4.22 MiB4.32 MiB+ 95.18 KiB
/wp-admin/post-new.php?post_type=page1.614 s1.856 s+0.242 s6.76 MiB6.86 MiB+ 100.98 KiB
/wp-admin/options-discussion.php0.724 s1.018 s+0.294 s4.23 MiB4.3 MiB+ 74.63 KiB
/wp-admin/edit-comments.php0.515 s0.617 s+0.102 s4.24 MiB4.32 MiB+ 78.13 KiB
/0.282 s0.191 s-0.091 s4.6 MiB4.62 MiB+ 14.79 KiB
Average 0.890 s0.920 s+0.030 s4.73 MiB4.81 MiB+ 80.96 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.

JavaScript
CSS
PHP
Language % Lines of code Comment lines Files
JavaScript41.0%1,8391422
CSS38.2%1,714632
PHP20.7%9291586
Total 4,482 363 10

PHP Code Analysis | More results »

Lines of code 924
Total complexity 164
Median class complexity 0.0
Median method complexity 0.0
Most complex class
Most complex function AXF_target_match()
Classes 0
Methods 0
Functions 27

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.

Options wp_options 1

Meta Boxes

{
    "dashboard": {
        "axf_meta": {
            "title": "Meta Box Title",
            "context": "advanced"
        }
    },
    "post": {
        "actus_fields": {
            "title": "ACTUS extra fields",
            "context": "normal"
        }
    },
    "page": {
        "actus_fields": {
            "title": "ACTUS extra fields",
            "context": "normal"
        }
    },
    "product": {
        "actus_fields": {
            "title": "ACTUS extra fields",
            "context": "normal"
        }
    }
}

PHP Error Log 12 lines

[08-Sep-2026 09:48:16 UTC] PHP Warning:  Attempt to read property "ID" on null in /wp-content/plugins/actus-xfields/includes/actus-xf-main.php on line 437
[08-Sep-2026 09:48:16 UTC] PHP Notice:  Function map_meta_cap was called <strong>incorrectly</strong>. When checking for the <code>edit_post</code> capability, you must always check it against a specific post. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.1.0.) in /wp-includes/functions.php on line 6260
[08-Sep-2026 09:48:16 UTC] PHP Warning:  Attempt to read property "ID" on null in /wp-content/plugins/actus-xfields/includes/actus-xf-main.php on line 438
[08-Sep-2026 09:48:22 UTC] PHP Warning:  Attempt to read property "ID" on null in /wp-content/plugins/actus-xfields/includes/actus-xf-main.php on line 437
[08-Sep-2026 09:48:22 UTC] PHP Notice:  Function map_meta_cap was called <strong>incorrectly</strong>. When checking for the <code>edit_post</code> capability, you must always check it against a specific post. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.1.0.) in /wp-includes/functions.php on line 6260
[08-Sep-2026 09:48:22 UTC] PHP Warning:  Attempt to read property "ID" on null in /wp-content/plugins/actus-xfields/includes/actus-xf-main.php on line 438
[08-Sep-2026 09:48:29 UTC] PHP Warning:  Attempt to read property "ID" on null in /wp-content/plugins/actus-xfields/includes/actus-xf-main.php on line 437
[08-Sep-2026 09:48:29 UTC] PHP Notice:  Function map_meta_cap was called <strong>incorrectly</strong>. When checking for the <code>edit_post</code> capability, you must always check it against a specific post. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.1.0.) in /wp-includes/functions.php on line 6260
[08-Sep-2026 09:48:29 UTC] PHP Warning:  Attempt to read property "ID" on null in /wp-content/plugins/actus-xfields/includes/actus-xf-main.php on line 438
[08-Sep-2026 09:48:33 UTC] PHP Warning:  Attempt to read property "ID" on null in /wp-content/plugins/actus-xfields/includes/actus-xf-main.php on line 437
[08-Sep-2026 09:48:33 UTC] PHP Notice:  Function map_meta_cap was called <strong>incorrectly</strong>. When checking for the <code>edit_post</code> capability, you must always check it against a specific post. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.1.0.) in /wp-includes/functions.php on line 6260
[08-Sep-2026 09:48:33 UTC] PHP Warning:  Attempt to read property "ID" on null in /wp-content/plugins/actus-xfields/includes/actus-xf-main.php on line 438
See also: All tests for this plugin, How to Hide ACTUS Xfields Admin Menus and More