This solutions don’t work here … same error … “Invalid post type” when i upload gz file!
Hi, and what theme do you use? One of my themes? ( http://themeforest.net/user/webmandesign/portfolio ) If so, please log a ticket on http://support.webmandesign.eu
I found the answer on http://wordpress.org/support/topic/failure-to-import-and-invalid-post-type-errors same as RockNRollaDesigns answer I gzipped the xml file and re-import it. it took a little long time to import but finally it works
Supercool, I’m glad the RockNRollaDesigns’ solution works fine!
Thanks very much for sharing the result with us!
3) Change the “Archive format” to gzip and hit “OK”. You’ll now see your file with a .gz extension on it.
4) Try to import/upload the file again (selecting the .gz you just created not the .xml file) and it should work.
Wou, if this works, I eat my head, guys! And would really love to hear the explanation too
Thanks very much for sharing!
I don’t think this is resolved issue yet, but it haven’t happened since to me.
As tips for you guys: firstly, activate the theme the XML is meant for (and all the possible required plugins) and then try to import the XML file.
Tip for theme authors: I know this doesn’t really resolve the issue I’ve started this thread with, but I found a good practice to move all downloadable content (images for example) in XML file at its end. By default WP creates this (or smilar) XML structure: first are imported taxonomies, then downloadable media and then content (also with downloadable media somewhere). So what I do before I distribute the theme demo XML is just open the XML file and cut and paste all the attachments post types at the end of XML file (surely before closing tags
</channel></rss>). This helps when there is a problem with importing images as all the text content is imported at the beginning of the file and all attachments are being downloaded just after this text content is imported. At least something
Thanks for sharing.
Well, that’s why I opened this thread. I was frustrated that I couldn’t find a solution for this anywhere. Still don’t have it and my customer went on by creating his pages from scratch…
I wasn’t able to recreate the error since which makes is more misterious one!
Thanks for the reply. This shouldn’t be a problem once the custom post has the same ID – basically same everything
As for whether custom post is theme related I don’t agree with that. In my opinion it belongs to plugin, but if we (WordPress theme authors) want to sell… That’s for the whole new thread
Post types can have the same display name, but different “ID” (the first param of the register_post_type() function) – maybe that’s the reason?
No, not the case. They are the same. That’s why it puzzles me. But anyway, it worked for me now and I’m sure the customer didn’t try to import demo content from my other theme as he only bought the one so I really don’t understand why there are those import errors…
My other thought would be could it be some server settings? I mean maybe the XML file (which is around 700KB) was not imported into WordPress in whole? But wouldn’t improter script throw off some error about invalid XML then?
Thank you for reply. I realized I’ve installed demo content from different theme of mine. But those themes use the same post types so it doesn’t matter? Well, anyway I tried now and was able to install demo content fine.
However, I’ve checked the screenshots my customer sent me and he has got the theme installed, active but he still get those errors. I can’t see why…
Also thank you for your answers! I didn’t know about 1) so thanks for the tip and I agree it is good behaviour.
I have a “weird” issue here.Recently I had couple of support calls for demo content of my themes. In both instances the WordPress importer returns many of similar errors:
- Failed to import post tag
- Failed to import (yes, this one is plain just like that)
- Failed to import “XYZ”: Invalid post type
Even I was able to replicate the issue when installing the demo content (and also with other ThemeForest themes I’ve bought) on localhost on my computer. It was working perfectly fine before. The only change I can think of was that I updated my theme demo websites (from where the demo images are being downloaded) to current WordPress 3.5, but I don’t think it should be a problem.
Though, when I try to install the demo content on the same server where my theme demo websites are installed, everything works fine.This rises several questions for me and I was wondering if anybody can shed a light on them:
- Why there are these “invalid post type” errors during the import process? As far as I know, WordPress takes the post types directly from XML file regardless what theme is installed / what post types you are actually using. The not-existing post types should be just saved in database, so they should be imported. Why does WordPress have issues with this? (And BTW, there is no error in actual XML file – I’ve run through it all and as I’ve mentioned, the erroneous imports occurs intermittently while importing the same file.)
- During import process WordPress downloads only images and attachments from external server. All other data are being taken from XML file, right?
- As of previous question: could WordPress import fail due to bandwidth limitation to my theme demo website?
- Can somebody explain how the WordPress import works? How it creates WP data, how it imports images (if it import also all created formats or just the main image that is formated during the import process)?
Thank you in advance for any suggestions/ideas!
The above filter gets approved finally.
Although I thought that was the last thing before releasing the theme for selling as reviewer already moved to code stage (http://notes.envato.com/general/submission-tip-understand-the-themeforest-reviewing-process/), that’s not the case with me. He’s back in rejecting design and even theme demo website (?).
This is funky long run as I’m back at the beginning…. However I don’t know if I have energy to do something about it after several soft rejections and long communication via Envato support. I’m preparing for the last strike though
Thanks for all your replies guys anyway.