Hey thebeanz,
Thanks for the feedback! If you can give the developer version a try it may have the fixes for your issue, we have made some improvements to the Update Engine. The very latest version (1.1.13) can be found by following these instructions:
-> Browse to http://wordpress.org/extend/plugins/duplicator/developers/
-> Click on “Development Version” link and download the zip plugin file
-> Uninstall your current version and install this one
Let me know if this solves your issue, if not we can work offline to try and isolate the problem…
Thanks
Thanks for quick reply. Downloaded and installed 1.1.13 but get the same problem.
Step 2: System scan
Scan Error
Please try again
Server Status: 500 -Internal Server Error
Error Message: No error message appears
If you need it I can give you temporary access to the test site.
Many thanks
Bruce
Couple of things to still check:
1. Do you know if WooCommerce writes to the .htaccess file if so you may need to check it to make sure there are no directives causing possible issues? Create a file named test.php (after the 500 error) with the following content below and see if you can browse to it. If you can then the .htaccess file shouldn’t be causing any issues. If not then you may try to clear the contents of .htaccess and try again.
<?php phpinfo() ?>
2. Check the installer-log.txt to see if any errors are in it (do not post the full log here)?
3. Have you checked with WooCommerce to see if they are aware of the issue as well?
Thanks
I have posted problem on woocommerce as per your suggestion.
Created test.php, ran the scan, got the error message but I could still then browse to test.php.
I cannot find the installer-log.txt – can you point me in the right direction?
I will continue using older version of Woocommerce until there is a fix as I really like Duplicator – it does everything I need – I use it mainly as my prime source of backup.
Thanks for your help and fingers crossed.
Bruce
OK – contacted web host and asked where I could find error logging. They replied saying they would enable it for me and to then try the scan so that I could see the error log. Lo and behold – the scan worked. I have contacted host again to ask whether or not they tweaked any other settings or whether simply enabling error logging would have done the trick – am awaiting a reply.
Again – many thanks for your time and patience.
Don’t know if any of this is of help for future reference as the problem I had only started after install of WC 2.6 but this is reply from my host:
xxxxx.co.uk already had a custom php.ini, which was probably put there by somebody. However, it was not called out properly, so all I did is specify that the site uses it using a line in your .htaccess file. I am not sure how this php.ini is changed from the default one, but most likely it increases some limits that the plugin requires. I just turned on error reporting and set the path to the error log file.
Hope this helps – I don’t pretend to understand much of it!
Hey @thebeanz,
So I’m not quite sure where this stands are you still having specific issues?
Thanks
Apologies for not making it clear – there are no more issues but I really don’t know what it that solved the problem. As per my last post, my host did a couple of things and I posted their reply. All I can say is that, having tried it twice with and without updating WC on what I am sure was initially a virgin site it must have been something that updating WC did that made it happen.
This can be marked as resolved and many thanks again for your help.
Sounds Good! Thanks for the update… Also as a note to other users, on some plugins it can clear up issues if you go back in and re-save any settings after performing the migration…
Cheers~
