I'm thinking of making the next version of opencart PHP 5.3 only!
I would like the communities input on this. It would be really good if we could start using php 5.3 features such as name spaces. it would make life so much easier.
I would like the communities input on this. It would be really good if we could start using php 5.3 features such as name spaces. it would make life so much easier.
OpenCart®
Project Owner & Developer.
I vote YES for this. All web host "should" be running this.
This account is inactive. Look for us under the name 'EvolveWebHosting' and contact us under that username.
Thanks!
Maybe setting up a poll on the homepage, asking the community "Which PHP version are you currently using?"
The results could help with the final decision.
Mine is 5.2.17 at the moment and I don't have immediate plans for changing web hosting, so it would be a no go for me.
The results could help with the final decision.
Mine is 5.2.17 at the moment and I don't have immediate plans for changing web hosting, so it would be a no go for me.
OpenCart custom solutions @ https://villagedefrance.net
my host is also currently running 5.2 but that's because it was the default. I can change it to 5.3 easily enough as they have a setting in their cpanel to do so.
I think it's very simple:
5.2.9 - END OF LIFE
5.2.17 - DEPRECATED
5.3.21 - END OF LIFE
5.3.22 and 5.4.12 are the new best options
It's clear that Daniel needs to focus on php 5.3 so OpenCart can take advantage of these new features like namespaces and much more.
5.2.9 - END OF LIFE
5.2.17 - DEPRECATED
5.3.21 - END OF LIFE
5.3.22 and 5.4.12 are the new best options
It's clear that Daniel needs to focus on php 5.3 so OpenCart can take advantage of these new features like namespaces and much more.
According to w3techs statistics, from all php 5 usage, php 5.2 have 47.3% while 5.3 have 46.8%
As you see, the users number is still the same.
But some cms like Joomla and Dupal develope version for php 5.3 start from new version.
If we used it in OpenCart, you can develope v.1.6 or v.2 with php 5.3 only.
But keep maintain the current version and release bugs fix so it come the stable version to run the business.
There is no need for you to maintain both version. Create a team for managing bugs fix for current version and you can focus on the new version. But of course, you still monitor the team to keep them on track.
As you see, the users number is still the same.
But some cms like Joomla and Dupal develope version for php 5.3 start from new version.
If we used it in OpenCart, you can develope v.1.6 or v.2 with php 5.3 only.
But keep maintain the current version and release bugs fix so it come the stable version to run the business.
There is no need for you to maintain both version. Create a team for managing bugs fix for current version and you can focus on the new version. But of course, you still monitor the team to keep them on track.
Perhaps like Qahar suggests you could develop v1.6 for PHP 5.3 and keep v1.5x for PHP 5.2. This way anybody who doesn't have a host with 5.3+ can still use OC but you will still be able to take advantage of newer versions of PHP for further development of OC. Eventually 5.2 will phase out anyways so the jump will have to be made sometime.
It is exactly my situation. However, after switching to 5.3 OpenCart stopped to work (500, Server error). Does it require OC re-installing?moneycarlo wrote:my host is also currently running 5.2 but that's because it was the default. I can change it to 5.3 easily enough as they have a setting in their cpanel to do so.
I can confirm that OC 1.5.5.1 works with PHP 5.3.Cepreu wrote:... after switching to 5.3 OpenCart stopped to work (500, Server error). Does it require OC re-installing?
Try to disable .htaccess maybe that is causing your 500, server error.
Going back to the initial post, I think the idea of getting min. req. PHP 5.3 for the next version (1.6 or 2.0) is more comprehensible if we look in perspective of a long term development.
Would it be feasible to maintain OC 1.5 with bug fixes only for, let's say 12-18 months? if the answer to this is yes, I would say, new features should go in the new version looking at the future for you and for the project.
These are the questions I would be asking myself? What happen if you keep the code compatible with old versions of PHP? would this affect development in 12/18months or later on? Would it be easier to make the switch to PHP 5.3 now or in 18months?
Since I'm able to specify php.exe version and to set php.ini, on plural servers, I've found that I prefer 5.3 over prior as well as over 5.4, for very smoothly running OC 1.5.0 through 1.5.5.1, alike. Versions' defaults differ, and that can foster 500 being thrown until .ini and .ht* changes are made to match version.
Here we are running 5.3 and even the old 1.4.xx are running on it without problems.
Next week 1 server is going to php 5.4 and see what's happening. But i think everything will be okay. I tested the old OC shop local on php 5.4. Maybe I get some problems with old WP and Joomla sites
But my clients were informed about the update
This is the latest list of easy apache
PHP 5 [More Info ↑]
None
5.2.9 END OF LIFE
5.2.17 END OF LIFE
5.3.26 END OF LIFE
5.3.27 DEPRECATED
5.4.17
5.5.1 EXPERIMENTAL
Next week 1 server is going to php 5.4 and see what's happening. But i think everything will be okay. I tested the old OC shop local on php 5.4. Maybe I get some problems with old WP and Joomla sites
But my clients were informed about the update
This is the latest list of easy apache
PHP 5 [More Info ↑]
None
5.2.9 END OF LIFE
5.2.17 END OF LIFE
5.3.26 END OF LIFE
5.3.27 DEPRECATED
5.4.17
5.5.1 EXPERIMENTAL
When php 5.4 becomes available you will, hopefully, be able to select php 5.3 -- the two do not behave the same, and I happen not to care for 5.4 after an extended term of discovery and muttering. So far, all OC 1.5 versions seem happy on php5.3, and you're adding OC 1.4 without reservation.
[EDIT, ADDED, 2014 Feb 18:] Into 2014 php 5.3 satisfies 1.5.0.0 through now 1.5.6.1 OC.
[EDIT, ADDED, 2014 Feb 18:] Into 2014 php 5.3 satisfies 1.5.0.0 through now 1.5.6.1 OC.
Last edited by butte on Wed Feb 19, 2014 12:59 pm, edited 2 times in total.
Is already available for the most servers.(Cpanel)Even Php 5.x is supported by CpanelWhen php 5.4 becomes available you will
Info of http://php.net/
PHP 5.3.27 Released - PHP 5.3 Reaching End of Life
11-Jul-2013
The PHP development team announces the immediate availability of PHP 5.3.27. About 10 bugs were fixed, including a security fix in the XML parser (Bug #65236).
Please Note: This will be the last regular release of the PHP 5.3 series. All users of PHP are encouraged to upgrade to PHP 5.4 or PHP 5.5. The PHP 5.3 series will receive only security fixes for the next year.
I think for the new 2.0 relaese with PHP 5.4
k2tec.-- My servers have had 5.4 available for a while, selectably among [5.1], 5.2, 5.3, 5.4, and 5.5, but as on 16th "Next week" yours "is going to php 5.4," so "when 5.4 becomes available" spoke (on 16th) to that.
Cepreu-- As for 5.3 stopping OC and throwing 500, no, it is not necessary to reinstall OC. Your php settings were not appropriate for 5.3, make those appropriate and both the 500 will go away and OC will revive. However, given the time elapsed, you will already have overcome that by now.
Cepreu-- As for 5.3 stopping OC and throwing 500, no, it is not necessary to reinstall OC. Your php settings were not appropriate for 5.3, make those appropriate and both the 500 will go away and OC will revive. However, given the time elapsed, you will already have overcome that by now.
Last edited by butte on Sat Jan 25, 2014 1:10 am, edited 1 time in total.
+1 PHP 5.3 namespaces
+1 PSR-{x} coding standard adoption
+1 complete registry pattern to service manager pattern, with single service instance creation
regards,
pine3ree
+1 PSR-{x} coding standard adoption
+1 complete registry pattern to service manager pattern, with single service instance creation
regards,
pine3ree
Who is online
Users browsing this forum: No registered users and 87 guests