Support » Theme: evolve » error 500

  • Hi,
    We uploaded a very large graphics file for testing as a slider (we had problems with image sharpness) and activated it in the bootstrap slider. After that the website reacted with an http error 500.
    When activating twentyseventeen and evolve plus the website works without problems, after activating evolve (version: 3.9.7) the http error 500 occurs again.
    Afterwards we uploaded the theme completely via FTP (binary), without success.
    Also the hoster cannot solve the problem.
    What options do I have to make the website run again with evolve (I have saved the evolve settings)?

    Best regards,

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

Viewing 15 replies - 16 through 30 (of 30 total)
  • @daeman23 Kirki framework is embedded so there is no need to install the plugin

    @romik84 our site uses Hostgator and our WordPress instance is set up for automatic updating. Typically both WordPress and themes and most of the plug-ins automatically update, and only once in the last three years have we had an issue (and it was a plug-in, not with the Evolve theme).

    Did a new Evolve theme version get pushed out last night or early this morning? If so, that coincides with our problems, because our site was working fine last night.



    I updated today morning so it may relate…I am investigating the issue now

    I have exactly the same problem and uns an autoupdate plugin. Without problems so until today.

    Working on a fix…will update soon…thanks for your patience



    Same problem. I updated from 3.9.6 to 3.9.7. No problem with backend but I’ve got internal error 500 or no error at all and a blank page (depending on browser).
    Fortunatelly I had a backup of the previous version and going back worked.
    Surely, I’ll check the forum before updating again… but I want to thank the author because he’s very fast in answering and checking/solving the problem.

    Please help me to test as it requires various environments. Edit file inc/admin/customizer/customizer.php line #1142:




    if ( is_customize_preview() ) {

    Please let me know if it solves the problem. thanks.

    One more confirmation that the fix works. Our web site is back up.



    hi romik, i still have the same issue.
    I installed the theme via wordpress (Versión: 4.0.5) and via ftp (Versión: 4.0.5) and even a older version and still happening the error.

    Put the code of my customizer.php but is not fixing the problem.

     else {
    			if ( is_customize_preview() ) {


    hi @comptels,

    please enable the WP debug mode and check the error log what exact error messages it writes. thanks



    thanks romik, but i turn on the wp_debug and wp_debug_log and this error dont create the file, so i assume there is no error in this case.

    Maybe we can talk by another chat, or email i give you my credentials and ftp account to check everything? thanks again.



    you might contact through the theme homepage.thx



    ok, i doit.. i hope you answer via email. thanks

    The 500 internal server error is not a WordPress-specific error. It is a general server error that may be related to your server settings or your WordPress files. Use the information in this tutorial to troubleshoot the 500 internal server error you are receiving.

    Here are the things you’ll need to troubleshoot.

    1. Your htaccess file may be corrupted. Try renaming it and see if that fixes the 500 error. If it does then the problem is in the htaccess file.

    2. You may have reached the memory limit on your hosting account. Try increasing the limit using one of the methods outlined in this tutorial:
    Check Your Plugins

    The first 500 internal server error troubleshoot is by deactivating all of your plugins.

    To do this log into your site files using FTP or going through cPanel.
    If you go the cPanel route, click on File Manager in your cPanel.
    if you get more information visit below given link:

    If there is an internal error, the first step is to view the log files. For Linux servers, the collection of error messages should be found at /var/log/httpd/error_log. It makes sense to reload the website to reproduce the HTTP error 500 code and observe how the log file is being created. This will help you find the source of the error quite quickly. Also consider which changes were made shortly before. In many cases, incorrectly programmed or incompatible plugins are the cause of error messages.

    Errors can also occur if you have not set permissions correctly for important files. In general, there are three types of rights:

    Read (r)
    Write (w)
    Execute (x)
    These permissions can be assigned for three different user types:

    Owner of the file
    Group of users
    All others
    The rights are specified either in the abbreviations r, w, and x, or in corresponding numerical values: 4 for read, 2 for write, and 1 for execute. They are added for each user type and specified one after the other: rwxr-xr-x (rwx for the owner, r-x for the group, and r-x for all others) or 755. This configuration (755) should be the default setting. If the permission assignment is set differently, an error may occur. You can change this with a command:

    chmod 755 filename
    If this change does not solve the problem, you can also release all rights for each group for test purposes:

    chmod 777 filename
    But only use this setting to locate the problem. Any user is allowed to rewrite the file, which is understandably a security risk.

    Next, check (if distributing the rights didn’t produce the error message) if your scripts are running correctly. Sometimes errors occur because the script files have been moved, renamed, or deleted. Also check the .htaccess file: even a syntax error – no matter how small – can cause an internal server error. An equally common error is incorrectly formatting the .htaccess file. This must be created in ASCII or ANSI format, not in Unicode. Therefore, write the file in a text editor such as Notepad, Notepad++, or Sublime Text, and not in a word processing program such as Microsoft Word. To test whether the file is responsible for the error, you can temporarily rename it and reload the website. The server now won’t access .htaccess when loading the website. If you no longer receive the error message, you can repair the file or create a new one.

    A timeout can also lead to an error message. In this case, it isn’t a web server error, but rather an interrupted connection to an external source. Are PHP scripts on your website set to access resources from other servers? Perhaps the resource is no longer available or server communication is down for some other reason. One way to eliminate this source of error is of course to not make your site dependent on external resources. If this is not possible, you can increase the time limit of your script. It also makes sense to implement efficient error handling so that errors in the PHP script can be detected more accurately.

    Could it be that the memory is overloaded? The memory limit determines how much memory a process may use. If more RAM is needed than is available, this could result in an internal server error. You can increase the limit as a temporary solution. To do this, add a command like this to php.ini:

    memory_limit = 512M
    In this example, you would set the memory provided to 512MB. Note, however, that your hosting provider will only allow you a certain PHP script limit within the package that you’ve booked. If you enter a higher value, the web server will ignore it. Raising the limit is only a temporary solution: once your site is up and running again, you should look for the reason for the high RAM usage. There is a high probability that the error can be found in the code of your website.

    If none of these methods offer you a solution, it is a good idea to contact your hosting provider. Before doing so, you can check the status of the servers: many hosting service providers will report the status of their servers via a status page or inform users via social media if a problem has occurred.


Viewing 15 replies - 16 through 30 (of 30 total)
  • You must be logged in to reply to this topic.