[researchreturnsParticipant]

Just installed X (ver 4.3) on the latest WP update 4.4.1 and I’m not sure how to get the Demo Content uploaded. I imported the XML file per the instructions in the comments at the beginning of the x-demo-content.xml file. I received some error messages which I’ll post below.

The Demo Content page reads: “No demos found. Refreshing this page may resolve the issue. If it persists, please review the connection issues article in our Knowledge Base.”

I’ve read and watched the resources available at: https://community.theme.co/kb/demo-content/ however my problems seem to be in that I don’t even have the option to select either Standard or Expanded options. I’ve read the documentation and followed the theme installation via FTP. This page seems to be a broken link: https://community.theme.co/demo-content/

After assigning authors and selecting to download attachments, importing the x-demo-content.xml returns these errors now:

“Import WordPress
Page “Home” already exists.
Page “Blog” already exists.
Failed to import Media “placeholder”
Failed to import Media “placeholder”
Failed to import Media “placeholder”
Failed to import Media “placeholder”
Failed to import Media “video-placeholder”
Failed to import Media “placeholder4”
Failed to import Media “placeholder5”
Failed to import Media “placeholder6”
Failed to import Media “placeholder7”
Failed to import Media “x-demowelcome”
Post “5 Reasons You Need The X Theme” already exists.
Post “Audio With Image” already exists.
Post “Audio Without Image” already exists.
Post “Little Red Riding Hood (Embedded Video)” already exists.
Post “Have You Heard Of Them?” already exists.
Post “Thought For The Day” already exists.
Post “Standard Post With No Featured Image” already exists.
Post “Beautiful Gallery Post” already exists.
Post “Image Post” already exists.
Post “Affiliate Marketing 101 (Self Hosted Video)” already exists.
Portfolio Item “Riomaggiore” already exists.
Portfolio Item “Pike Place Market” already exists.
Portfolio Item “Bridge to Gucci” already exists.
Portfolio Item “Stockyards Hotel” already exists.
Portfolio Item “San Francisco Bay Bridge” already exists.
Portfolio Item “Red Miami Sunset” already exists.
Portfolio Item “South Beach” already exists.
Portfolio Item “Have You Tried This?” already exists.
Post “Standard Post With Shortcode Goodies” already exists.
Page “Page” already exists.
Portfolio Item “Monterrey Blue” already exists.
Portfolio Item “Beach Town” already exists.
Portfolio Item “Big Sur Milky Way” already exists.
Portfolio Item “Black and White” already exists.
Portfolio Item “Keyhole Arch” already exists.
Portfolio Item “Roman Forum” already exists.
Portfolio Item “Sierra Farm” already exists.
Portfolio Item “Skyline” already exists.
Portfolio Item “Make It Count” already exists.
All done. Have fun!

Remember to update the passwords and roles of imported users.”

Thanks for your help!
Michael

[ChristopherModerator]

Hi there,

Would you mind providing us with login credentials so we can take a closer look? To do this, you can make a post with the following info:

– Link to your site
– WordPress Admin username / password

Don’t forget to select Set as private reply. This ensures your information is only visible to our staff.

Thanks.

[researchreturnsParticipant]

This reply has been marked as private.

[researchreturnsParticipant]

This reply has been marked as private.

[FriechModerator]

Hi There,

May we know where did you get the x-demo-content.xml file? The video on the link you provide above is referring to Addons > Demo Content which has the issue.

Would you mind to confirm the following to your hosting as well.

– Ensure my site can reach this domain: community.theme.co
– Ensure cURL is working, and allow_url_fopen is enabled.
– Ensure PHP is configured with the latest CA Root Certificates.

Let us know how it goes. Cheers!

[researchreturnsParticipant]

Web upload of the theme didn’t work most likely because of the group/ownership issues I mentioned above. So I manually uploaded the theme via FTP, which worked for the most part save the Addons > Demo Content portion. Again, this error is what appears on a fresh install upload of X under Addons > Demo Content : “No demos found. Refreshing this page may resolve the issue. If it persists, please review the connection issues article in our Knowledge Base.”

In the x_package zip file, there’s a file x-demo-content.xml. I tried using Tools>Import>Wordpress Importer to import that xml file which gave me the error messages I posted above.

