Warning: touch(): Unable to create file /home/marcolinux7/workspace/my-site/content/plugins/image-regenerate-select-crop/log/tracer.log because Permission denied in /home/marcolinux7/workspace/my-site/wordpress/wp-admin/includes/class-wp-filesystem-direct.php on line 516

Thanks in advance

Many thanks & greetings

etc….
I checked the DB privileges for the user and sure enough, the DELETE permission had been revoked (now fixed), but my question is, why the cascade of error messages – seems like a bug to me.

I would like to create a custom log file with the updates that has been done on an import.

For example:

Currently, the log file will create a line like this:
Property regular_price updated with value 35.95

I would like to see the following in the log file:
Property regular_price updated from ‘30.00’ with value 35.95

And this basically for each field that has been updated. So old value versus new value.

Could you please help me with this?

Thanks a lot.

HINT:
The page I need help with:
Not available (… because Yoast is disabled since a week because of the error!)

—

Since about a week we are having serious problems with our website everytimes we are trying to activate the yoast-plugin.

The main problem is the missing display of the All-Posts list logged in as a User with editor-role.
Firstly an “server error”-message was displayed beyond the usual header-items of the list.
Trying to activate the yoast-plugin (after waiting about a week) today again (… in hope of self-healing abilities over time we’re getting a hint to switch on WP-debugging.

Doing so, i.e. enabling WP-debugging, a massive log-file was created:
About 5 GByte! … in only a few minutes, when trying to display the All-Posts-list.

Main problem of the plugin seems to be trying to access the column “version” of the
#NON-EXISTING table twli_wp4_wp_yoast_indexable

Now we’re very surprised:

How the yoast-plugin can try to use a non-existent table!
or – not much better –
How the yoast-plugin is getting lost of an entire (self owned ?!) table!

All this also happened on a productive iunstance ;-((

—

So we are finally having this questions:

* Are we the only website watching this problems?
* Is there a known procedure to “heal” this issue?
* Should we better consider to find an alternative plugin?

Kind regards,
also in hope of getting some enlightening about this uncomfortable issue

Jens Roggemann
Diepholz / Freistatt, Germany

(since now minus 7 days an overall pleased user of the yoast-plugin for about 2,5 years)

This is the reply from Kinsta Support:
“Unfortunately it is not possible to overwrite the 403 block for the log files. I tried setting up different rules but the block always take precedence. If you are able to rename the log file from your plugin like log_file.txt using a .txt extension instead, then you should be able to access it via http.”

Would it be possible to give your log file the extension .txt, instead of .log?

[06-Oct-2020 20:49:10 UTC] PHP Notice: Undefined index: HTTP_USER_AGENT in /var/www/clients/client90/web69/web/mysite/wp-content/plugins/ecwid-shopping-cart/includes/kliken.php on line 3

Looks like a little hot programmed without checking first, that the required element exists. Thank you for having a look on it

new idea from my side: display the username in some cases are not very meaningful (e.g. if a nic-name or mail-address is used).
It would be better to access the display name then.

And because there are plugins that make it automatically from the first name and last name, the view in logging would be more perfect.

Thank you again!