onOffice for WP-Websites 6.5.1

Does onOffice for WP-Websites work with WordPress 6.8.3 and PHP 8.1.12? A smoke test was performed on .

Summary

Errors
22PHP notices
No JavaScript exceptions
3Pages failed to load
  • 3 500 Internal Server Error
No resource errors
Performance

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

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

Environment
WordPress version6.8.3
PHP version8.1.12
MySQL version10.6.10
PHP memory limit512M
Plugin Info
Last updated
Active installs 1,000+
WordPress.org page https://wordpress.org/plugins/onoffice-for-wp-websites/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 11

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=onoffice-for-wp-websites%2Fplugin.php&plugin_status=all&paged=1&s&_wpnonce=265c763a70
Aspect after-activation
HTTP status 200
Load time 4.858 s
Memory usage 4.37 MiB
JS errors None
Resource errors None

onOffice

Page screenshot: onOffice
URL /wp-admin/admin.php?page=onoffice
Aspect menu-item
HTTP status 200
Load time 1.977 s
Memory usage 4.04 MiB
JS errors None
Resource errors None

onOffice → Addresses

Page screenshot: onOffice → Addresses
URL /wp-admin/admin.php?page=onoffice-addresses
Aspect menu-item
HTTP status 200
Load time 1.982 s
Memory usage 4.07 MiB
JS errors None
Resource errors None

onOffice → Addresses → Detail View

Page screenshot: onOffice → Addresses → Detail View
URL /wp-admin/admin.php?page=onoffice-addresses&tab=detail
Aspect menu-item-tab
HTTP status 500
Load time 1.135 s
Memory usage N/A
JS errors None
Resource errors None

onOffice → Estates

Page screenshot: onOffice → Estates
URL /wp-admin/admin.php?page=onoffice-estates
Aspect menu-item
HTTP status 200
Load time 1.975 s
Memory usage 4.04 MiB
JS errors None
Resource errors None

onOffice → Estates → Detail View

Page screenshot: onOffice → Estates → Detail View
URL /wp-admin/admin.php?page=onoffice-estates&tab=detail
Aspect menu-item-tab
HTTP status 500
Load time 1.126 s
Memory usage N/A
JS errors None
Resource errors None

onOffice → Estates → Similar Estates

Page screenshot: onOffice → Estates → Similar Estates
URL /wp-admin/admin.php?page=onoffice-estates&tab=similar-estates
Aspect menu-item-tab
HTTP status 500
Load time 1.519 s
Memory usage N/A
JS errors None
Resource errors None

onOffice → Estates → Unit Lists

Page screenshot: onOffice → Estates → Unit Lists
URL /wp-admin/admin.php?page=onoffice-estates&tab=units
Aspect menu-item-tab
HTTP status 200
Load time 1.960 s
Memory usage 4.03 MiB
JS errors None
Resource errors None

onOffice → Forms

Page screenshot: onOffice → Forms
URL /wp-admin/admin.php?page=onoffice-forms
Aspect menu-item
HTTP status 200
Load time 1.951 s
Memory usage 4.03 MiB
JS errors None
Resource errors None

onOffice → Settings

Page screenshot: onOffice → Settings
URL /wp-admin/admin.php?page=onoffice-settings
Aspect menu-item
HTTP status 200
Load time 3.792 s
Memory usage 4.23 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 1.094 s
Memory usage 3.71 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.348 s2.199 s+1.851 s3.51 MiB4.09 MiB+ 596.6 KiB
/wp-admin/edit.php0.210 s2.007 s+1.797 s3.57 MiB4.12 MiB+ 557.46 KiB
/wp-admin/post-new.php0.820 s2.934 s+2.114 s6.06 MiB6.61 MiB+ 566.42 KiB
/wp-admin/upload.php0.590 s2.204 s+1.614 s3.52 MiB4.04 MiB+ 527.97 KiB
/wp-admin/options-writing.php0.228 s2.008 s+1.780 s3.5 MiB4.02 MiB+ 535.81 KiB
/wp-admin/media-new.php0.349 s2.051 s+1.702 s3.49 MiB4.03 MiB+ 546.15 KiB
/wp-admin/edit-tags.php?taxonomy=category0.222 s1.973 s+1.751 s3.5 MiB4.04 MiB+ 551.34 KiB
/wp-admin/post-new.php?post_type=page0.618 s2.388 s+1.770 s6.05 MiB6.6 MiB+ 566.29 KiB
/wp-admin/options-discussion.php0.280 s2.103 s+1.823 s3.5 MiB4.02 MiB+ 529.97 KiB
/wp-admin/edit-comments.php0.407 s2.016 s+1.609 s3.52 MiB4.05 MiB+ 537.81 KiB
/0.342 s1.007 s+0.665 s3.43 MiB3.7 MiB+ 276.16 KiB
Average 0.401 s2.081 s+1.680 s3.97 MiB4.48 MiB+ 526.54 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
PO File
Language % Lines of code Comment lines Files
PHP65.2%39,38424,426482
PO File26.1%15,7685,98814
JavaScript5.2%3,1162631
CSS3.3%2,005197
JSON0.1%7203
Markdown0.1%5902
HTML0.1%3101
SVG0.0%1001
Total 60,445 30,459 541

