• Resolved wp_account_hs

    (@wp_account_hs)


    I installed wordpress and activated theme Hestia 2.0.5, works fine (free version, not pro). Today updating theme to 2.0.7: complete crash. Browser says: internal server error, http 500.
    Browserwindow empty and I cannot access cms

    Other websites on the same server work fine.
    Deactivated by ftp all plugins, makes no diverence. Deactivated child-theme, no diverence.
    There is a .htaccess file in httpdocs
    php version running on the server is 5.3.29
    This is quite old but Hestia 2.0.7 should be compatible with version 5.3 –> 7.2

    Please help, what can it be?

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter wp_account_hs

    (@wp_account_hs)

    And I use wordpress version 4.9.8

    kind regards,

    Henriëtte Santing

    rodicaelena

    (@rodicaelena)

    Hi @wp_account_hs,

    I’m sorry to hear you encountered this problem. I tried updating from Hestia 2.0.5 to 2.07 on a server with PHP 5.3.29, and everything seemed ok.
    If you’ve tried that update when Hestia was active ( not the child theme ) and is still not worked, I’m not sure, what could have been wrong. Is there a small possibility that it can be just a temporary server error, and trying again, should work, if you have the possibility to try this again?

    Regards,
    Rodica

    Thread Starter wp_account_hs

    (@wp_account_hs)

    Host has updated php version to 7.2

    Now it works!

    🙂

    Thread Starter wp_account_hs

    (@wp_account_hs)

    I’ve made a new wp-site for a client. It has a very low rating, but it’s a perfectly, heathy, new site. WordPress latest version, theme Hestia latest version, and a child theme of my own. I did everything by the book.

    So I did Google Search Console –> url inspection
    the rapport says: page has issues, not mobile compatibel

    live url test google search console: Googlebot can not load many .css and .js

    So because Googlebot can not load many css, it sees the pages without graphic layout and then it says for example: the links are standing to close to each other.

    My robots.txt is fine, I wrote for example:

    User-agent: Googlebot
    Allow: .js
    Allow: .css

    there’s noting that says disallow wp-content or wp-includes.

    then I wrote this:
    Allow: /wp-content/cache/*.js
    Allow: /wp-content/cache/*.css

    no difference, I tried many things
    At the end I wrote a ‘allow’ with a specific path to a specific stylesheet the robot could not load …

    no difference, its not about the robots.txt

    Has anybody heard of this problem before? Has anybody any ideas?

    Regards, Henriëtte

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘activate theme Hestia 2.0.7: immediate crash. Browser says: error http 500’ is closed to new replies.