PHP errors after recent updates

  • Resolved michaldybczak

    (@michaldybczak)


    6 years ago

    On php error debug log I saw something like this:

    Notice: Function id was called incorrectly. Properties of a product shouldn’t be accessible 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, ma_connector->the_template, ma_connector->execute_connector, MobileAssistantConnector->get_orders_info, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong Learn more: Debugowanie w WordPressie. (This notice was added in version 3.0.) in /home/akcesoriameblowe-online/public_html/wordpress/wp-includes/functions.php on line 4667

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author eMagicOne

    (@emagicone)

    Hello!

    Thank you for your comment.

    As we have checked with tech dept, there is no issue related to Mobile Assistant, this message is related to WordPress itself.

    Still, if you face inconveniences when using Mobile Assistant or receive any errors directly in the app – kindly submit a ticket to our Support Center via [email protected] and we will gladly check it.

    Regards.

    Thread Starter michaldybczak

    (@michaldybczak)

    What? Then why the message? It clearly says that your plugin is using some obsolete way of doing things, hence the complaint.
    The reason for reports as mine is to improve the plugin. I’m pretty sure the plugin must adjust to the WP, not the other way around, so I don’t really understand that answer. Are you really saying “it’s not us, it’s the WP”? In meantime, the plugin is literally spamming my debug log with those notices.
    Or maybe I’m not understanding something? I assume that notice isn’t bad (it’s not an error) but is pointing out toward some problems that may become errors in the future and it looks like WP is complaining about your plugin doing something that was depreciated a long time ago. So why not improve it?

    I found other threads with similar issue and plugin authors fixed it so I’m really disappointed in that answer that literally says “it’s not us, we won’t fix it” as if WP was doing things wrong and was suppose to adjust to your plugin… This is an insane and backward approach that causes issues to stay forever.

    Plugin Author eMagicOne

    (@emagicone)

    Hello again,

    We apologize if we have have misunderstood you, we answer here only for general questions.

    We will gladly assist you with your request and the tech person will give you full answer regarding the message you get.

    For this, please provide us with the versions of WordPress and WooCommerce you are currently using, and the list of plugins you have installed in the admin.

    Kindly send the email to [email protected]

    Regards.

    Thread Starter michaldybczak

    (@michaldybczak)

    OK, thanks, will do that.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘PHP errors after recent updates’ is closed to new replies.

Tags