HTTP ERROR 500 in checkout when compilation is on and user is logged












0














I recently updated my Magento to 1.9.3.8.



Now, I have a HTTP ERROR 500 in a specific case.



I got an error when the following three conditions are met:




  1. URL : base_url/checkout/cart OR base_url/checkout/onepage

  2. Compiler state is enabled

  3. User is logged


I have nothing into Magento log (system.log or exception.log).
Nothing else into server logs (/var/log/httpd/error_log) or (mysite/logs/error_log).



My observations



After some deep research in the magento code, I think the error is in includes / src / __ checkout.php.



I can solve it with a bad trick. Update lib/Varien/autoload.php at line 105



static public function registerScope($code)
{
if($code != "checkout")
{
self::$_scope = $code;
if (defined('COMPILER_INCLUDE_PATH')) {
@include_once COMPILER_INCLUDE_PATH . DIRECTORY_SEPARATOR . self::SCOPE_FILE_PREFIX.$code.'.php';
}
}
else
{
//DO NOTHING
}
}


Someone else has the same error ? Or a real solution ?



I found nothing about this error and I don't understand why I have it. I never modify Magento core checkout files.



If this question is reporting to an already open subject, my apologize, I didn't find it.










share|improve this question
























  • if its 500 error, then you can check it in server error.log file. The issue will be there.
    – Shyam Krishna Sreekumar
    Mar 13 '18 at 9:55










  • it can also be due to permission error.
    – Shyam Krishna Sreekumar
    Mar 13 '18 at 9:57










  • @ShyamKrishnaSreekumar About Log : I already check file and there are nothing about errors. When I clean the logs, reload page, the log is still empty. I follow instructions from stackoverflow.com/questions/4731364/…. But still empty. About permission : I migrate all my website to my development server, I update permission of all files to 777. And still have the same error.
    – hemir
    Mar 13 '18 at 10:13












  • @hemir can you disable Compiler state ! and try
    – Sam
    Mar 13 '18 at 11:12










  • @Sam like I answered to your answer, I know without compiler, it works but that was not the subject of my question. I will keep my compiler enable to improve performance. I have this bug when the three conditions are met and compiler enable is one of them.
    – hemir
    Mar 13 '18 at 12:34
















0














I recently updated my Magento to 1.9.3.8.



Now, I have a HTTP ERROR 500 in a specific case.



I got an error when the following three conditions are met:




  1. URL : base_url/checkout/cart OR base_url/checkout/onepage

  2. Compiler state is enabled

  3. User is logged


I have nothing into Magento log (system.log or exception.log).
Nothing else into server logs (/var/log/httpd/error_log) or (mysite/logs/error_log).



My observations



After some deep research in the magento code, I think the error is in includes / src / __ checkout.php.



I can solve it with a bad trick. Update lib/Varien/autoload.php at line 105



static public function registerScope($code)
{
if($code != "checkout")
{
self::$_scope = $code;
if (defined('COMPILER_INCLUDE_PATH')) {
@include_once COMPILER_INCLUDE_PATH . DIRECTORY_SEPARATOR . self::SCOPE_FILE_PREFIX.$code.'.php';
}
}
else
{
//DO NOTHING
}
}


Someone else has the same error ? Or a real solution ?



I found nothing about this error and I don't understand why I have it. I never modify Magento core checkout files.



If this question is reporting to an already open subject, my apologize, I didn't find it.










share|improve this question
























  • if its 500 error, then you can check it in server error.log file. The issue will be there.
    – Shyam Krishna Sreekumar
    Mar 13 '18 at 9:55










  • it can also be due to permission error.
    – Shyam Krishna Sreekumar
    Mar 13 '18 at 9:57










  • @ShyamKrishnaSreekumar About Log : I already check file and there are nothing about errors. When I clean the logs, reload page, the log is still empty. I follow instructions from stackoverflow.com/questions/4731364/…. But still empty. About permission : I migrate all my website to my development server, I update permission of all files to 777. And still have the same error.
    – hemir
    Mar 13 '18 at 10:13












  • @hemir can you disable Compiler state ! and try
    – Sam
    Mar 13 '18 at 11:12










  • @Sam like I answered to your answer, I know without compiler, it works but that was not the subject of my question. I will keep my compiler enable to improve performance. I have this bug when the three conditions are met and compiler enable is one of them.
    – hemir
    Mar 13 '18 at 12:34














0












0








0


2





I recently updated my Magento to 1.9.3.8.



Now, I have a HTTP ERROR 500 in a specific case.



