Forum Replies Created
-
AuthorPosts
-
October 8, 2014 at 8:04 pm in reply to: Unable to load Enfold Demo following WordPress v4.0 update #332662
Christian / Kriesi Team:
I suspect it’s a WAMP localhost or a configuration parameter. If I figure it out (or not) I’ll add another comment to this support ticket. Your attached screenshot with table layout is similar to the demo import and how it’s mapped on my end.
Thanks for your feedback. Enfold v3.0 is top-shelf and so is your support forum.
Tom R
October 7, 2014 at 8:47 pm in reply to: Unable to load Enfold Demo following WordPress v4.0 update #331882Arvish:
I tried your suggestion with increasing memory. It had no effect on what I’m experiencing.
I’m scratching my head that with the tens-of-thousands of Enfold customers that the Kriesi team hasn’t heard of this going on with v3.0. I wonder what I’m doing that could be causing the problem. But, again, it’s the Enfold demo data that is mapping the MySQL database so strangely (see my thread above). It happened again with the test of the demo here. In my opinion, something happens during the demo import placing critically important “siteurl” and “home” field data in the wrong places.
I hope someone from the Kriesi team takes a closer look at this. It must be hectic with the release of v3.0 and all.
Thanks, Tom
October 5, 2014 at 8:09 pm in reply to: Unable to load Enfold Demo following WordPress v4.0 update #330535Devin:
Thanks for your your reply.
I did two (2) follow-ups. The first one I installed a new WordPress v4.0 instance on my localhost dev platform. Then, I imported a MySQL database from a website that I am going to migrate to Enfold. I installed Enfold v3.0. The result; I was able to generate a homepage successfully.
The second follow-up was doing a the WordPress v4.0 “5-minute install” with Enfold v3.0. I successfully generated a sample page. Next, I did an Enfold Demo Import using the Default Demo. I am unable to run the demo on my localhost dev platform. I continue to get (after a considerable delay ) the “Connection was reset” message. I happened to check the database with the demo import, too. It has a very odd wp-options layout:
- Page 1 option_id 1 has an option _name of “siteurl”
- Page 2 option_id 2 has an option_name of “home”
All other WordPress databases I’ve ever seen have the option_name “siteurl” on page 1 of wp_options in option_id 3 and option_name “home” on page 2 in option-id 39 of wp_options. I believe you have some kind of demo import issue that would affect access wherever the demo site is hosted.
Please look into this further and advise. Your help is appreciated. Your theme v3.0 is otherwise a superb product from what I can tell.
Regards, TDR
-
AuthorPosts