Function ID was called incorrectly. should not be accessed directly

Resolved

(@balvan64)

Hello,

Since the last update these appear many times in our log:

[21-Feb-2026 10:19:24 UTC] PHP Notice:  Function ID was called <strong>incorrectly</strong>. Order properties should not be accessed directly. Backtrace: do_action('woocommerce_page_wc-orders'), WP_Hook-&gt;do_action, WP_Hook-&gt;apply_filters, Automattic\WooCommerce\Internal\Admin\Orders\PageController-&gt;output, Automattic\WooCommerce\Internal\Admin\Orders\Edit-&gt;display, Automattic\WooCommerce\Internal\Admin\Orders\Edit-&gt;render_meta_boxes, do_meta_boxes, Plf_setting-&gt;plf_meta_box, WC_Abstract_Legacy_Order-&gt;__get, wc_doing_it_wrong 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.0.) in /home/aaa/public_html/wp-includes/functions.php on line 6131

[21-Feb-2026 10:19:24 UTC] PHP Notice:  Function ID was called <strong>incorrectly</strong>. Order properties should not be accessed directly. Backtrace: do_action('woocommerce_page_wc-orders'), WP_Hook-&gt;do_action, WP_Hook-&gt;apply_filters, Automattic\WooCommerce\Internal\Admin\Orders\PageController-&gt;output, Automattic\WooCommerce\Internal\Admin\Orders\Edit-&gt;display, Automattic\WooCommerce\Internal\Admin\Orders\Edit-&gt;render_meta_boxes, do_meta_boxes, Plf_setting-&gt;plf_meta_box, WC_Abstract_Legacy_Order-&gt;__get, wc_doing_it_wrong 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.0.) in /home/aaa/public_html/wp-includes/functions.php on line 6131

[21-Feb-2026 10:19:25 UTC] PHP Notice:  Function ID was called <strong>incorrectly</strong>. Order properties should not be accessed directly. Backtrace: do_action('woocommerce_page_wc-orders'), WP_Hook-&gt;do_action, WP_Hook-&gt;apply_filters, Automattic\WooCommerce\Internal\Admin\Orders\PageController-&gt;output, Automattic\WooCommerce\Internal\Admin\Orders\Edit-&gt;display, Automattic\WooCommerce\Internal\Admin\Orders\Edit-&gt;render_meta_boxes, do_meta_boxes, Plf_setting-&gt;plf_meta_box, WC_Abstract_Legacy_Order-&gt;__get, wc_doing_it_wrong 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.0.) in /home/aaa/public_html/wp-includes/functions.php on line 6131

How can this be resolved?

Thank you

This topic was modified 1 month, 2 weeks ago by balvan64.

Viewing 9 replies - 1 through 9 (of 9 total)

Plugin Author enomoto celtislab
(@enomoto-celtislab)

1 month, 2 weeks ago

This is not an error generated by plugin load filter.

It appears to be a PHP Notice output when WordPress is running in WP_DEBUG mode, displaying a warning “Order properties should not be accessed directly.” on the woocommerce_page_wc-orders hook.

Please contact the WooCommerce plugin support.

Thread Starter balvan64
(@balvan64)

1 month, 2 weeks ago

Hello,
Thank you for your reply.

I think it might be Plugin Load Filter after all.

Here is an order opened with PLF active:

And this is the same order loaded after I deactivated PLF:

As you can see, when PLF is not active, the issue is gone.

Maybe you can look into it?

Thank you

Plugin Author enomoto celtislab
(@enomoto-celtislab)

1 month, 2 weeks ago

It seems that the plugin load filter settings box, which appears on editing screens like order pages, is considered legacy and deprecated, and this is a warning message about it.

This plugin load filter settings box is displayed on the editing screens for posts, pages, and custom post types.

To address this, we need to add a feature to prevent this editing box from being displayed on WooCommerce custom page types. However, other plugins might also deprecate similar features in the future.

Disabling it for all custom post type editing pages uniformly could have a significant impact, so it seems necessary to add some selective custom post type disabling functionality.

I anticipate that this will take some time. I aim to complete the implementation by the end of March to be ready for the next WordPress version update.
Thread Starter balvan64
(@balvan64)

1 month, 2 weeks ago
Hello,
Thank you for your reply.

Is there no way to preserve the same functionality, but update the code so it complies with the current WooCommerce standards?

From what I understand, the issue comes from accessing order properties directly, for example:
```
$order->id;
$order->order_total;
```
And that this should now be replaced with the proper getter methods, such as:
```
$order->get_id();
$order->get_total();
```
Wouldn’t updating those calls resolve the warning while keeping the settings box available?

Thank you
Thread Starter balvan64
(@balvan64)

3 weeks, 6 days ago

Hello,
What are your thoughts? can you release an update?

Thank you

Plugin Author enomoto celtislab
(@enomoto-celtislab)

1 week, 6 days ago

I have added a hide option for plugin filters on the custom post type edit screen.
Thread Starter balvan64
(@balvan64)

1 week, 2 days ago
Hello,
Thank you for your reply.

I’m not sure I fully understand what was added or how it is intended to help in this case.

The issue we encountered is a warning related to accessing order properties directly, which appears during admin execution and not specifically on the edit screen UI.

Could you please clarify:
- where this new option is located
- what it does exactly
- and how it is expected to resolve this issue?
Thank you
- This reply was modified 1 week, 2 days ago by balvan64.
- This reply was modified 1 week, 2 days ago by balvan64.
Plugin Author enomoto celtislab
(@enomoto-celtislab)

1 week, 2 days ago

I have added a feature to hide the individual page filter settings of the plf_meta_box, which were previously displayed on the custom post type edit screen.

If you set the individual page filter settings to hidden on the WooCommerce order page, the plf_meta_box displayed by PLF will no longer be involved on that edit screen.

If you still encounter any PHP errors, the cause lies outside of PLF.
It may be due to the way $order->id or $order->order_total are written, as you have already pointed out.
However, since that code is not part of PLF, it needs to be fixed by the plugin that generates it, and there is nothing I can do within PLF to address it.
Thread Starter balvan64
(@balvan64)

6 days, 15 hours ago
Hello,

Thank you for your reply.

It seems the update had made it possible to avoid the issue, and it not longer appear in our log.

Thank you
- This reply was modified 6 days, 15 hours ago by balvan64.

Viewing 9 replies - 1 through 9 (of 9 total)

You must be logged in to reply to this topic.