Home › Forums › WoodMart support forum › 500 error after migration

500 error after migration

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • March 18, 2018 at 6:48 am #46720

    FabricDigital
    Participant

    Hi there,

    Have a 500 error after migrating it from our development server to production. I zipped up the directory and copied SQL across manually. I am able to isolate the issue down to the theme because it works when I change the theme to another.

    March 18, 2018 at 8:35 am #46731

    Artem Temos
    Keymaster

    Hello,

    500 Internal Error says about some issue on the server and can be caused by different things. Anyway, to understand its nature you need to see your server error logs or enable PHP error display on the website. If you can’t do this, you need to contact your hosting provider for help in this question. Here is an article that may help you understand the error better http://www.wpbeginner.com/wp-tutorials/how-to-fix-the-internal-server-error-in-wordpress/

    Regards

    March 19, 2018 at 7:51 am #46962

    FabricDigital
    Participant

    Looks like the error message is:

    PHP Warning: file_get_contents(https://WEBSITE/wp-content/uploads/2017/06/004-furniture.svg): failed to open stream: Connection timed out in /home/WEBSITE/public_html/wp-content/plugins/woodmart-core/post-types.php on line 368

    Very weird as I have a staging directory that is on the exact same server and it works just fine, when I put in to the Public_html folder it doesnt work.

    March 19, 2018 at 8:15 am #46973

    Artem Temos
    Keymaster

    It may happen if the file no longer exists, has incorrect permissions or file_get_contents function is disabled on your hosting server.

    March 19, 2018 at 8:32 am #46981

    FabricDigital
    Participant

    The file is there, it has the exact correct permissions and file_get_contents is enabled on my server as it works on a different sub directory.

    March 19, 2018 at 8:59 am #46988

    Artem Temos
    Keymaster

    In this case, you need to contact your hosting provider’s support and ask why this error occurs. There are no any issues from our theme side.

  • Author
    Posts
Viewing 6 posts - 1 through 6 (of 6 total)