As default WP Staging tries to create a staging site in a subfolder of the live site root folder. If this folder has no write permission, WP Staging will show a warning like this and can not create the staging site as intended:
Don’t worry – we have a solution for you! This article will provide two simple workarounds to help you successfully create a staging site in a sub-directory without having to worry about the root directory read & write permissions.
Solution 1: Manually Create the Sub-directory via an FTP Client
For users who have access to their server via FTP, you can create the staging site sub-directory manually. This allows you to bypass the permission issues in the WordPress root directory. Follow these steps to create the sub-directory using an FTP client:
- Download and install an FTP client, if you haven’t already. Some popular options include FileZilla, WinSCP, and Cyberduck.
- Connect to your server using your FTP credentials (host, username, and password). You can usually find this information in your hosting control panel or by contacting your hosting provider.
- Once connected, navigate to the root directory where your WordPress installation resides.
- Create a new folder within the root directory. Name it something descriptive, such as “staging” or “test-site”.
- Adjust the folder permissions to allow read/write access. In most FTP clients, you can do this by right-clicking the folder, selecting “Properties” or “Permissions,” and setting the permissions to “755” or “775”, depending on your server configuration.
- Now, make sure to use the same sub-directory name you created in step 4 above when you create the staging site as in this screenshot:
Solution 2: Use an Alternative Writable Location
If you prefer not to use an FTP client or if you encounter issues with the first solution, you can choose to create the staging site in an alternative writable location, such as the “/wp-content/uploads/” folder. Use the settings as described in this screenshot:
You can use WP Staging Pro and create a staging site in a completely different folder and in another domain or subdomain to bypass this issue. In that case you can choose a totally different folder and do not need to create the staging site in the write protected root folder.
If you have any questions or require further assistance, feel free to reach out to our support team. We’re always here to help!