Is Kohana framework alive or not?
Development site returns an error when I try to enter it. I can't seem to find Kohana in more or less modern PHP frameworks comparison tables (like this Wikipedia article)
I would consider it dead, but there seem to be some life signs in Github repo.
Than again, looking at their repo creates more questions than answers. Official site states that last stable version is 3.3.3.1, but last commit to 3.4 happened at January and last commit to unstable 4.0 core happened two years ago.
Were there some official announcements or releases I've missed somehow?
For all intents and purposes it's dead. There's a very small community that still uses it and makes some commits to the repo, but the staff abandoned it a year ago.
The official announcement was in the forum, you can read it here - http://forum.kohanaframework.org/discussion/12509/final-releases-of-kohana-beginning-of-ohanzee
Related
Okay, so I'm building a Web application using PHP and Laravel and the ultimate goal is to have a free, standard version as well as a commercial version which the user will have to pay. Of course, the commercial version will have additional features which will be locked in the community edition.
The problem here is that I have no idea how to go about this and surprisingly, I can't seem to find anything on how to intelligently develop this type of application. Having two codebase, one for each version, seems like a very bad idea. Equally, having my code riddled with "if" statements to lock features up depending on specific clients seems pretty bad too.
How does one go about developing an application with multiple flavors like this? Are there tools? Tutorials which I could read?
Thanks in advance.
EDIT: In answer to Scott's comment, at the moment, we're going to manage the hosting of the application. The owner mentioned his plan to go open-source in a couple of years, but right now my main focus is to manage Community VS Commercial edition.
I've tried looking at the CakePHP site but there isn't a sliver of information to be found as to when is the end of support for CakePHP 2.X.
I have tried asking someone at the #cakephp irc channel and got this answer from a person
I would take it that because 1.3 support ended when 3.x came out, that 2.x support will end when 4.x is released
However this is unverified, I hope someone can answer this and also provide a source or from someone involved with the development team.
There hasn't been any decision taken to end support for CakePHP 2.x. It will continue to be maintained for the foreseeable future.
The current 2.6 series will keep getting bugfix releases and we also have a 2.7 branch where new features are added and will be released sometime in future.
So rest assured support for 2.x won't stop for months to come.
P.S. I am a member of the CakePHP dev team.
1.3 support didn't end after 2.0 came out. There were 7 1.3 releases after 2.0. As ADmad mentioned we'll continue to do bugfixes for a at least a couple years, and security releases for a year or so longer. Given that we supported 1.3 for 3 years after 2.x came out, I suspect we'll do something similar with the last 2.x release as well.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I'm just starting on a software as a service project using CakePHP. I can see that version 3 is still in beta and I can see this project taking 3-6 months.
My question is should I start with version 2 or version 3 beta with the latter probably reaching a stable release.
I don't want to learn version 2 and then version 3 has a fair few changes.
Update: Go for CakePHP 3.0 now if you start a new project. CakePHP 3 is no longer in RC or beta state so it can be used without any doubts now.
The question is likely to get closed because it is opinionated, I'm undecided to put up a close vote for that reason myself, however...
Cake3 is in fact OK to be used for a project that is going to take 3-6 month - that is my opinion. But you'll have to expect a few API changes until then. I would not sacrifice the more modern architecture of Cake3 and language features, mostly the namespaces and closures for using an old version that doesn't support them just because Cake3 has not yet reached 3.0 (without the RC).
I've started using Cake myself when 1.3 was in alpha and the transition from 1.2 to 1.3 was pretty smooth. I've had to adept to the API changes during the ongoing development of 1.3 but this was not a game breaker and I never had to spend much time for it.
Same story with Cake3. We are using 2.x and started a new project using Cake3 and don't have much trouble with it. So far it just works fine and the occasional adoptions to the API changes are no game breaker as it was before.
You can see that Cake3 is mostly feature complete by now.
https://github.com/cakephp/cakephp/wiki/3.0-Roadmap
If you go further you'll notice that 3.1 is going to raise the minimum php version to 5.5.
https://github.com/cakephp/cakephp/wiki/3.1-Roadmap
This is because 5.4 is going to reach it's end of support. So there is no reason to support it any more. Based on this you can make your guess when 3.0 will be released: Likely before 5.4 is officially deprecated.
The one and only disadvantage of Cake3 right now might be the availability of plugins. But there are already lots of plugins that are upgraded to 3.0 and even new plugins for 3.0.
Update:
Absolutely 100% go with CakePHP 3.x. There should no longer be any debate as Cake 3 is now up and running and no longer in beta or RC...etc.
Original Answer:
If you're starting now (Jan '15), I see no point in learning CakePHP 2.x. Why go through the trouble, when by the time your project is complete, you'll already have out-of-date code (I know "out-of-date" might be a bit extreme, but...).
Not only that, but CakePHP2 and CakePHP3 are worlds different with a fairly sizable learning curve. I cannot imagine, at this point learning one language only to have to re-learn the entire thing in less than a year.
IF CakePHP 3 RC wasn't a viable choice (ie projects crashed all the time, or had issues left and right), and you're on a deadline, then you'd have no choice anyway. But CakePHP 3 RC seems to be running fine and is already being used on live projects.
The no-brain answer IMO: Go with CakePHP 3. I certainly would if I were in your shoes.
At this point (19th Jan 2014) , it is safe to go with cakephp 2 . cakephp 3 is not a stable release and there is no clear schedule date for stable release yet. I dont think it will be a breeze to update it later to a stable version if you develop in its current version . You might end up changing lot of code.
Hi I am working with cakephp since 1 year and I found that you can use cakephp 2.x because it is stable version don't need to extra configuration but in cakphp 3 is unstable version you install the composer in cakephp 3 & the structure of cakephp 3 is totally different form cakephp2 such as cakephp2 root folder is APP but cakphp 3 there is no app folder its contains src, bin, vendor etc
I found too many problems width cakephp 3.1 :
In appController, the function beforeFilter() is not working well as it was in cakephp 2.x, when I tape return false It should return a blank page but now It returns everything like if this function beforeFilter() in the appController is not controling nothing.
In Model, the functions beforeFilter(), beforeSave() and beforeDelete() have been replaced with too many functions in cakephp 3.1 but in reality those functions are not realy usefull, for the simple reason these functions don't work as we expected them to work, there is no centralization of these functions, you can say those new functions are not working at all.
The system of prefix and how we can contrôl access to some users to access to Admin/ prefix for example only from the controller and all the liberty this great functions of cakephp 2.x can give us now all this is gone with cakephp 3.1 and there are some bad restrictions you should respect.
cakephp 3.1 error managing are not helping you at all to found the source of the problem, it's like you're working with no compiler you found the source of the problem yourself, an if it's an very big project I garenty for you that you can failed at 60%....
too many reasons push you to wait for an other stable version of cakephp 3.x to start using this technologie.
now Symfony2 PR4 is released, probably the last one before the official release.
I already have done some tutorials with the latest symfony 1.4 (the complete jobeet tutorial).
My question now: is it better to learn symfony2 before getting closer with 1.4?
if yes, any good sources for learning symfony2? blogs, books, etc..
thanks!
a big part of your answer should be based on your timetable. if you have to launch your project within the next 3-4 months then I would go with symfony 1.4.
since the GA release of symfony2 is not planned until early next year it would not be good to begin alot of work on that system since things may change and you may have bugs from the code that would be hard to track down.
even though there will be major changes between 1.4 & 2, I don't believe it would be wasted time learning 1.4
for learning symfony2, i would say the two best places would be the symfony site. blog here and forum here
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
Is OSCommerce outdated?
I recently started working for a web development company that uses it a lot and I noticed the code base is really messy and has a lot of older php code in there. Being used to something nice like cakePHP or drupal I wasn't too impressed with it.
Is it worth using any more?
Is there a decent port of OSC that is updated and easy to transfer existing stores to? bonus points if it has a plug in system that isn't a hack fest.
Right now I'm looking at Zen-cart, Ubercart and Magento as alternatives. Would you recommend anything else?
ThankYou
Is OSCommerce outdated?
That depends on how you would define outdated. If you are using a v1.0, then yes. But osCommerce is still actively maintained and developed. The current development version is osCommerce 3.0 Alpha 5.
I recently started working for a web development company that uses it a lot and I noticed the code base is really messy and has a lot of older php code in there. Being used to something nice like cakePHP or drupal I wasn't too impressed with it.
I am sure you can find prettier architectures. I looked at the source code briefly and can confirm there is a number of things considered code smells nowadays, like lots of defined constants, global keywords and such. The codebase is old-fashioned compared to today's standards, but that's the way it is with long running systems that have evolved over many years. Old fashioned doesnt necessarily mean outdated though.
Is it worth using any more? Is there a decent port of OSC that is updated and easy to transfer existing stores to? bonus points if it has a plug in system that isn't a hack fest.
osCommerce is a mature product. And like said in the beginning, it is actively maintained. You shouldnt base the application's worth on the codebase alone. Wordpress would be worthless then. And CakePHP isnt exactly famous for it's codebase either. A client you will install ocCommerce for is rarely interested in the codebase, but rather in if the system can satisfy his or her requirements to a shop system.
Right now I'm looking at Zen-cart, Ubercart and Magento as alternatives. Would you recommend anything else?
There is also xtCommerce which forked from osCommerce a few years ago. This is not meant as recommendation though. I find it hard to recommend a shop system from the vast amount of systems out there without knowing any requirements.
On a sidenote: if you want to collect software metrics about osCommerce, head over to phpqatools.org and run some tools over, gather statistics and compare it to some other shop systems.
Short answer: Yes
I can not tell you anything about the version 3 (alpha items on their roadmap) but if you are using a 2.x you are basicly stuck in 2006, compared to other shopping solutions like magento (which I like to call 'the diva' because everything comes with a price).
OSCommerce is older than simmons... AND SIMMONS IS OLD!
Avoid it like the plague.
Magento and Cube Cart are decent. Would go for Symfony if you're looking for and upgrade from cake or drupal. :-)
osCommerce 2.x.x is bit outdated for following reasons:
No MVC concept. This makes maintenance a real difficult and when one error is fixed another might pop in.
Architecture is from 2001. With advancement in concept architecture has become very important. So benefits of newer design concepts not used.
Security issue : Lots of plugins that are not secured as they are not updated. osCommerce out of box is secured for its latest version.
Not Yet, You can work on Version 3. Oscommerce has good community rather than others. and most important things Oscommerce is complete GUI License with huge code library. Like other e-commerce has many restriction and limitation and most are paid.
Thats why we can't say that oscommerce is outdated right now but in future we say anythings,
osCommerce 2.x is built on technology from 2001-2002 (The Exchange Project). Over the years they have added som patches and paint to make it stand. So yeah it's pretty outdated. Always has been.
The last version 2.3.1 is the biggest rewrite so far (not counting 3.0). I would say there is still work to be done on this one as well.
osCommerce 3.0 is just a framework. It has no features for adding products or categories yet. It's just for developers who want to contribute to the next generation osCommerce.