• Status: Waiting on customer

FS#10864 - error_log in wp-admin

Hi, the error_log file in wp-admin constantly gets filled with the following message:

[28-Sep-2017 07:37:21 UTC] id was called incorrectly. Product properties should not be accessed directly. Backtrace: do_action(’admin_init’), WP_Hook→do_action, WP_Hook→apply_filters, PK_Features→admin_init, PK_Features→get_settings_fields, PK_Features→get_brands, WC_Abstract_Legacy_Product→__get, wc_doing_it_wrong. This message was added in version 3.0.

The entries are continuous, the file size increases by 3.3MB/min!

When I use another theme, eg TwentySeventeen, the error doesn’t occur.

I think it has to do with deprecated methods related to WooCommerce.
Attached you can find the WooCommerce status report. The under-construction website is spharm.infoscope.gr.

Any help would be much appreciated, cause now I have to “empty” the error_log file every day, so that the website folder doesn’t exceed the hosting space in the server.

Thank you in advance,
George Efthymiou

This ticket does not depend on any other tickets.

Marek (marek)
Thursday, 28 September 2017, 21:51 GMT+2
Support Team

Hi George.
Thank you for your report.
If it's not critical for you, could you please wait for next week to get a fix? Right now I have limited internet access.

George Efthymiou (geefthym)
Thursday, 28 September 2017, 22:34 GMT+2

Hi Marek, I understand.
Tomorrow it's Friday, so next week is not so far away. However, please put this issue in priority, because as I said, I have to empty the log file daily.

So I'll be waiting for your response.

Thank you,
George

Marek (marek)
Tuesday, 03 October 2017, 14:02 GMT+2
Support Team

Hi, George.
Could you please tell me the line and file where the error appears?

George Efthymiou (geefthym)
Tuesday, 03 October 2017, 14:24 GMT+2

That's all the server logs in /wp-admin/error_log file. It doesn't say anything about which file causes the problem.
Do you know if this information is maybe logged in another log file, e.g. apache error log?

Marek (marek)
Tuesday, 03 October 2017, 14:56 GMT+2
Support Team

Yes, it must be indicated in the apache error log

George Efthymiou (geefthym)
Wednesday, 04 October 2017, 20:28 GMT+2

Hello, I looked at apache error log and in error_log file inside public_html folder. I didn't find any mention in specific file and line about this error.
Could you please take a closer look at the problem? I know it might won't be easy to figured it out, but you have credentials for the backend and FTP access.
Maybe we have to update some woocommerce files? Or the way some woocommerce functions are called? Or maybe there is an incompatibility with a plugin.

I tried many things, but the error stopped occurring when I changed to seventeen twenty theme.

Any help would be much appreciated.
Thank you in advance,
George

Marek (marek)
Wednesday, 04 October 2017, 23:02 GMT+2
Support Team

I understand where the issue could appear, but would be easier to know exact line, but ok.
Could you please try to disable hoki features plugin and look is the issue still there?

George Efthymiou (geefthym)
Thursday, 05 October 2017, 12:18 GMT+2

I disabled Hoki features plugin and the issue disappeared (error_log file doesn't get bigger).

Marek (marek)
Thursday, 05 October 2017, 12:27 GMT+2
Support Team

Ok, I'll try to find the issue as soon as possible

Marek (marek)
Friday, 06 October 2017, 12:06 GMT+2
Support Team

Hi, George.
Could you please give me a path to error_log file which always get bigger

George Efthymiou (geefthym)
Friday, 06 October 2017, 12:20 GMT+2

Hi,

public_html/wp-admin/error_log

Marek (marek)
Friday, 06 October 2017, 13:09 GMT+2
Support Team

I just make an experimental fix, but it's hard to see the result. I suppose we should wait and watch on error_log

George Efthymiou (geefthym)
Friday, 06 October 2017, 13:37 GMT+2

The file used to grow by 3.3ΜΒ/min. Its size hasn't been changed for the last half-hour, so there good possibilities that the problem is solved.
In case it persists, I'll contact you back.

Thank you!

Marek (marek)
Friday, 06 October 2017, 13:38 GMT+2
Support Team

Ok, we will wait some time more

George Efthymiou (geefthym)
Monday, 16 October 2017, 17:29 GMT+2

Hi, the specific problem has been solved.
I'm getting back after some time, because a similar one has occurred.

In public_html/wp-admin/error_log now it says:

[13-Oct-2017 13:03:57 UTC] product_type was called incorrectly. Product properties should not be accessed directly. Backtrace: do_action('wp_ajax_nopriv_woof_draw_products'), WP_Hook→do_action, WP_Hook→apply_filters, WOOF→woof_draw_products, do_shortcode, preg_replace_callback, do_shortcode_tag, WOOF→woof_products, wc_get_template_part, load_template, require('/themes/hoki/woocommerce/content-product.php'), do_action('woocommerce_function_butons'), WP_Hook→do_action, WP_Hook→apply_filters, woocommerce_template_loop_add_to_cart, wc_get_template, include('/themes/hoki/woocommerce/loop/add-to-cart.php'), WC_Abstract_Legacy_Product→__get, wc_doing_it_wrong. This message was added in version 3.0.
[13-Oct-2017 13:03:57 UTC] The WC_Product::get_gallery_attachment_ids function is deprecated since version 3.0. Replace with WC_Product::get_gallery_image_ids.

The file doesn't grow as fast as in the previous case.

Could you please help me with this one, as it seems to be kind of similar to the previous issue?

Thank you in advance,
George Efthymiou

Marek (marek)
Monday, 16 October 2017, 21:18 GMT+2
Support Team

Hi George.
I'll try to fix where is the issue. I let you know once I'll have a result.

George Efthymiou (geefthym)
Tuesday, 17 October 2017, 12:15 GMT+2

Alright, thank you.

Marek (marek)
Thursday, 19 October 2017, 10:42 GMT+2
Support Team

I have tried to find the reason of warnings but still have no result. I also found another possible solution, but I don't know is it suitable for you or not. Please take a look http://www.techrounder.com/wordpress/wordpress-disable-error-logging-avoid-huge-error-log-file/

George Efthymiou (geefthym)
Thursday, 19 October 2017, 14:28 GMT+2

Yes, I have in mind that I can disable error logging. However, I think that the best solution is to avoid having errors and warnings.
If you continue taking care of the issue and you fix it, please let me know.

Thank you.

Marek (marek)
Thursday, 19 October 2017, 14:29 GMT+2
Support Team

Yes, I'll try to fix it

Loading...