Don’t recognise your own db.php?

  • dapster105

    (@dapster105)


    3 years ago

    Hi John. Love the plugin, great work!
    Unfortunately my host provides no mechanism for creating symlinks so I thought I’d just copy the db.php file to the wp-contents directory manually and add it to my ‘update notes’ crib sheet!
    Weirdly the plugin then complains that an incompatible db.php is already in place. Anyway you could extend your code to check if it is, in fact, YOUR db.php and not someone elses!
    Cheers,
    Tim

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    The original intention of the symlink (instead of copying the file) is to avoid the copied file getting out of date with changes in the plugin. Years ago there used to be endless support threads in the forums of plugins such as W3 Total Cache and others that copy the db.php file into place, where the plugin had been updated to a newer version but the db.php drop-in hadn’t, and things broke. With a symlink it avoids that problem.

    QM doesn’t support the db.php file being copied into place, and I’d be hesitant to allow it because of the above. I’ll have a think about it, but no guarantees. And you might want to find a better host ??

    Thread Starter dapster105

    (@dapster105)

    Fair enough, and yes I do. ??

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Don’t recognise your own db.php?’ is closed to new replies.