SurfLink – Link Manager & Backup Restore

Yes! Database operations are powerful. Entering a wrong search or replace string could break your site. Always perform a Backup (using Module 3) before running a Search & Replace operation. Use the "Dry Run" feature first to verify what will be changed.

Yes, SurfLink supports restoring database on a different domain (WordPress Multisite Installation).

Yes, SurfLink automatically handles differences in database table prefixes.

This issue can occur if the login session expires after restoration and the active login security plugins interfere with your access to wp-login.php. There are two possible causes: 1. Login Security Plugins (WPS Hide Login, Loginizer, etc.) The Issue: Third-party login security plugins may also block access to wp-login.php or change the login URL. After a restore if login session expires, these settings may cause 404 errors or unwanted redirects if you try to access wp-login.php default login page. Note: SurfLink does NOT override or deactivate these plugins to be in line with wp org. guidelines - it only handles its own LoginHider module. Solutions to try: Option 1: Use your custom login URL (if known) - If you remember the custom login slug configured in the other plugin, access it directly - Example: yourdomain.com/your-custom-login-slug Option 2: Deactivate via FTP/File Manager Connect to your site using an FTP client (like FileZilla) or your hosting control panel's File Manager Navigate to the plugins folder: Go to: wp-content/plugins/ Deactivate the conflicting plugin by renaming its folder: Find the plugin's folder (e.g., wps-hide-login, loginizer, etc.) Rename it by adding -disabled to the folder name Example: Rename wps-hide-login to wps-hide-login-disabled This automatically deactivates the plugin Log in normally: Go to yourdomain.com/wp-login.php Log in with your credentials Decide which plugin to use: Go to Plugins → delete the disabled plugin (optional) Configure SurfLink's Login Security if you want to use SurfLink instead Important: Don't enable multiple login security plugins simultaneously 2. SurfLink's LoginHider Feature is ON and the grace period is over SurfLink automatically provides a 10-minute grace period after every restore operation. If your login session expires due to the restore operation, you will be redirected to the custom login URL (e.g., /secret-login) without facing a 404 error. But after the grace period, SurfLink will act normally i.e. will prevent you from the default wp-login.php with a 404 error. The Solution: Option 1 (Within 10 minutes): - Nothing to worry about. SurfLink will automatically redirect you to your custom login URL. - Just log in with your credentials. - Once logged in, go to SurfLink → Login Hider to verify your custom login slug Option 2: Use your custom login URL (if known) - If you remember the custom login slug configured in the plugin, access it directly - Example: yourdomain.com/your-custom-login-slug Option 3: Deactivate via FTP/File Manager - If grace period is over and you don't remember your custom login slug, then connect to your site using an FTP client or your hosting control panel's File Manager. - Navigate to the plugins folder, deactivate SurfLink plugin by renaming its folder. - Afterwards Log in via wp-login.php. - Finally, Don't forget to rename Surflink folder and activate it again in your dashboard.

It provides a custom login url with a nice login form. It also logs failed login attempts and automatically bans IP addresses after a set threshold.

No. It is not fully compatible with WordPress Multisite. Use with caution on Multisite installations.

You don't have to change anything it will adjust with your browser's preferred theme.