Normally I setup the monitor to use both PHP and WP error log.
The log entries are written to the same file debug.log
This works fine.
Now I am experimenting with switching of PHP logging and later switching on WP error logging on request.
I can see the WP log entries written in the debug.log file itself.
But when I select Log monitor I get the respons “Couldn’t open the file . Make sure file is exists or is readable.”
If I switch on PHP error logging again then I can see ALL log entries (both PHP and WP).

It looks like the plugin concludes that there will be no log file when PHP error logging has been switched off?

Can you please analyse? (And maybe also change the typo in the message text )

A suggested enhancement to make the monitor more readable has been delivered quickly.

I installed the plugin today for the first time. I am using Free Version, as I only need to download invoice sometimes.

In the Customer Invoice Template, I have added an Image and many custom fields.

I checked the php error log. And this is what I found:
The error message:

Payment gateway with handle ‘wc-payment-method-cod’ has been deactivated in Cart and Checkout blocks because its dependency ‘wc-blocks-registry’ is not registered. Read the docs about registering assets for payment methods:?https://github.com/woocommerce/woocommerce-blocks/blob/060f63c04f0f34f645200b5d4da9212125c49177/docs/third-party-developers/extensibility/checkout-payment-methods/payment-method-integration.md#registering-assets

What to do?

Over the Christmas holiday several of our automated backups failed because our host’s disk storage space had been filled with the following recurring error:

[29-Dec-2022 12:52:32 UTC] WordPress database error Unknown column '**db_name**_tec_occurrences.occurrence_id' in 'group statement' for query
                                        SELECT SQL_CALC_FOUND_ROWS  **db_name**_posts.ID
                                        FROM **db_name**_posts  LEFT JOIN **db_name**_term_relationships ON (**db_name**_posts.ID = **db_name**_term_relationships.object_id)
                                        WHERE 1=1  AND (
  **db_name**_posts.ID NOT IN (
                                SELECT object_id
                                FROM **db_name**_term_relationships
                                WHERE term_taxonomy_id IN (7,9)
                        )
  AND
  **db_name**_term_relationships.term_taxonomy_id IN (1617)
) AND ((**db_name**_posts.post_type = 'tribe_events' AND (**db_name**_posts.post_status = 'publish' OR **db_name**_posts.post_status = 'acf-disabled' OR **db_name**_posts.post_status = 'tribe-ea-success' OR **db_name**_posts.post_status = 'tribe-ea-failed' OR **db_name**_posts.post_status = 'tribe-ea-schedule' OR **db_name**_posts.post_status = 'tribe-ea-pending' OR **db_name**_posts.post_status = 'tribe-ea-draft'))) AND **db_name**_posts.ID IN (0)
                                        GROUP BY **db_name**_tec_occurrences.occurrence_id
                                        ORDER BY **db_name**_posts.menu_order ASC, **db_name**_posts.post_title ASC
                                        LIMIT 0, 20
                                 made by require('wp-blog-header.php'), wp, WP->main, WP->query_posts, WP_Query->query, WP_Query->get_posts, do_action_ref_array('pre_get_posts'), WP_Hook->do_action, WP_Hook->apply_filters, FacetWP_Request->update_query_vars, FacetWP_Renderer->render, WP_Query->__construct, WP_Query->query, WP_Query->get_posts, apply_filters_ref_array('posts_pre_query'), WP_Hook->apply_filters, TEC\Events\Custom_Tables\V1\WP_Query\Modifiers\Events_Only_Modifier->filter_posts_pre_query, TEC\Events\Custom_Tables\V1\WP_Query\Custom_Tables_Query->get_posts, WP_Query->get_posts

I know Advanced Custom Fields and Facet WP get a mention, but 90% of the lines reference TEC or tribe.

We display our events in a Widget if that helps.

Thanks,

Hunter

our hoster told us that the php error log is blasting (19gb within a few hours) because of Yoast SEO and we should solve this. But I don’t know how. Do you have any idea?

example log:

