Interference with W3 Total Cache due to "db.php"

[SemoTech]

Hello,

Seems Query-Monitor (latest v3.15.0) creates a file called db.php located at:
.../public_html/wp-content/db.php
which is actually a simlink to:
.../public_html/wp-content/plugins/query-monitor/wp-content/db.php

Now, W3 Total Cache puts up an error about "FTP credentials don't allow to copy to file .../public_html/wp-content/db.php"
It is trying to issue this command which fails since the target file is a symlink:
cp /public_html/wp-content/plugins/w3-total-cache/wp-content/db.php /public_html/wp-content/db.php

Is there any way for Query-Monitor to rename/use a different name, like "QMDB.php", as not to interfere with W3 Total Cache?

Thank you.

[John Blackbourn]

Unfortunately this is a limitation of WordPress itself. See https://querymonitor.com/help/db-php-symlink/#when-an-existing-db-php-file-is-already-in-place for a little more info.

[SemoTech]

Thanks @johnbillion. In my case this actually turned out to be a legacy symlink from InterWorx. Deleting it fixed the issue with W3 Total Cache!