Searching documentation and old forum posts its unclear to me what the most current process for setup is. Is using the WordPress importer from an older version of X? Should it just run without importing the XML file now? The Demo Content page makes no mention of importing the XML file and I can’t find documentation of this process other than in the comments of the XML file itself.

I emailed my hosting provider about those 3 queries, thank you. I also ran phpinfo(); myself and can confirm that cURL is enabled (7.44.0) and allow_url_fopen is “On” (both local value and Master Value).

Is there any other code I could run on my site to answer your other two questions quicker? Response from my hosting provider is not as prompt as I would have hoped – certainly not as quick as the team at X 🙂

[Paul RModerator]

Hi,

It would be best if we go in and take a closer look first.

When I go to the link you provided above it just shows the phpinfo.

Would you mind providing us with the following info:

– Link to your wordpress site
– WordPress Admin username / password
– FTP credentials

Don’t forget to select Set as private reply. This ensures your information is only visible to our staff.

Thanks

[researchreturnsParticipant]

This reply has been marked as private.

[RadModerator]

Hi there,

You’re right, services have their own owner. Web server (apache) and FTP Server has their own different owners or group. You’re processing it through web server and accessing the file system that belongs to FTP group. Hence, that’s where the issue begins, and your web server can’t write to the file system.

I’m not sure if we can really help since it’s your hosting limitation. Your site should be installed with the correct group or permission at the very start.

Though, I don’t see this kind of problem with another hosting. It’s probably just connected to your hosting configuration.

Thanks.

[researchreturnsParticipant]

This reply has been marked as private.

[researchreturnsParticipant]

Another thing I noticed, per my host’s email: “The server would have been able to reach community.theme.co if https was being used, but if not, we do have to whitelist that (which has been done now). Because of how frequently WordPress gets exploited, we have had to take a strict stance on how we allow WordPress sites to communicate with the outside world.”

I’m not using https, so it seems I have to “whitelist” specific outisde domains for WordPress to specifically communicate with. You noted community.theme.co which my host whitelisted. I was browsing the code of x-demo-content.xml and that domain is not contained once, however, 118 instances of theme.co exist. Would that be the correct domain to ask my host to whitelist? Are there any other relevant domains I should whitelist?

Thanks.

PS.
I went through the x-demo-content.xml file and in addition to the 113 instances of calls to theme.co, the following URL’s show up. Would I need to “whitelist” all these URL’s or just theme.co?

http://wordpress.org/?v=3.8.1
http://wordpress.org/export/1.2/excerpt/
http://purl.org/rss/1.0/modules/content/
http://wellformedweb.org/CommentAPI/
http://purl.org/dc/elements/1.1/
http://wordpress.org/export/1.2/

[RadModerator]

This reply has been marked as private.

[researchreturnsParticipant]

I had to step away from this for a bit, but I’m trying address my issues again.

I got my host to “whitelist” theme.co.

A couple observations. I still feel like I’m having ownership/permission issues. For example, I was having problems installing the X update. After getting theme.co whitelisted by my host and then temporarily changing the permissions of my “X” theme folder to 777, the theme updated without a problem.

It seems to me that this workaround solution could work for initializing the theme data. Are there any specific folders in the X or WP folder structure I could change the permissions to 777 temporarily in order to get the theme data/files to download?

Or another way of asking, what folders/files are affected when the theme data first is initialized?

I tried setting my entire website/WP folder structure to 777 permission and that basically broke the site for reasons I’m not sure.

Also, my host confirmed that they are indeed behind a firewall. Other than theme.co are there any other links that should be whitelisted? For example, browsing some of the code, I noticed calls to:
http://themeco-demo-content.s3.amazonaws.com/x/

Is this a link that should be whitelisted or is that irrelevant? It seems like the download source for the theme files to me, is that true?

Thanks!

[Paul RModerator]

Hi,

Yes, your host needs to whitelist themeco amazon s3 for the demo to work.

Thanks

[researchreturnsParticipant]

Thanks for the feedback. This solved my issues and I have been working with the great demo content the last couple of days!

Your error page makes references to unlblocking theme.co if the host is behind a firewall, I would just like to recommend adding this Amazon url to that page as well in case anyone is having the same problem as I did!

Thanks again for your help!

[Author]

Posts