PHP Code Analysis | More results »

Lines of code 37,520
Total complexity 5,678
Median class complexity 7.0
Median method complexity 1.0
Most complex class onOffice\WPlugin\EstateList
Most complex function onOffice\SDK\internal\ApiCall::filterRecords()
Classes 405
Methods 2,895
Functions 15

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 22

Options wp_options 10

Capabilities 7

PHP Error Log 22 lines

[03-Oct-2025 12:12:34 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>onoffice-for-wp-websites</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. 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.7.0.) in /wp-includes/functions.php on line 6121
[03-Oct-2025 12:12:38 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. 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 3.9.0.) in /wp-includes/functions.php on line 6121
[03-Oct-2025 12:12:41 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. 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 3.9.0.) in /wp-includes/functions.php on line 6121
[03-Oct-2025 12:12:43 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. 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 3.9.0.) in /wp-includes/functions.php on line 6121
[03-Oct-2025 12:12:46 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. 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 3.9.0.) in /wp-includes/functions.php on line 6121
[03-Oct-2025 12:12:50 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. 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 3.9.0.) in /wp-includes/functions.php on line 6121
[03-Oct-2025 12:12:57 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. 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 3.9.0.) in /wp-includes/functions.php on line 6121
[03-Oct-2025 12:12:59 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. 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 3.9.0.) in /wp-includes/functions.php on line 6121
[03-Oct-2025 12:12:59 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. 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 3.9.0.) in /wp-includes/functions.php on line 6121
[03-Oct-2025 12:13:02 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. 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 3.9.0.) in /wp-includes/functions.php on line 6121
[03-Oct-2025 12:13:08 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. 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 3.9.0.) in /wp-includes/functions.php on line 6121
[03-Oct-2025 12:13:11 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. 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 3.9.0.) in /wp-includes/functions.php on line 6121
[03-Oct-2025 12:13:13 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. 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 3.9.0.) in /wp-includes/functions.php on line 6121
[03-Oct-2025 12:13:17 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. 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 3.9.0.) in /wp-includes/functions.php on line 6121
[03-Oct-2025 12:13:19 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. 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 3.9.0.) in /wp-includes/functions.php on line 6121
[03-Oct-2025 12:13:21 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. 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 3.9.0.) in /wp-includes/functions.php on line 6121
[03-Oct-2025 12:13:23 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. 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 3.9.0.) in /wp-includes/functions.php on line 6121
[03-Oct-2025 12:13:26 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. 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 3.9.0.) in /wp-includes/functions.php on line 6121
[03-Oct-2025 12:13:29 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. 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 3.9.0.) in /wp-includes/functions.php on line 6121
[03-Oct-2025 12:13:32 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. 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 3.9.0.) in /wp-includes/functions.php on line 6121
[03-Oct-2025 12:13:35 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. 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 3.9.0.) in /wp-includes/functions.php on line 6121
[03-Oct-2025 12:13:39 UTC] PHP Notice:  Function wpdb::prepare was called <strong>incorrectly</strong>. The query argument of wpdb::prepare() must have a placeholder. 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 3.9.0.) in /wp-includes/functions.php on line 6121
See also: All tests for this plugin, How to Hide onOffice for WP-Websites Admin Menus