[Dennis Freeze]

OK, I’m good. Cloned the template, added what I needed, and it works….

Thanks!

[Dennis Freeze]

Brian,

Thanks, I’ll tweak the template as you suggested — should be a trivial fix. If you don’t hear back from me on this one, assume it’s fixed. 🙂

[Dennis Freeze]

Josh,

Thanks — I expected that Events would be last….

I have to take a few days before I can test this — I was making the switchover tonight, and discovered that I’d forgotten a plugin-specific dependency on the home page. It knocks out most of the home page content, so I can’t just disable it and switch. I’ll have to add some additional fields to events that were being shown on the home page in a special way.

I’ll close the thread now, and just open a new one if I run into something I can’t figure out.

Thanks,
Dennis

[Dennis Freeze]

One more thing: I didn’t disable the theme before I posted the message, since it was just backend stuff. So I tried it anyway now, and the search works properly. I didn’t know that a theme could affect backend code — how do I figure out the problem?

[Dennis Freeze]

OK, some good choices. A couple of clarifications to help decide which way to go:

1. The first choice (using the WordPress export for the 3 custom post types) sounds like the easiest, as long as all your info is contained in posts and postmeta…. I’m guessing from your suggestion that it is self-contained, so this one is trivially easy. Right?

2. Emitting my own CSV would be OK — I’ve done a lot of stuff with CSV files (in and out of WP), so it’s mostly just identifying the right functions in your code to process the data. I’m assuming I’d use the Event title to locate the record when processing the CSV file, but I’m sure there’s more to it if you’ve got recurring events (and my client has a lot).

Not familiar with WP_CLI or Duplicator, but I’ll have a look if the first approach doesn’t work.

[Author]

Posts