[05-Oct-2
021 22:01:28 UTC] WordPress-Datenbank-Fehler Unknown column 'version' in 'field list' für Abfrage UPDATE <code>wp_yoast_indexable</code> SET <code>object_id</code> = '1', <code>object_type</code> = 'user', <code>permalink</code> = 'https://drumtrainer.online/profile/adminod/', <code>title</code> = NULL, <code>description</code> = NULL, <code>is_cornerstone</code> = '0', <code>is_robots_noindex</code> = '0', <code>is_robots_nofollow</code> = NULL, <code>is_robots_noarchive</code> = NULL, <code>is_robots_noimageindex</code> = NULL, <code>is_robots_nosnippet</code> = NULL, <code>is_public</code> = NULL, <code>has_public_posts</code> = '0', <code>blog_id</code> = '1', <code>open_graph_image</code> = 'https://secure.gravatar.com/avatar/2cbcac2dce9fbc77dbe4acfc9dec1e82?s=500&d=blank&r=g', <code>open_graph_image_id</code> = NULL, <code>open_graph_image_source</code> = 'gravatar-image', <code>open_graph_image_meta</code> = NULL, <code>twitter_image</code> = 'https://secure.gravatar.com/avatar/2cbcac2dce9fbc77dbe4acfc9dec1e82?s=500&d=blank&r=g', <code>twitter_image_id</code> = NULL, <code>twitter_image_source</code> = 'gravatar-image', <code>version</code> = '1', <code>permalink_hash</code> = '43:9bf751752f225daa6aeb585a4b276c75', 

u!
pdated_at= '2021-10-05 22:01:28' WHEREid` = ‘1’ von require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), include(‘/themes/michigan/page.php’), get_header, locate_template, load_template, require_once(‘/themes/michigan/header.php’), wp_head, do_action(‘wp_head’), WP_Hook->do_action, WP_Hook->apply_filters, wp_robots, apply_filters(‘wp_robots’), WP_Hook->apply_filters, Yoast\WP\SEO\Integrations\Front_End\WP_Robots_Integration->add_robots, Yoast\WP\SEO\Integrations\Front_End\WP_Robots_Integration->get_robots_value, Yoast\WP\SEO\Memoizers\Meta_Tags_Context_Memoizer->for_current_page, Yoast\WP\SEO\Repositories\Indexable_Repository->for_current_page, Yoast\WP\SEO\Repositories\Indexable_Repository->find_by_id_and_type, Yoast\WP\SEO\Repositories\Indexable_Repository->upgrade_indexable, Yoast\WP\SEO\Builders\Indexable_Builder->build, Yoast\WP\SEO\Repositories\Indexable_Repository->find_by_id_and_type, Yoast\WP\SEO\Repositories\Indexable_Repository->upg!
rade_indexable, Yoast\WP\SEO\Builders\Indexable_Builder->build!
, Yoast\WP\SEO\Builders\Indexable_Builder->save_indexable, Yoast\WP\SEO\Models\Indexable->save, Yoast\WP\Lib\Model->save, Yoast\WP\Lib\ORM->save, Yoast\WP\Lib\ORM::execute`

Upon importing (manually) all my products from Zettle – some 180 of them. I keep getting the two errors below logged by the hundreds. This is not a problem per se, as the import is working fine, or so it at least seems.

PHP Notice:  Array to string conversion in /data/wordpress/wp-content/plugins/woo-izettle-integration/includes/izettle-integration-iz-products.php on line 1355
PHP Warning:  sprintf(): Too few arguments in /data/wordpress/wp-content/plugins/woo-izettle-integration/includes/izettle-integration-iz-products.php on line 1355

Another thing is that the process of getting images is s – l – o – w Maybe 2 images get imported per minute! Refreshing WP media library every now and then reveals that the import is bringing the images in, but the rate is, uh, sub-par

