0

I have an XML from our old WP website that I'd like to import into new WP (management makes me do this, help). Now, the XML is quite thick, and I'm using WP all import to import it. The catch is, the management for some reason wants to import it to jet-engines Custom Content Types (CCT) instead of custom Post Types (CPT), and WP all import doesnt support that. Why? No idea. I doubt they have one either.

Their original argument is that when the xml will grow larger, the pages will load slower. It's quite obvious as WP isnt the fastest thing out there when it loads 100+ rows from CPT.

I've asked in all the places really, WP all import people, jet-engine people. Now I ask here. Is it possible to somehow link these two? I am aware I can create a relation inside jet engine, and I've done that, but is it possible to automate connecting the parent-child relation?

All that "I" need is 1:1 relation. Once again, don't ask.

OR, what are some other ways to make WP bit faster when loading these from the CPTs?

Please help, I'm going insane.

Tried creating custom CPTs, CCTs, relations, manually adding tables, all the shenanigans. Consulted the right people who should knew (to no surprise, they said it's impossible the way "I" want to do it)

O. Jones
  • 103,626
  • 17
  • 118
  • 172
justacrappyprogrammer
  • 3
  • 1
  • With respect, the argument that many custom posts slow down WordPress is incorrect. The performance argument made in this [JetEngine document](https://crocoblock.com/knowledge-base/articles/jetengine-how-to-create-a-custom-content-type/) is not correct. Specifically, access to the posts table is much faster than they claim unless your theme does something very strange. It's not surprising that the XML exported from WordPress imports back only to posts. You'll need to write some kind of program to create a post table entry for each separate data item visible to users. – O. Jones Dec 21 '22 at 13:08

0 Answers0