500 internal server error

  • Resolved rebl27

    (@rebl27)


    7 years, 9 months ago

    It’s working now because HostMonster restored my files from one of their backups.

    I had opened the admin section of the site and was researching how to remove the “0 comments” under the post in a listing. I had made no changes. I opened the file manager (HostMonster) and was viewing (in view mode, not edit) some of the template files. When I went to the site front end, there was a 500 internal server error displayed. When I tried to change the screen in admin, I got the same error. I was locked out of both the front and back end.

    After trying half a dozen (at least) fixes that didn’t fix anything, I contacted HostMonster. Their tech said, “themes/hestia/inc/admin/about-page/class-hestia-about-page.php on line 105 line has issues” and recommended that I contact you. As I said, HostMonster restored my site from a backup.

    I love this theme and most likely, will be sticking with it. But this is one of several problems I’ve encountered, two of which I’ve posted about. Nearly 3 weeks ago, I posted about a problem with losing data when switching back to Hestia after going to another theme to troubleshoot a plugin problem; I never got a response. I don’t know if it’s still a problem because I’m hesitant to change themes again. I posted about a second problem, but solved it after several hours of research. It involved the “/blog/” part of the post address, which I’d never seen before and couldn’t find anywhere.

    The theme’s structure perplexes me, which I know is not your problem, but mine. I’ve never worked with a theme with template pieces, and I’m not sure where to look for the code that needs to be modified. Some of the documentation seems to be for a previous version because the code is not where the documentation says it is, which is where I would expect it to be. So I’m a bit frustrated. It would be helpful to have a good reference about how the templates, template parts and the page phps fit together. I read the WordPress codex, but that’s too technical for a non-developer like me.

    A lot of these comments should go only to the developers, but your website’s support links create an endless loop that never allows one to post anything. I understand that you don’t have a lot of time for handling problems for users of the free version, but please just put that out there, and take away the loopy links.

    I’m not usually so surly, but it’s been a long, crazy-making day. Again, despite my complaints, I do like Hestia a lot.

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

Viewing 1 replies (of 1 total)
  • rodicaelena

    (@rodicaelena)

    7 years, 9 months ago

    Hi @rebl27,

    Thank you for contacting us and sorry for the late reply. We do our best to answer everyone but sometimes this is a bit more difficult.
    Regarding the problem with the 500 internal server error, that was most likely caused by the fact that you are using a child theme, and you’ve probably tried changing its name or recreating it during the time the child theme was still active. And indeed there is an if clause in Hestia’s code, at that line suggested by you, where this case can cause problems.
    We just fixed that, and the fix will be available in the next release.
    Regarding the problem with the lost data during a switch with another theme, unfortunately, there isn’t much we can do there. Hestia’s options are built as theme mods, meaning that they are kept in the database as just related to Hestia, and at a theme switch, the theme can’t know how to get those options back, the only solution would be to add a simple import script in the code, where you would need to get the options back ( as they should still be in the database ).
    So, my advice would be to not switch themes, without making sure you are also migrating the content.
    Regarding the issue with the “/blog/” part of the post address, I’m not sure what the exact problem was, but usually, those can be fixed by regenerating the permalinks in WordPress.

    I hope I was able to help you.
    Regards,
    Rodica

Viewing 1 replies (of 1 total)

The topic ‘500 internal server error’ is closed to new replies.