Review Changed – Explanation below
-
[Vote Changed – See replies below]
Trying to import an XML file with test data from wptest.io. Does not work. Asks for tons of settings. Cannot select all items to import. Such a simple thing so complicated.
-
You’re supposed to use this plugin to import that data: https://wordpress.org/plugins/wordpress-importer/
Not WP All Import.
So WP All Import does not import any XML file like it says everywhere and like it comes up in search results everywhere and like I can see it says next to the logo?
So why not make sure and let potential users know that WP All Import is NOT for any XML file?
Regarding the infamous WP Importer: Have you seen the unanswered support threads? Have you seen the ratings? That plugin is foobar and like so for months.
Would not be here if WordPress.org would get their act together and support a plugin with 1M+ installs. But apparently no one over there feels responsible or can be asked to either reply to support threads or actually patch the darn thing.
So either pay for premium plugins that then also are apparently not for importing XML files or be left on one’s own.
You see like so many other people out there importing test data into a theme is essential for developing a theme. Not being able to do that is messed up.
Loosing highly valuable time with trying to get the test data imported rather than actually working on the theme. Trying alternatives but like you say, even WP All Import does not seem to be able to import that XML file from wptest.io.
Then what plugin can do that?
If you point me to a working alternative that works out of the box and does not have to be purchased I will edit my rating to 100% since you helped me.
Otherwise it would be a great idea to inform potential users that WP All Import does not import any XML file.
What didn’t work when you tried to import the file with the WordPress Importer? I’d imagine it’s an easy fix.
See here what I have tried to far please:
https://wordpress.org/support/topic/cannot-import-xml-file-from-wptestio-wordpress-importer-fails-local-live?replies=5Also here:
https://wordpress.org/support/topic/save-your-time-and-nerves-keep-clear-of-this-rubbish?replies=2Any clues?
Look, I also don’t want to make you debug something that is not yours. If you can help great, if not, I will try and either get this thread deleted or give you a 100% review and explain the issue. This has nothing to do with you so why should you care. The fact that I tried to import the XML file with your plugin and it also did not work does not mean you plugin does not work generally, it is just not suitable for this kind of XML file. Though for what type of XML files is it? I don’t know and at the moment I don’t have time to find out. Bottom line, I am always fair and don’t want to rate you down for something that is clearly NOT your fault. If you can help somehow great and thank you for the time invested in debugging a foreign plugin.
You let me know how you like to take it from here and I will happily accept help or a simple “no”, as you prefer.
Thank you.
Those errors are not a result of a problem with the WordPress Importer plugin. They are a result of a problem with your server settings.
I know you think you set your max_execution_time to more than 60 seconds but if you continue to get the error as described in the threads it actually means you haven’t actually successfully changed the setting. I’d guess that you’re editing the wrong config file or you need to restart the server.
If you don’t know how to do server admin tasks or debug PHP errors, I’d recommend you either get help from a professional server admin or instead, test the import on a web hosting provider where you can simply e-mail their technical support and ask them to fix any errors you might get.
More on the purpose of WP All Import:
If you have flexible needs as to where the data in your file goes you use WP All Import. You have to configure your import settings though – it takes effort but the result is that you can get any data in your file into any place in WordPress. If you have a file with an arbitrary structure, just map the fields in your file to the appropriate places in WordPress and run your import and the data will go right where you specified.
The reason WP All Import is not right for your use case is because you have a file that is already set up to work with the WordPress Importer. WP All Import WILL import this file but the problem is you have to configure all the settings and drag & drop each thing to the right place and import each custom post type with a separate import, etc. It would be much easier to just use the WordPress Importer – you won’t have to configure any import settings because the file is in the specific format required by the WordPress Importer already.
Thank you for your in depth reply.
I have in fact had two server admin guys look at the issue. One from the WAMP forum and one from the XAMPP forum and both confirmed that the settings have been set correctly or at least adjusted to higher values.
Also the plugin https://wordpress.org/plugins/wordpress-php-info/ confirms that the settings used are reflected in the php settings/configuration. So if this plugin confirms the proper values why is the plugin still throwing that message?
All this is quite frustrating and leaves not only me but also true professionals puzzled.
Thank you for taking the time to explain more about WP All Import, I do fully understand now what this is for and that importing with it has to be set up.
Thank you indeed for your help, this is much appreciated.
Oh and last not least, if you check the support threads for the WordPress Importer you can see that many other people are also having this problem, so it is not a single machine where it does not work.
Best Regards
I’m puzzled as well.
This is just a short in the dark, but try opening the wordpress-importer.php file and removing line 106. It reads add_filter( ‘http_request_timeout’, array( &$this, ‘bump_request_timeout’ ) );
Comment it out or delete it entirely.
If that doesn’t work… I don’t know have any clue how to solve the problem.
Fatal error: Maximum execution time of 60 seconds exceeded in root\wp-includes\class-http.php on line 1597
It seems like something is setting the max_execution_time back to 60.
The WordPress Importer is not what is displaying the message. A max execution time error is displayed by PHP itself – NOT the plugin.
You hit the bull’s eye. Simply by commenting that line it does the import, though one has to import twice, the first time it will throw an error that some files could not be imported, then the second time it will import the missing ones and the ones that are imported already are skipped. I can live with this for the time being.
How can I reimburse you for your great help?
None of the people from the WP Support forum felt like giving ANY sort of reply nor did anyone in the WP Importer Support or Review site felt like it would be “cool” to give a reply, even if not being helpful, just a simple, “try this” or “try that” or anything really..
Shame on WP.org in that sense and the conclusion I draw from this is if things go really bad it is better to have a paid pro on hand for debugging/code auditing rather than trying and waiting for a reply from either the Support Forums or the plugin creator IF it is wp.org that made the plugin. Now I might be terribly wrong about this assumption and I HOPE that I am wrong only hearing great things from the WP community so far, though this definitely showed me the contrary.
Naturally, trying to debug this as a pure beginner in WP it was a horror scenario come true. Only THANKS to your “shot in the dark” this got resolved to about 80% since one always has to still import twice but at least the data gets imported and can be used for theme development now.
So yeah, how can I show my appreciation for your help to you?
Very Best Regards
- The topic ‘Review Changed – Explanation below’ is closed to new replies.
