Destroyed JSON data structure

It’s exactly the same on local and live.

You can try viewing it here: https://raabjergmilecamping.dk/wp-json/acf/post/17
Here’s the JSON output:

"table-layout": {
          "header": false,
          "body": [
            [
              {
                "c": ""
              },
              {
                "c": "20/3-29/5"
              },
              {
                "c": "29/5-14/8"
              },
              {
                "c": "14/8-30/9"
              }
            ],
            [
              {
                "c": "Voksen"
              },
              {
                "c": "59 kr"
              },
              {
                "c": "76 kr"
              },
              {
                "c": "59 kr"
              }
            ],
            [
              {
                "c": "B?rn 0-11 ?r"
              },
              {
                "c": "34 kr"
              },
              {
                "c": "49 kr"
              },
              {
                "c": "34 kr"
              }
            ],
            [
              {
                "c": "Milj?till?g pr. person"
              },
              {
                "c": "14 kr"
              },
              {
                "c": "14 kr"
              },
              {
                "c": "14 kr"
              }
            ],
            [
              {
                "c": "Str?m 10 A"
              },
              {
                "c": "39 kr"
              },
              {
                "c": "39 kr"
              },
              {
                "c": "39 kr"
              }
            ],
            [
              {
                "c": "Hund"
              },
              {
                "c": "15 kr"
              },
              {
                "c": "15 kr"
              },
              {
                "c": "15 kr"
              }
            ]
          ]
        }
      }

This is from this page: https://raabjergmilecamping.dk/priser/
Where the backend looks like this live: https://c.matiasvad.com/e1mj
And like this locally (and on test-server): https://c.matiasvad.com/e2Is

Thanks much! I check this out within 24 hours.

Can you please say, what kind of migration tool you use? And I need the database entries of the field before and after migration copied from a database tool like MYSQL. I′m sorry about that, but this is a strange and tough issue.

Hi Johann,

Below some data from before and after migration, the tool used is WP migrate DB pro/WP sync db

Original data (created with v1.1.4)

{
	"p": {
		"o": {
			"uh": 1
		}
	},
	"c": {
		"0": {
			"p": ""
		},
		"1": {
			"p": ""
		}
	},
	"h": {
		"0": {
			"c": "Technische gegevens"
		},
		"1": {
			"c": ""
		}
	},
	"b": {
		"0": {
			"0": {
				"c": "Afmetingen rijbanen"
			},
			"1": {
				"c": "4400 x 617 x 126 mm\t"
			}
		},
		"1": {
			"0": {
				"c": "Afzekering"
			},
			"1": {
				"c": "16 A traag"
			}
		},
		"2": {
			"0": {
				"c": "Aggregaat"
			},
			"1": {
				"c": "2,5 kW, 3 x 400 V"
			}
		},
		"3": {
			"0": {
				"c": "Hef- en daaltijd"
			},
			"1": {
				"c": "ca. 35 sec."
			}
		},
		"4": {
			"0": {
				"c": "Hefcapaciteit"
			},
			"1": {
				"c": "3.500 kg"
			}
		},
		"5": {
			"0": {
				"c": "Inbouw diepte"
			},
			"1": {
				"c": "2.540 mm"
			}
		},
		"6": {
			"0": {
				"c": "Lengte oprijbanen (bij opbouw)"
			},
			"1": {
				"c": "1.000 mm"
			}
		},
		"7": {
			"0": {
				"c": "Maximale hefhoogte"
			},
			"1": {
				"c": "2.056 mm"
			}
		},
		"8": {
			"0": {
				"c": "Stempelafstand"
			},
			"1": {
				"c": "1.350 mm"
			}
		},
		"9": {
			"0": {
				"c": "Totale breedte"
			},
			"1": {
				"c": "2.074 mm"
			}
		}
	}
}

Orignal data (After re-save with v1.1.5)

{
	"p": {
		"o": {
			"uh": 1
		}
	},
	"c": [{
		"p": ""
	}, {
		"p": ""
	}],
	"h": [{
		"c": "Technische gegevens"
	}, {
		"c": ""
	}],
	"b": [
		[{
			"c": "Afmetingen rijbanen"
		}, {
			"c": "4400 x 617 x 126 mm\t"
		}],
		[{
			"c": "Afzekering"
		}, {
			"c": "16 A traag"
		}],
		[{
			"c": "Aggregaat"
		}, {
			"c": "2,5 kW, 3 x 400 V"
		}],
		[{
			"c": "Hef- en daaltijd"
		}, {
			"c": "ca. 35 sec."
		}],
		[{
			"c": "Hefcapaciteit"
		}, {
			"c": "3.500 kg"
		}],
		[{
			"c": "Inbouw diepte"
		}, {
			"c": "2.540 mm"
		}],
		[{
			"c": "Lengte oprijbanen (bij opbouw)"
		}, {
			"c": "1.000 mm"
		}],
		[{
			"c": "Maximale hefhoogte"
		}, {
			"c": "2.056 mm"
		}],
		[{
			"c": "Stempelafstand"
		}, {
			"c": "1.350 mm"
		}],
		[{
			"c": "Totale breedte"
		}, {
			"c": "2.074 mm"
		}]
	]
}

Data after migration (pulled to site with v1.1.5, data shows alright in editor)

{
	"p": {
		"o": {
			"uh": 1
		}
	},
	"c": [{
		"p": ""
	}, {
		"p": ""
	}],
	"h": [{
		"c": "Technische gegevens"
	}, {
		"c": ""
	}],
	"b": [
		[{
			"c": "Afmetingen rijbanen"
		}, {
			"c": "4400 x 617 x 126 mm\t"
		}],
		[{
			"c": "Afzekering"
		}, {
			"c": "16 A traag"
		}],
		[{
			"c": "Aggregaat"
		}, {
			"c": "2,5 kW, 3 x 400 V"
		}],
		[{
			"c": "Hef- en daaltijd"
		}, {
			"c": "ca. 35 sec."
		}],
		[{
			"c": "Hefcapaciteit"
		}, {
			"c": "3.500 kg"
		}],
		[{
			"c": "Inbouw diepte"
		}, {
			"c": "2.540 mm"
		}],
		[{
			"c": "Lengte oprijbanen (bij opbouw)"
		}, {
			"c": "1.000 mm"
		}],
		[{
			"c": "Maximale hefhoogte"
		}, {
			"c": "2.056 mm"
		}],
		[{
			"c": "Stempelafstand"
		}, {
			"c": "1.350 mm"
		}],
		[{
			"c": "Totale breedte"
		}, {
			"c": "2.074 mm"
		}]
	]
}

Dont know if this was what you are looking for but hope it helps!

EDIT: didn’t read correctly, I thought you needed this. Ill just leave it just in case

Johann: I’m using WP Migrate DB Pro 1.5.2.

Wow, this is really annoying – I haven’t touched the site since my last message, and I tried migrating several times, always with the same result – Messed up tables. And now when I look at the production site, every table is just as it should be. Like magic.

I will keep an eye on it, and see if I can reproduce the issue, so we can get some real data for you to look at, and hopefully get to the bottom of this.

Thanks for the data. The two date, re-save with v1.1.5 and after migration are identical. So there is no migration issue. I guess, the problem was caused by caching old data or scripts somewhere.