I got an error when the following three conditions are met:




  1. URL : base_url/checkout/cart OR base_url/checkout/onepage

  2. Compiler state is enabled

  3. User is logged


I have nothing into Magento log (system.log or exception.log).
Nothing else into server logs (/var/log/httpd/error_log) or (mysite/logs/error_log).



My observations



After some deep research in the magento code, I think the error is in includes / src / __ checkout.php.



I can solve it with a bad trick. Update lib/Varien/autoload.php at line 105



static public function registerScope($code)
{
if($code != "checkout")
{
self::$_scope = $code;
if (defined('COMPILER_INCLUDE_PATH')) {
@include_once COMPILER_INCLUDE_PATH . DIRECTORY_SEPARATOR . self::SCOPE_FILE_PREFIX.$code.'.php';
}
}
else
{
//DO NOTHING
}
}


Someone else has the same error ? Or a real solution ?



I found nothing about this error and I don't understand why I have it. I never modify Magento core checkout files.



If this question is reporting to an already open subject, my apologize, I didn't find it.










share|improve this question















I recently updated my Magento to 1.9.3.8.



Now, I have a HTTP ERROR 500 in a specific case.



I got an error when the following three conditions are met:




  1. URL : base_url/checkout/cart OR base_url/checkout/onepage

  2. Compiler state is enabled

  3. User is logged


I have nothing into Magento log (system.log or exception.log).
Nothing else into server logs (/var/log/httpd/error_log) or (mysite/logs/error_log).



My observations



After some deep research in the magento code, I think the error is in includes / src / __ checkout.php.



I can solve it with a bad trick. Update lib/Varien/autoload.php at line 105



static public function registerScope($code)
{
if($code != "checkout")
{
self::$_scope = $code;
if (defined('COMPILER_INCLUDE_PATH')) {
@include_once COMPILER_INCLUDE_PATH . DIRECTORY_SEPARATOR . self::SCOPE_FILE_PREFIX.$code.'.php';
}
}
else
{
//DO NOTHING
}
}


Someone else has the same error ? Or a real solution ?



I found nothing about this error and I don't understand why I have it. I never modify Magento core checkout files.



If this question is reporting to an already open subject, my apologize, I didn't find it.







php checkout compilation magento-1.9.3.8 http-error-500






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 6 '18 at 3:36









WISAM HAKIM

1,553617




1,553617










asked Mar 13 '18 at 9:38









hemirhemir

11




11












  • if its 500 error, then you can check it in server error.log file. The issue will be there.
    – Shyam Krishna Sreekumar
    Mar 13 '18 at 9:55










  • it can also be due to permission error.
    – Shyam Krishna Sreekumar
    Mar 13 '18 at 9:57










  • @ShyamKrishnaSreekumar About Log : I already check file and there are nothing about errors. When I clean the logs, reload page, the log is still empty. I follow instructions from stackoverflow.com/questions/4731364/…. But still empty. About permission : I migrate all my website to my development server, I update permission of all files to 777. And still have the same error.
    – hemir
    Mar 13 '18 at 10:13












  • @hemir can you disable Compiler state ! and try
    – Sam
    Mar 13 '18 at 11:12










  • @Sam like I answered to your answer, I know without compiler, it works but that was not the subject of my question. I will keep my compiler enable to improve performance. I have this bug when the three conditions are met and compiler enable is one of them.
    – hemir
    Mar 13 '18 at 12:34


















  • if its 500 error, then you can check it in server error.log file. The issue will be there.
    – Shyam Krishna Sreekumar
    Mar 13 '18 at 9:55










  • it can also be due to permission error.
    – Shyam Krishna Sreekumar
    Mar 13 '18 at 9:57










  • @ShyamKrishnaSreekumar About Log : I already check file and there are nothing about errors. When I clean the logs, reload page, the log is still empty. I follow instructions from stackoverflow.com/questions/4731364/…. But still empty. About permission : I migrate all my website to my development server, I update permission of all files to 777. And still have the same error.
    – hemir
    Mar 13 '18 at 10:13












  • @hemir can you disable Compiler state ! and try
    – Sam
    Mar 13 '18 at 11:12










  • @Sam like I answered to your answer, I know without compiler, it works but that was not the subject of my question. I will keep my compiler enable to improve performance. I have this bug when the three conditions are met and compiler enable is one of them.
    – hemir
    Mar 13 '18 at 12:34
















if its 500 error, then you can check it in server error.log file. The issue will be there.
– Shyam Krishna Sreekumar
Mar 13 '18 at 9:55




