Re-install of XAMPP, followed by 1.000s of error messages!
-
I do not know how special my situation is, I presume that may people has experienced something similar, but to me this is a first!
For reasons I will not dive in to, I had to uninstall XAMPP and make a “fresh” installation, but before I did this, I copied the files in “data” and “backup” in the MySQL folder and the “htdocs” folder from the XAMPP installation.
After having uninstalled the old instance of XAMPP and installed the latest new version, I located the new “data” and “backup” folders in the MySQL folder and the “htdocs” folder in new XAMPP installation, replacing them with the old copies and started the servers.
I then checked the phpMyAdmin site and found that all the databases was established, so I proceeded to the first (of 9) website I am working on by entering “localhost/website name/wp-admin”, only to be presented with the installation menu for WordPress.
After having selected the language and filled in the name of the website, my email address and selecting pressing “Install WordPress” (I had no other options), a page called ” localhost/website name/wp-admin/install.php?step=2” appeared with several 1.000 of error messages (please see the attached for the first browser window of error messages – in total it was in excess of 90 browser windows long!
I wanted to attached a screen dump of the first page for your information, but the people who knows the answer probably know what it looks like in full – any way, at the bottom I will cut and paste the first browser page or so.
Now the first and most important question is, how do I solve this issue so that I can access the websites on my localhost installation and work on them – without having to rebuild the sites all over?
The second question – which is not that important if I get the first issue solved, but still important for my own curiosity and to prevent that something like this happens again and so we all can learn – is what has gone wrong?
Your assistance in solving this issue is naturally very much appreciated.
———-First browser window error message start———-
WordPress database error: [Table ‘wp_users’ already exists]
CREATE TABLE wp_users ( ID bigint(20) unsigned NOT NULL auto_increment, user_login varchar(60) NOT NULL default '', user_pass varchar(255) NOT NULL default '', user_nicename varchar(50) NOT NULL default '', user_email varchar(100) NOT NULL default '', user_url varchar(100) NOT NULL default '', user_registered datetime NOT NULL default '0000-00-00 00:00:00', user_activation_key varchar(255) NOT NULL default '', user_status int(11) NOT NULL default '0', display_name varchar(250) NOT NULL default '', PRIMARY KEY (ID), KEY user_login_key (user_login), KEY user_nicename (user_nicename), KEY user_email (user_email) ) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci
WordPress database error: [Table ‘wp_usermeta’ already exists]
CREATE TABLE wp_usermeta ( umeta_id bigint(20) unsigned NOT NULL auto_increment, user_id bigint(20) unsigned NOT NULL default '0', meta_key varchar(255) default NULL, meta_value longtext, PRIMARY KEY (umeta_id), KEY user_id (user_id), KEY meta_key (meta_key(191)) ) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci
WordPress database error: [Table ‘wp_termmeta’ already exists]
CREATE TABLE wp_termmeta ( meta_id bigint(20) unsigned NOT NULL auto_increment, term_id bigint(20) unsigned NOT NULL default '0', meta_key varchar(255) default NULL, meta_value longtext, PRIMARY KEY (meta_id), KEY term_id (term_id), KEY meta_key (meta_key(191)) ) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci
WordPress database error: [Table ‘wp_terms’ already exists]
CREATE TABLE wp_terms ( term_id bigint(20) unsigned NOT NULL auto_increment, name varchar(200) NOT NULL default '', slug varchar(200) NOT NULL default '', term_group bigint(10) NOT NULL default 0, PRIMARY KEY (term_id), KEY slug (slug(191)), KEY name (name(191)) ) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci
———-First browser window error message end———-
- You must be logged in to reply to this topic.