[07-Sep-2020 11:45:16 UTC] PHP Warning: Illegal string offset ‘header-title’ in /home/dibdench/public_html/wp-content/plugins/wptouch/core/class-wptouch-pro.php on line 580
[07-Sep-2020 11:45:16 UTC] PHP Warning: Illegal string offset ‘link-color’ in /home/dibdench/public_html/wp-content/plugins/wptouch/core/class-wptouch-pro.php on line 647
[07-Sep-2020 11:45:16 UTC] PHP Warning: Illegal string offset ‘link-color’ in /home/dibdench/public_html/wp-content/plugins/wptouch/core/class-wptouch-pro.php on line 648
[07-Sep-2020 11:45:16 UTC] PHP Warning: Illegal string offset ‘header-background-color’ in /home/dibdench/public_html/wp-content/plugins/wptouch/core/class-wptouch-pro.php on line 651
[07-Sep-2020 11:45:16 UTC] PHP Warning: Illegal string offset ‘header-background-color’ in /home/dibdench/public_html/wp-content/plugins/wptouch/core/class-wptouch-pro.php on line 652
[07-Sep-2020 11:45:16 UTC] PHP Warning: Illegal string offset ‘header-border-color’ in /home/dibdench/public_html/wp-content/plugins/wptouch/core/class-wptouch-pro.php on line 655
[07-Sep-2020 11:45:16 UTC] PHP Warning: Illegal string offset ‘header-border-color’ in /home/dibdench/public_html/wp-content/plugins/wptouch/core/class-wptouch-pro.php on line 656
[07-Sep-2020 11:45:16 UTC] PHP Warning: Illegal string offset ‘header-title’ in /home/dibdench/public_html/wp-content/plugins/wptouch/core/class-wptouch-pro.php on line 580
[07-Sep-2020 11:47:32 UTC] PHP Warning: ini_set() has been disabled for security reasons in /home/dibdench/public_html/wp-content/plugins/download-manager/download-manager.php on line 73

[09-Aug-2020 13:25:24 UTC] PHP Warning:  Illegal string offset 'url' in 
/public_html/wp-content/plugins/wp-cloudflare-page-cache/libs/preloader.class.php on line 42

[09-Aug-2020 13:25:26 UTC] PHP Warning:  Illegal string offset 'url' in 
 /public_html/wp-content/plugins/wp-cloudflare-page-cache/libs/preloader.class.php on line 26

[09-Aug-2020 13:25:26 UTC] PHP Warning:  Illegal string offset 'cf_cookie' in 
/public_html/wp-content/plugins/wp-cloudflare-page-cache/libs/preloader.class.php on line 38

PHP Warning: count(): Parameter must be an array or an object that implements Countable in /home/soapdirt/public_html/wp-includes/post-template.php on line 284

The log was 2GB in size when a client asked me to look at some problems in their site. The “quick fix” (see what I did there?) is to simply add the following before line 19 of quick-adsense/includes/widgets.php:

global $pages;
if ( !isset( $pages ) || !is_array( $pages ) ) {
    $pages = array();
}

I am hoping you will do this before your next release so that the client upgrading won’t cause the problem to recur.

Any idea how to stop it beyond disabling or limiting PHP Error Log?

Version info:
WordPress Version: 4.9.8.
PHP Version: 7.2
MySQL Version: 5.5
Remove Google Fonts References Version: 2.6

PHP Error Log Example:

WordPress-Datenbank-Fehler Got a packet bigger than ‘max_allowed_packet’ bytes für Abfrage UPDATE options SET option_value = ‘a:1:{s:8:\”cssfiles\”;a:205593:{s:32:\”049132cbcacf2d29f59d249d54db9907\”;s:0:\”\”;s:32:\”1753fc3953581ec4b18451c9db3295d1\”;s:0:\”\”;s:32:\”fa9622fceafe1ae91337cba630a1baa5\”;s:0:\”\”;s:32:\”162d99ee16d436403d06f9646e3e2298\”;s:0:\”\”;s:32:\”594e28b9808515abc357cdd767c1ab62\”;s:0:\”\”;s:32:\”3aece2109887a206e870c04e723bed85\”;s:0:\”\”;s:32:\”3da63798cb30f5aa6b780951e1481938\”;s:0:\”\”;s:32:\”004346d7a869403787ae004f4fd0cedf\”;s:0:\”\”;s:32:\”e187884a7444cbad528bef53ec840be6\”;s:0:\”\”;s:32:
.
.
.
WHERE option_name = ‘remove_google_fonts_configs’ von shutdown_action_hook, do_action(‘shutdown’), WP_Hook->do_action, WP_Hook->apply_filters, wp_ob_end_flush_all, ob_end_flush, remove_google_fonts_obend, remove_google_fonts_filter, preg_replace_callback, remove_google_fonts_css_file_handler, update_option, QM_DB->query
PHP Warning: Error while sending QUERY packet. PID=25757 in /homepages/10/d33843394/htdocs/www/wp-includes/wp-db.php on line 1924
.
.
.