XAMPP ProFTPD für Wordpress konfigurieren
XAMPP is a local server environment for developing and hosting web applications on your device. And it's highly likely you are using this setup already.
If you also use Wordpress for some of your projects, you probably have experienced some issues when it comes to updating the core or installed plugins. I am going to show you briefly how you can fix that using the ProFTP module that comes with XAMPP.
Thou shall not pass..
Something that never seems to be any issue on a regular server online, just does not work straight out of the box locally. So you end up being asked for FTP user credentials, when trying to update the WP core, your plugins or theme(s).
But – what are you supposed to enter here, when you're on your own machine?
Ugly Workaround
Without entering credentials, the only way of updating is downloading the files manually and pasting them to the korrect folders.
But when it comes to updating the Wordpress core, things get a little more complicated or let's say annoying. We do prefer the more convenient way, don't we?
Just activating ProFTPD does not cut it.
ProFTPD is already part of the XAMPP package, but after activating the module, still nothing can be updated by just clicking a button.
In the end it's a piece of cake – once you know the way to the bakery.
So what are the FTP credentials then, and where can we store them to avoid entering those every time we need to update something? Luckily we can just write those into the Wordpress config file (config.php), in order to store them as global variables.
Assuming you have not altered the original XAMPP installation, the FTP credentials should be as follows.
Just add those to the end of your wp-config.php:
/** XAMPP ProFTPD settings */
define("FS_METHOD","direct");
define("FTP_HOST", "localhost");
define("FTP_USER", "daemon");
define("FTP_PASS", "xampp");
Fig. 3: Settings for ProFTPD inside the wp-config.php
Provide read access for daemon
Now you have enabled updates directly from the Wordpress backend. Please be advised to provide read/write access for the system user daemon.
Got beef?
Comments for this entry have not been activated.
Comments to this post