• Resolved mattkersley

    (@mattkersley)


    Notice: id was called incorrectly. Product properties should not be accessed directly. Please see Debugging in WordPress for more information. (This message was added in version 3.0.) in /home/devcasestation/public_html/zeus/wp-includes/functions.php on line 4137

    $product->id needs to be changed to $product->get_id()

    Hope that helps.

Viewing 15 replies - 1 through 15 (of 27 total)
  • Plugin Contributor yikesitskevin

    (@yikesitskevin)

    Hey @mattkersley,

    Thanks for the info. I was going to go through the plugin today at some point and try to catch any 3.0 changes.

    Cheers,
    Kevin.

    Thread Starter mattkersley

    (@mattkersley)

    No worries, client project meant I was running it on the new version, so figured I’d help ??

    Hello! I’m having this same issue and have no idea how to fix it. I’m using the theme “Divi” and this message is displaying on my products page. Where do I insert the code? I can’t seem to find it anywhere…

    Thank you so much!

    I also get this error after updating woocommerce, fairly new to all this can someone help with a ‘fix’ in layman’s terms. Thank you.

    the exact error Im getting is :
    Notice: variation_id was called incorrectly. Product properties should not be accessed directly. Please see Debugging in WordPress for more information. (This message was added in version 3.0.) in /wp-includes/functions.php on line 4137

    • This reply was modified 7 years, 7 months ago by gffmac.
    Plugin Contributor yikesitskevin

    (@yikesitskevin)

    @mattkersley, @cowjuh, @gffmac

    I pushed a new version, 1.5.9, yesterday that should have fixed this. Can everyone upgrade to the latest version and let me know if the error is still there? It would be greatly appreciated!

    Thanks,
    Kevin.

    Thread Starter mattkersley

    (@mattkersley)

    was fixed for me after an upgrade yesterday (resolved the ticket).
    @gffmac has a slightly different issue, so I’ll let them sign-off on their issue ??

    Yes sorry I think this is a general 3.0 issue, I googled the issue and came to this thread.

    Plugin Contributor yikesitskevin

    (@yikesitskevin)

    Thanks Matt.

    Thanks @gffmac!

    @gffmac – we don’t call the variation ID anywhere in the plugin, so if you’re still seeing this error, please disable our plugin and check again – if the error remains then it isn’t coming from us. Let me know. ??

    • This reply was modified 7 years, 7 months ago by yikesitskevin.

    I rebuilt my permalinks and things started working again.

    Settings > Permalinks

    Check your option and then save changes. You might have to clear your cache plugin afterwards too.

    Hi Guys,

    Same problem here:

    Notice: payment_method_title was called incorrectly. Order properties should not be accessed directly. Please see Debugging in WordPress for more information. (This message was added in version 3.0.) in /home/public/sites/www.kunstinkaart.nl/wp-includes/functions.php on line 4137
    Payment method:
    iDEAL

    Notice: billing_email was called incorrectly. Order properties should not be accessed directly. Please see Debugging in WordPress for more information. (This message was added in version 3.0.) in /home/public/sites/www.kunstinkaart.nl/wp-includes/functions.php on line 4137

    Notice: billing_first_name was called incorrectly. Order properties should not be accessed directly. Please see Debugging in WordPress for more information. (This message was added in version 3.0.) in /home/public/sites/www.kunstinkaart.nl/wp-includes/functions.php on line 4137

    Notice: billing_last_name was called incorrectly. Order properties should not be accessed directly. Please see Debugging in WordPress for more information. (This message was added in version 3.0.) in /home/public/sites/www.kunstinkaart.nl/wp-includes/functions.php on line 4137

    Notice: billing_last_name was called incorrectly. Order properties should not be accessed directly. Please see Debugging in WordPress for more information. (This message was added in version 3.0.) in /home/public/sites/www.kunstinkaart.nl/wp-includes/functions.php on line 4137

    https://kunstinkaart.nl/checkout/order-received/66743/?key=wc_order_58e8f594163ad

    Anyone can tell me please how to fix this?
    Where i should change “$product->id needs to be changed to $product->get_id()” which file we should check?

    Thanks

    to get product id you can use that
    $id = method_exists( $product, 'get_id' ) ? $product->get_id() : $product->id;

    Plugin Contributor yikesitskevin

    (@yikesitskevin)

    Hello Everyone,

    The notices thrown by this plugin should be fixed – make sure you have v1.5.11.

    @fcujorick2 – I don’t believe these notices are coming from our plugin. We do not interact with the billing details in that way. Please try turning off our plugin and verifying the errors remain.

    @maldboy – The code snippet @hafizusman pasted is correct, but if you have the latest version of the plugin you shouldn’t need to change anything. What notice are you seeing? It is most likely the same issue @fcujorick2 is having (notices being thrown from other plugins). If you turn off our plugin and the error remains, it’s not us. You can turn off plugins sequentially until finding the one throwing the notice.

    If I’m wrong and there is a notice being thrown from our plugin, please let me know!

    Cheers,
    Kevin.

    P.S. @hafizusman – thanks for the help :-)!

    Hi,

    I;m using Flatsome theme and the shopping cart & product cart for Woocommerce is all messed up after the latets update.

    I get this msg

    Notice: product_type was called incorrectly. Product properties should not be accessed directly. Please see Debugging in WordPress for more information. (This message was added in version 3.0.) in /hermes/bosnaweb05a/b2681/ipg.kadzafashioncom/kadzafashion.com/wp-includes/functions.php on line 4137

    Plugin Contributor yikesitskevin

    (@yikesitskevin)

    Hi @dinodrumz,

    Are you using the Custom Product Tabs plugin? We don’t access the product_type attribute in this plugin, so I believe your issue is coming from a different plugin/theme.

    Kevin.

Viewing 15 replies - 1 through 15 (of 27 total)
  • The topic ‘WooCommerce 3.0 Notice’ is closed to new replies.