if its 500 error, then you can check it in server error.log file. The issue will be there.
– Shyam Krishna Sreekumar
Mar 13 '18 at 9:55












it can also be due to permission error.
– Shyam Krishna Sreekumar
Mar 13 '18 at 9:57




it can also be due to permission error.
– Shyam Krishna Sreekumar
Mar 13 '18 at 9:57












@ShyamKrishnaSreekumar About Log : I already check file and there are nothing about errors. When I clean the logs, reload page, the log is still empty. I follow instructions from stackoverflow.com/questions/4731364/…. But still empty. About permission : I migrate all my website to my development server, I update permission of all files to 777. And still have the same error.
– hemir
Mar 13 '18 at 10:13






@ShyamKrishnaSreekumar About Log : I already check file and there are nothing about errors. When I clean the logs, reload page, the log is still empty. I follow instructions from stackoverflow.com/questions/4731364/…. But still empty. About permission : I migrate all my website to my development server, I update permission of all files to 777. And still have the same error.
– hemir
Mar 13 '18 at 10:13














@hemir can you disable Compiler state ! and try
– Sam
Mar 13 '18 at 11:12




@hemir can you disable Compiler state ! and try
– Sam
Mar 13 '18 at 11:12












@Sam like I answered to your answer, I know without compiler, it works but that was not the subject of my question. I will keep my compiler enable to improve performance. I have this bug when the three conditions are met and compiler enable is one of them.
– hemir
Mar 13 '18 at 12:34




@Sam like I answered to your answer, I know without compiler, it works but that was not the subject of my question. I will keep my compiler enable to improve performance. I have this bug when the three conditions are met and compiler enable is one of them.
– hemir
Mar 13 '18 at 12:34










1 Answer
1






active

oldest

votes


















0














I'm getting the same issue following an update to 1.9.4.0 from 1.9.3.4



As you've reported there are no related errors messages being reported in either magento logs or server error logs.



Did you ever find a solution to this other than the obvious step of turning off the compiler?



(Your suggested code mod works insofar as it ignores compiled files for checkout pages. But as you said - you've already established that the error occurs when the compiler is activated. So it's just a workaround really that depends on modifying core code - and as you suggest - therefore not a great long term solution.)






share|improve this answer





















    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "479"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f217122%2fhttp-error-500-in-checkout-when-compilation-is-on-and-user-is-logged%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    I'm getting the same issue following an update to 1.9.4.0 from 1.9.3.4



    As you've reported there are no related errors messages being reported in either magento logs or server error logs.



    Did you ever find a solution to this other than the obvious step of turning off the compiler?



    (Your suggested code mod works insofar as it ignores compiled files for checkout pages. But as you said - you've already established that the error occurs when the compiler is activated. So it's just a workaround really that depends on modifying core code - and as you suggest - therefore not a great long term solution.)






    share|improve this answer


























      0














      I'm getting the same issue following an update to 1.9.4.0 from 1.9.3.4



      As you've reported there are no related errors messages being reported in either magento logs or server error logs.



      Did you ever find a solution to this other than the obvious step of turning off the compiler?



      (Your suggested code mod works insofar as it ignores compiled files for checkout pages. But as you said - you've already established that the error occurs when the compiler is activated. So it's just a workaround really that depends on modifying core code - and as you suggest - therefore not a great long term solution.)






      share|improve this answer
























        0












        0








        0






        I'm getting the same issue following an update to 1.9.4.0 from 1.9.3.4



        As you've reported there are no related errors messages being reported in either magento logs or server error logs.



        Did you ever find a solution to this other than the obvious step of turning off the compiler?



        (Your suggested code mod works insofar as it ignores compiled files for checkout pages. But as you said - you've already established that the error occurs when the compiler is activated. So it's just a workaround really that depends on modifying core code - and as you suggest - therefore not a great long term solution.)






        share|improve this answer












        I'm getting the same issue following an update to 1.9.4.0 from 1.9.3.4



        As you've reported there are no related errors messages being reported in either magento logs or server error logs.



        Did you ever find a solution to this other than the obvious step of turning off the compiler?



        (Your suggested code mod works insofar as it ignores compiled files for checkout pages. But as you said - you've already established that the error occurs when the compiler is activated. So it's just a workaround really that depends on modifying core code - and as you suggest - therefore not a great long term solution.)







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered yesterday









        David BDavid B

        1




        1






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Magento Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f217122%2fhttp-error-500-in-checkout-when-compilation-is-on-and-user-is-logged%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            1300-talet

            1300-talet

            Display a custom attribute below product name in the front-end Magento 1.9.3.8