Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • October 5, 2014 at 8:24 am #330400
    TDR_ent16

    Enfold Team:

    I can only run an Enfold demo on WordPress v3.9.2 not WordPress v4.0. After updating to WordPress v4.0 and running the site in my localhost development sandbox I receive a “Connection was reset” page from Firefox or “The webpage is not available” from Chrome. The only plugins I have activated are bbPress and WooCommerce (suggested for running your demo content.

    If I revert back to WordPress v3.9.2, build the database from scratch (5-minute install), select a demo import (I’ve used either the default demo or the small business- flat), and then start the enfold site it runs without a glitch. If I use my admin page to update to WordPress v4.0 and then run Enfold, though, I will receive a “Connection was reset” page from Firefox, again.

    I have also taken a WordPress v4.0 environment, built the database from scratch (5-minute install), selected a demo import of Enfold, saved all changes from the Enfold admin area, and tried to access the Enfold site -unsuccessful, too.

    What are your suggestions to remedy this?

    Thanks, TDR

    October 5, 2014 at 3:17 pm #330487
    Devin

    Hi TDR_ent16!

    Are you using Enfold version 3.0 locally? Enfold 2.9.2+ is needed to work on WordPress 4.0 because of a change in the updated WordPress version.

    Best regards,
    Devin

    October 5, 2014 at 8:09 pm #330535
    TDR_ent16

    Devin:

    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

    October 7, 2014 at 11:12 am #331484
    Arvish

    Hey!

    Add this line above the “/* That’s all, stop editing! Happy blogging. */” comment in wp-config.php

    define('WP_MEMORY_LIMIT', '128M');
set_time_limit(0);

    Then try importing the demo data again.

    Let us know if it helps.

    Regards,
    Arvish

    October 7, 2014 at 8:47 pm #331882
    TDR_ent16

    Arvish:

    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 8, 2014 at 5:58 pm #332592
    Kriesi

    Hi Tom!

    I am afraid I have never heard or seen an issue like this. As for the options. Apart from the fact that what you describe seems to be fine to me ( see my demo import: http://cl.ly/XvJA ) the theme does not alter any of the options other than the ones starting with “avia” or “enfold”

    I am afraid I have no idea on how to reproduce this issues, especially since I am not a server expert :/ (And I would assume that this has something to do with the server, since no other user out of the 40.000 using enfold has reported the issue yet)

    If we can’t find the problem here we might need to wait if someone else shows up with the same issue so we can start cross referencing settings…

    Kriesi

    October 8, 2014 at 8:04 pm #332662
    TDR_ent16

    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 8, 2014 at 8:19 pm #332686
    Kriesi

    Thanks a lot, and let us know if you have an follow up information ;)

    Best regards,
    Kriesi

  • Author
    Posts
Viewing 8 posts - 1 through 8 (of 8 total)
  • The topic ‘Unable to load Enfold Demo following WordPress v4.0 update’ is closed to new replies.