I installed the last Patch 10570 on 18.104.22.168 via SSH.
If I now add something to the basket with the Enabled compiler, I get a white page.
With disabled compiler everything works without problems.
Does anyone have an idea?
Same issue here on 22.214.171.124, 126.96.36.199, 188.8.131.52.
When user is logged in white page on cart and checkout error 500. No logs on magento logs nor nginx.
A workaround available here : https://www.econcess.de/blog/onlineshop-erstellung-magento/152-magento-onlineshop-supee-10570-und-we...
Ok, so there is no log cause of : lib/Varien/Autoload.php
@include COMPILER_INCLUDE_PATH . DIRECTORY_SEPARATOR . self::SCOPE_FILE_PREFIX.$code.'.php';
The error is :
FastCGI sent in stderr: "PHP message: PHP Fatal error: Cannot declare class Zend_Date_DateObject, because the name is already in use in /www/includes/src/__checkout.php on line 44121
what do you mean by your last post?
Is the problem to be solved via your link? Or is there another option here?
Thanks and Greetings
The solution on the link seems to work.
However, I'm not sure it's the best solution.
Yes. Tried it on 184.108.40.206 and it seems to work. I'm also not sure if this solution is the best.
What I can not understand is why you even program a patch and in case of problems there is no official solution.
I am having the same issue with this patch on Magento 220.127.116.11. It gives 500 blank screen with compilation. I reverted the Patch by this command
$ sh PATCH_SUPEE-10570_CE_v18.104.22.168_v1-2018-02-28-04-54-29.sh -R
and everything started working again. Magento please release its correct version. Thanks
same here. 22.214.171.124 - customers not redirected to payment pages but returned to homepage instead. We couldn't replicate the problems but enabling compilation throws error 500 in the cart. For now reverted the patch and waiting for a viable solution from Magento devs
the issue has now been solved with version 2 of the patch (https://magento.com/security/patches/supee-10570), however this version does no longer protect against two low risk session handling-related security issues that patch SUPEE-10570 protected against. I'm assuming this will be addressed again in the next patch...