Can I run CakePHP 1.3 with PHP7? I have to do a migration to PHP7, but in the hosting there is a project in CakePHP 1.3 and need to know if there is any risk if I run this project in this version of PHP.
Unfortunately CakePHP 1.3 is not really compatible with PHP7 out of the box. I work on a old project in CakePHP 1.3 and my system upgraded to PHP7. There are a lot of these in the core of CakePHP 1.3
After changing these, I ran into the next batch of errors, after which I rolled back and postponed the upgrade.
So to answer the question, it would be rather risky upgrading to PHP7 if there is a CakePHP 1.3 project.
If you are still looking for a CakePHP 1.3 port to PHP7, you are in luck!
I've ported CakePHP 1.3.21 to PHP 7.3, you can check it out on GitHub.
Please pay attention to the readme, as it naturally requires changes to your own code as well!
I had to migrate a CakePHP 1.3 project to PHP7 and the only thing I did was find the "String" class and using PhpStorm's rename all occurrences feature I renamed it to "String_Renamed" that fixed the errors and everything worked afterwards. I've had no issues since.
Related
I have a Laravel application that has been running since mid 2018. PHP is currently version 7.2.5 and Laravel is 5.6.22. I need to upgrade PHP to either 7.4 or 8.0, and Laravel to either 6 LTS, or 8.
As far as I can see, I have two options:
Upgrade PHP to the new version, then incrementally upgrade Laravel from 5.6.22 to 6 LTS (or 8), testing each version as I go; or
Upgrade both PHP and Laravel to their new versions, and do one round of testing
My initial thought was to use method 1, reading the Laravel notes for each release and tailoring my testing efforts as I go. But upon upgrading PHP to 7.4, Laravel started to fail somewhere deep in the library, so I guess V 5.6.22 does not work with PHP 7.4
Is there a standard approach to this problem? (Note that, sadly, I don't have automated unit tests).
This happened to me when I started working with Laravel, I started with Laravel 5.3 and my team had to upgrade it to 5.4, 5.5, 5.6 and 5.7 (then I left haha).
What we ended up doing was:
First upgrade PHP, as it is the mostly certain that it will not cause any issue. I recommend you to upgrade to 8.0
What we had done to upgrade was having tests. Previously we did not have, so we learn how to test and we reach a coverage of 90%, so we were extremely good at it and advancing fast on it.
Once you have the tests, you can start migrating version by version. Because you are on 5.6, you could directly upgrade to 6 or 8, so you can follow the guide to upgrade from 5.8 to 6 or 7 to 8. It is easy to upgrade, the important stuff is related to packages mostly.
These are the tips and personal experience I can share with you. It is 100% important to have tests, else it will be a pain for you as you will not be 100% sure if something broke.
I am trying to upgrade from CI version 1.7.3 to CI Version 3.1.7. The problem I have is for some unknown reason the User Guide for 3.1.7 DOES NOT even mention upgrading from version 1.7.3 to version 2.0-let alone upgrading from 1.7.3 to version 3.1.7. How can I get a list of changes made from version 1.7.3 to 3.1.7, IF codeigniter's own user' guide does not even MENTION my version?
I do remember reading something about changing CI version 1.7.2 to version 1.7.3, but then, I am not sure if that means I should follow the upgrade steps for 1.7.2?
So, if I am to follow the steps to upgrade from 1.7.2 to 2.0 then what was the point of upgrading to 1.7.3 to begin with? Any ideas would be greatly appreciated.
Thanks in advance!
This is the current upgrade paths on the CI Site. You need to upgrade from 1.7.x to 2.x, then 2.x to 3.x.
Most of it is pretty simple, but you will want to read carefully from 2.2 -> 3, as that has the most changes.
In response to the comment about system folders, in general you are always entirely deleting the existing system folder in your current project, and then putting in the new system folder from the version you are upgrading too. It is important to delete the old one first, not simply replace it, as sometimes files are removed and not replaced in upgrades.
The caveat is that this is only safe if you have used the framework as intended, and not modified any file inside the system folder. If you have, you will still need to do the aforementioned steps, but you will then need to address your previous modification, perhaps by re-hacking the system files.
This error is driving me crazy.
I had Laravel 5.2, then I upgraded to 5.3 and then 5.4 then this error started to appear.
I have searched everywhere on Google and here in SO but none of the solutions is working on my case. Any idea what to do?
I did have a look that the package you provided. Their last commit was in October 2016. So I can say, this does not support Laravel 5.4 yet.
The latest version you can use this package in is Laravel 5.3. Open an issue for the package manager to add support for Laravel 5.4.
I installed it in a clean Laravel 5.4 project and it didnt work as well, though I received a different error. You said it works in 5.3, so I think it's just a matter of version support.
Is Zend Framework 2 work with PHP version 5.3.2?. During the skeleton application installation i got following message.Is this just a warning or it will cause any problem in future?
D:\web\Apache24\htdocs\zendsample>composer create-project -n -sdev zendframework
/skeleton-application D:\web\Apache24\htdocs\zendsample
Your version of PHP, 5.3.22, is affected by CVE-2013-6420 and cannot safely perf
orm certificate validation, we strongly suggest you upgrade.
Installing zendframework/skeleton-application (2.4.11)
Make thinks short :
With PHP 5.3 you'll not able to use Traits and new features php 5.4 wich is used in most of vendor plugin and the framework itself.
Usually it's strongly recommanded to upgrade your PHP version.
From this link PHP version maintained PHP 5.3 is no longer maintained since 2014. It's antique. You'll be face to security issues and no evolution of your code will be possible.
To answer your question :
You'll not able to use traits
You'll faceing security issues
You'll not able to improve your code withe best practises (wich evolves permanently)
your views can't use short version for echoing stuff <?='toto'?>
All new features linked above are not supported with your version if it's used in the framework, you'll can't run the framework itself.
I recommend upgrade your version at least at 5.6 or 7 for a good longevity support
EDIT : 5.5 to 5.6 because 5.5 no longer supported.
After getting this message i just upgraded my php to 5.5.
How do I migrate a site I've made using cakephp 1.1 to a newer version compatible with my PHP version 5.4.7?
Read all the migration guides and upgrade accordingly:
http://book.cakephp.org/2.0/en/appendices.html
You can also leverage the upgrade shell of cakephp or the enhanced one (only for experts, though).
This should make it possible to upgrade.
But 1.1 to 2.3 is still quite a bit of work, though.