How to debug a failed import from GoDaddy (Managed WP)

Support
1

What issue or error are you experiencing?

Importing a .zip file with .sql and wp-content. I’ve imported lots from WP Engine, HostPapa, GoDaddy (full Wordpress).. this is the first time I’ve run into this (with a ‘managed WP’).

Log seems to point to:

“ERROR 1050 (42S01) at line 32: Table ‘wp_3x5rcvnqfa_commentmeta’ already exists\”

But the SQL file has only one line that says:

CREATE TABLE wp_3x5rcvnqfa_commentmeta

My REAL question is how do I debug this myself? Can I get verbose logging? TIA

What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc

Similar to closed thread at Importing site from GoDaddy Manged WordPress site

  • I suspect it’s a non-standard .sql option or setting

System Details

  • Local Version: Version 9.2.8+6882

  • Operating System (OS) and OS version: MacOS 15.6.1 (24G90)

Local Logs

Attach your Local Logs here (Help Doc - Retrieving Local’s Log)

local-lightning.log (753.8 KB)

Security Reminder
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.

2

Hey @g_dub!

Does the database include a DROP IF EXISTS statement? For example, here is a wp_commentmeta section from a new, blank Local site:

-- Table structure for table `wp_commentmeta`
--

DROP TABLE IF EXISTS `wp_commentmeta`;
/*!40101 SET @saved_cs_client     = @@character_set_client */;
/*!50503 SET character_set_client = utf8mb4 */;
CREATE TABLE `wp_commentmeta` (
  `meta_id` bigint unsigned NOT NULL AUTO_INCREMENT,
  `comment_id` bigint unsigned NOT NULL DEFAULT '0',
  `meta_key` varchar(255) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL,
  `meta_value` longtext COLLATE utf8mb4_unicode_520_ci,
  PRIMARY KEY (`meta_id`),
  KEY `comment_id` (`comment_id`),
  KEY `meta_key` (`meta_key`(191))
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
/*!40101 SET character_set_client = @saved_cs_client */;

--
-- Dumping data for table `wp_commentmeta`
--
3

just checked the script and no, it doesn’t have any such… I’ll add a bunch of ‘drop table if exists’ statements and try it out today.. TIA

1 Like
4

thx @Nick-B .. you pointed me to the issue. The DB Export actually uses its own DB schema, so I had to comment out:

CREATE DATABASE IF NOT EXISTS km9c45541183307 DEFAULT CHARACTER SET latin1 COLLATE latin1_swedish_ci;
USE km9c45541183307;

Thanks!! I’ll mark this as closed.

1 Like
5

Glad to hear you were able to narrow that down @g_dub! Thank you for coming back and sharing the resolution here. :green_heart: