wji

good tip! Keep up the good work.

Hi John,

I got feedback from Ithemes (from the migration plugin Backupbuddy) about this problem.
I think it is interesting information to address the issue.

I quote from Ithemes support:

The symlink _should_ be defined as relative rather than absolute – the _relationship_ between the source and target will not change when the site is moved (migrated) so there is no problem. Currently the symlink is defined as an absolute path and this is what causes the problem. This is the _best_ solution for _users_ of the plugin and would be very simply implemented by the plugin author.

…

let’s suppose a scripts did search every file just to check for any symlink that needed to be changed to something – not all hosts allow the use of the symlink() function to define symlinks and so this simply wouldn’t be possible (the qm plugin itself acknowledges this because it checks whether the symlink() function is available and doesn’t provide this particular functionality if it is not). So if the migration couldn’t update the symlink() what does it do? It might tell you it finds an invalid symlink that cannot be updated

John, is it possible to adjust this in a future update? Especially for a debugging plugin like QM portability is very much appreciated for a great plugin like QM.
Let me know what you think.

Regards,

This is what was causing the issue,
Ipstas’s brilliant remark:

Then figured out – I was backing up to windows box, symlink was lost and for some reason was not recreated while installing. So, I have just created symlink manually
wp-content# ln -s plugins/query-monitor/wp-content/db.php .
Now it works

The symlink path is copied with a migration, but not changed to the new path, plugins keeps using the old symlink path.

John, any way you can fix this in an upgrade?

Dear John,
any updates on this? Error seems persistent with moving installs.

Regards,