Since recently I am getting a new PHP notice or warning in debug.log. It shows:

[08-Dec-2020 12:09:15 UTC] id was called incorrectly. Order properties should not be accessed directly. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_checkout’), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, apply_filters(‘woocommerce_payment_successful_result’), WP_Hook->apply_filters, WC_GZD_Emails->send_order_confirmation_mails, do_action(‘woocommerce_gzd_order_confirmation’), WP_Hook->do_action, WP_Hook->apply_filters, WC_Emails::send_transactional_email, do_action_ref_array(‘woocommerce_gzd_order_confirmation_notification’), WP_Hook->do_action, WP_Hook->apply_filters, WC_GZD_Emails->trigger_order_confirmation_emails, WC_Email_New_Order->trigger, WC_Email->get_attachments, apply_filters(‘woocommerce_email_attachments’), WP_Hook->apply_filters, WPO\WC\PDF_Invoices\Main->attach_pdf_to_email, WPO\WC\PDF_Invoices\Main->get_documents_for_email, apply_filters(‘wpo_wcpdf_custom_attachment_condition’), WP_Hook->apply_filters, wpo_wcpdf_exclude_payment_method, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.

I am assuming that this is related to this plugin. Does anyone know how I can get rid of this?

Thanks,
Chris

Anyways, I need to show the properties by size from the smallest to the biggest on every page.

For example, when user searches for a house with 3 bedrooms, the result should to be from the smallest to the biggest building based on the SqMt inserted in the “Size” field.

If that’s too much of a work, I’d need this feature at least on the “Advanced Search Page” widget for Visual Composer.

I hope to hear from you soon,
With best Regards,
Grete

We have a custom template with custom fields. After the last update, some customs fields are no longer displayed. Here is the part of our code :

<h3><?php $wpo_wcpdf->custom_field(‘_billing_civilite’); ?> <?php $wpo_wcpdf->custom_field(‘_billing_first_name’); ?> <?php $wpo_wcpdf->custom_field(‘_billing_last_name’); ?></h3>
<h3><?php $wpo_wcpdf->custom_field(‘_billing_address_1’); ?</h3>
<h3><?php $wpo_wcpdf->custom_field(‘_billing_address_2’); ?></h3>
<h3><?php $wpo_wcpdf->custom_field(‘_billing_postcode’); ?> <?php $wpo_wcpdf->custom_field(‘_billing_city’); ?></h3>

The custom field (‘_billing_civilite’) appears well but not the others.

Thank you for your help.

The following line in my template stops working when I upgrade from 1.5.9 to the latest version:

<div class="order-name"><?php $wpo_wcpdf->custom_field('_shipping_last_name', ''); ?> <?php $wpo_wcpdf->custom_field('_shipping_first_name', ''); ?> 様 </div>

The chinese character displays fine, but _shipping_last_name and _shipping_first_name don’t appear to be working. Is there something I should be replacing them with for later versions?