• Resolved aakraak

    (@aakraak)


    I am trying to duplicate an existing website. I created a subdomein, with a database. I uploaded the duplicator .zip, but the “validation button” is not responsive. Because I was unable to use this methode I tried to do a clean WordPress install with the latest version of Wordpres 6.5. When I did this, the CSS of the install screens was missing. After the install, buttons in the backend were non responsive. For example the change password button for a any user doesn’t respond.


    I tried:
    Deleting the browser cache from Chrome
    Changing from Chrome to Safari
    Changing the PHP version from 7.4 to 8.0
    Installing WordPress 5.9

    Using local the duplicator file does work. But I am not able to get it running on my server. At this point, I do not know what to do next.

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • It sounds like you’ve encountered several issues during your website duplication process and WordPress installation. Let’s troubleshoot step by step:Step 1: Ensure Server Compatibility

    1. Check PHP Settings: Ensure your server meets the WordPress requirements. PHP version should be 7.4 or higher. Also, check the following PHP settings:
      • max_execution_time should be at least 300 seconds.
      • memory_limit should be at least 256M.
      • upload_max_filesize and post_max_size should be at least 64M.
    2. Check MySQL Version: Ensure your MySQL version is 5.7 or higher.
    3. Check Apache/Nginx Settings: Ensure your web server (Apache or Nginx) is properly configured and supports .htaccess files if you are using Apache.

    Step 2: Resolve CSS and Button Issues

    1. File Permissions: Ensure all WordPress files have the correct permissions. Typically:
      • Folders should have 755 permissions.
      • Files should have 644 permissions.
    2. .htaccess File: Ensure your .htaccess file is correctly configured. You can use the default WordPress .htaccess file:plaintextCopy code# BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteRule ^index\.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] </IfModule> # END WordPress
    3. Disable Plugins and Themes: Sometimes plugins or themes can cause issues. Rename the plugins and themes folders inside wp-content to temporarily disable them.

    Step 3: Troubleshooting Duplicator

    1. Check Duplicator Log: Check the duplicator log files for any errors or warnings.
    2. Server Logs: Check your server logs (Apache/Nginx and PHP error logs) for any clues or errors during the duplicator process.
    3. Manual Migration: If duplicator still fails, consider a manual migration:
      • Export your database from the original site using phpMyAdmin or a similar tool.
      • Import the database into your new site’s database.
      • Copy all WordPress files from the original site to the new site.
      • Update the wp-config.php file with the new database details.
      • Update the site URL in the database using phpMyAdmin:sqlCopy codeUPDATE wp_options SET option_value = 'https://newsiteurl.com' WHERE option_name = 'siteurl'; UPDATE wp_options SET option_value = 'https://newsiteurl.com' WHERE option_name = 'home';

    Step 4: Additional Checks

    1. Check for Corrupted Files: Sometimes, files can get corrupted during transfer. Re-upload the WordPress core files.
    2. Browser Console: Open the browser console (F12) and check for any JavaScript errors that could be causing the issues.
    3. Server Resources: Ensure your server has enough resources (CPU, RAM) to handle the WordPress installation and duplication process.

    By following these steps, you should be able to identify and resolve the issues with your WordPress site duplication and installation. If you continue to experience problems, providing specific error messages or logs can help further diagnose the issue.

    Thread Starter aakraak

    (@aakraak)

    All sounds good, but I think this is a server issue. I will contact my hosting provider.

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.