[Hunch]

This reply has been marked as private.

[Hunch]

@Tomglover

Yes there’s actually a few unofficial ones. You can try:
* Keko – http://www.kekaosx.com/en/ (free)
* iPackr – https://www.macupdate.com/app/mac/38498/ipackr (free, get the iPack mac store app for password files)

There’s also Archiver which is a paid app: http://archiverapp.com
There used to be a couple of others (7zX etc) but they stopped developing them a couple of years ago, so give these a shot.

Good luck!

[Hunch]

@ww2010 :

“Demo content is not integral to the theme working, but an option”
Pretty clear a lot of us obviously brought it for this reason

Yes some have bought this theme with the want of adding the demo content, but my quote has nothing to do with that. It has everything to do with the fact that the issues people are having with not being able to import that demo content do not mean that the theme itself is faulty or broken. Or that the theme installation doesn’t work. It is a content upload issue.

@vkialka
This is why I was suggesting for some issues people might be better off to start a specific thread, because every time someone answers or adds on to a thread with a post, it will bump it back to the end of the queue and will further delay the time the request gets seen by @SwiftIdeas support. Especially if it’s a popular thread like this.

—

The images are huge and to be retina ready some of them have to be. If you really don’t need the entire shop content, dummy comments, etc replicated on your own site, the ALT file should be more efficient and suitable for most people’s needs – and there’d be less dummy content to delete at the end.

I’ve added both (Full & Alt) and the ALT file was actually adequate, faster to upload. You don’t get ALL the shop products but there are some included and it is more than enough to get you started if your primary intention for using demo content is as a basis to model your own site on. (If anyone is still debating which to use and having issues).

[Hunch]

I agree that perhaps the documentation instructions for uploading the XML and other sections could be updated/expanded upon. Pictures would help guide people a little better, but contrary to some previous claims this is not a broken theme issue. The theme works fine. Demo content is not integral to the theme working, but an option. Buyers should/can read the feedback first to make an informed purchase.

Again, the theme works fine. The full XML is really large and many other high content theme demos from other developers often suffer similar issues with XML uploads. You’d be surprised at what can and cannot affect your installs with differences in various servers, shared servers, WordPress core, human error, knowledge, bandwidth, security, plugins, conflicts et al. People who may not understand the dynamics of servers and hosting systems are often too quick to blame everything else. Hosting set ups are beyond the control of theme creators, so it is up to end users to ensure theirs is adequate. There is not always a one-size-fits-all solution else it would have been provided.

For those who need smaller XML file chunks, there is a link to a program you can use to do it yourself in this very thread – the one mentioned 2-3 times if you read back a couple of pages. That way you have control of what size you need to make them. Simple.

Others spend $60 and seem to expect the World in free support – offering support is good business sense and an added bonus, but not exactly a requirement. Some developers provide little to no support. The @SwiftIdeas support has been most often prompt and helpful with the issues and questions here and on the theme pages. But they are not magicians and one cannot expect every server or set up is going to act the same – there are ALWAYS exceptions to the rule. Also they have stated several times that they do not answer on weekends, so yes, sometimes there will be delays.

A faster and far more productive way of getting issues escalated & resolved is by giving more specific details, providing logins where required and politely/calmly asking for some help (instead of venting frustrations as occasionally seen throughout the forum and theme page discussions). Start a thread even. I understand it can be frustrating, but some of these posts come across more like impolite complaining which borders on a whinge – I could hardly blame them if they didn’t bother to help. One catches more flies with honey than vinegar.  

That said, I do hope you all get it sorted out.

[Hunch]

@s2dgn:

Sometimes it depends on your server (shared, not shared, etc) too. Some hosts will override the settings that you change in php.ini but yours don’t seem to at least. [Changes to the .htaccess file, to dictate the recommended values can get around this, but I’d generally try that last].

If you change it yourself, create or edit the php.ini settings file, make any changes and save, then uploading it to the wp-admin folder may make all the difference. It may not be recursive.

Also if you are getting time out errors or similar you could also try to increase this additional part of your php.ini file:

default_socket_timeout = 700

which can help if your upload bandwidth is being iffy.

You could also increase the rest of the settings by even more than what was recommended in the theme documentation and see if it makes a difference. You can always change them back later (after import done). Try doubling it or using the following values:

default_socket_timeout = 700
max_execution_time = 7000
max_input_time = 7000
memory_limit = 512M
upload_max_filesize = 200M

Then use the “WordPress Database Reset” plugin and start over as above.

If that doesn’t work (which if all things are correct it really should), you can alternately split the XML file using the windows based program as mentioned above.

[Hunch]

@westcoastsurf: yes that utility is handy and saves lots of time to do manually.

@hustle1: if all goes to plan it and it works properly it should look exactly like the demo.
If you are unsure about doing this on top of the work you have already done, then you could always install WordPress into a subfolder with this theme, and import the demo content to this separate theme install if all you want is to reference it & deconstruct.

[Hunch]

@SwiftIdeas – Ed: good idea. No worries 🙂

@s2dgn
– which file were you uploading?
– what host are you with?
– Is your wordpress install in the root folder or a sub-folder?

@westcoastsurf: yes everything between the <channel> tags is considered the body of the xml file. To make it cleaner you could remove the unnecessary text so it looks like this:

<?xml version="1.0" encoding="UTF-8" ?>

<rss version="2.0"

	xmlns:excerpt="http://wordpress.org/export/1.2/excerpt/"

	xmlns:content="http://purl.org/rss/1.0/modules/content/"

	xmlns:wfw="http://wellformedweb.org/CommentAPI/"

	xmlns:dc="http://purl.org/dc/elements/1.1/"

	xmlns:wp="http://wordpress.org/export/1.2/"

>

<wp:wxr_version>1.1</wp:wxr_version>

<channel>

*ADD ITEM CONTENT HERE*

</channel>

</rss>

Though you prob already know, incase others don’t and are doing the same: don’t forget to always save it in a UTF-8 text format with .xml extension.
You can validate your XML’s using something like this if you just want to check it before you upload or gzip it (validator mostly works).