How to disable the v2 wordpress-importer about wordpress-playground HOT 6 CLOSED

Did I understand right, you mean to basically clone the existing importWxr function to do the same stuff using the old importer?

Yes, that's what I had in mind. Another alternative solution would be for you to use the WP CLI for importing.

Is ImportFile and ImportWxr the same? I can't find any docs about ImportFile.

I'm not sure, I don't have experience with it. Maybe the source code can help you.

So I have to come back to my initial impulse and like to ask why the v2 is used here, while it is buggy, not well documented and not backwards compatible?

@adamziel might have the context.

from wordpress-playground.

So I have to come back to my initial impulse and like to ask why the v2 is used here, while it is buggy, not well documented and not backwards compatible?

Because v1 had even more issues. Sadly, there doesn't seem to be a single importer that would solve all the problems. I know folks in Automattic use at least three different implementations, depending on the use-case. What we really need here is a new, reliable WXR importer that would just work, stream-handle the incoming data, correctly parse character entity references, pause, resume on failure etc. @dmsnell's work on the HTML and XML parser will come handy here.

from wordpress-playground.

I'll close this issue since the question of disabling importer v2 is answered. I'm very aware of the limitations and would love to see a new reliable importer that would solve it all.

from wordpress-playground.

This is how the importWxr step works.

You could install the plugin by using the importFile step and use a runPHP step to execute the import similarly to how the importWxr step works.

from wordpress-playground.

@bgrgicak Thank you, this is the direction I hoped for. Let's see if I can fiddle this out.

1. Did I understand right, you mean to basically clone the existing importWxr function to do the same stuff using the old importer?

2. Is ImportFile and ImportWxr the same? I can't find any docs about ImportFile.

from wordpress-playground.

Two hours ago, I wanted to close this already, as I thought it might be better to go with the new Importer, instead of writing playgrounds steps by myself, but as longer I'm trying to use the v2 importer, things get worse and more worse.

So I have to come back to my initial impulse and like to ask why the v2 is used here, while it is buggy, not well documented and not backwards compatible?

The v2 importer is an un-neccesary burden for the playground.

from wordpress-playground.