Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 12 months ago.
Improve this question
I have a admin panel made with Codeigniter 3.1.6 version. I searched it but i found different opinions about it. Can i upgrade it to 4.1.9? I have site settings, image uploading, mail sending and some different things in my project. (iziToast, sweetalert, toggle button)
I believe this is a big endeavor but nonetheless - this should give you some structure and pointers - Upgrading CodeIgniter 3 to CodeIgniter 4
While most is generally to Filetype (Model, View or Controller) and specific upgrade and/or omissions of libraries and in few areas extensive changes might be needed in your code.
Most of the changes must be from Models as more of CRUD Functionality is built-in available, while Configuration Files is completely different than CodeIgniter 3. I believe part by part some areas might be tricky.
Wishing success ahead with new features and Built in ORM.
P.S. - Myself am beginner in CodeIgniter 4 only.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
Im beginning a new project with Laravel 4 / 5 (done this many times).
I dont want to re-write the wheel setting up admin interfaces and user authentication.
Is it wise to use something like OctoberCMS and pull it part to my own ends?
Why I would do this:
I want extensive CMS functionality
I want a nice user interface
I dont want to code all that!
I have dabbled with the october CMS, and it's really great (as a cms) for someone like a front end dev (rather than say, a generic client who wants to just update content).
A lot of work has been put into the CMS, and to use it effectively you will be extending the October CMS which means doing things the "October way" assuming you want to tie most of your added functionality into some sort of user interface.
If you are ok with learning the ins and outs of October - then it seems like in the long run it will be of benefit.
If you don't go with October - there aren't many alternatives ([packages] which I have come across) which provide a simple foundation and have been updated recently - having said that the core of wardrobe might be something to look into: https://github.com/wardrobecms/core
As for roles/auth - take a look at Entrust (https://github.com/Zizaco/entrust) and Confide - I have used them together in the past and found them functional and easy to use.
(I have no affiliation with any of the packages mentioned above)
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I have used codeigniter for few of my projects in my portfolio and currently seeking a job opportunities. However, I heard yii is a very nice and high demanded php framework in the market now. Is that true? Should I turn my attention to yii or keep building more codeigniter projects in my portfolio for my first web developer job? Thanks for the help.
Well this does not fit here but what i have learned that since 4-5 months industry here have started working on Yii. I have been working on Yii since 4 months it is easy and supports Rapid Application Development.
Moreover performance may be key factor but to me its time to development that this framework allows you. I have worked on CI but Yii is far more ahead of that. provides you nice JQuery implemenation does Ajax validations for you and much more.
I recommend it 100%.
If you see what is in market you may not be able to learn whole things and some how things keep changing once COBOL was famous but now........... so basically on everything I guess factor overrides is Ease and Rapid Application Developement these are provided by Yii
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
If I build a site with Zend framework, and later want to add an e-commerce extension, can I esaily plug Magento? Do have I to rebuild the website from a fresh new magento install?
Thanks.
You do not necessarily have to rebuild the whole website. If you have a lot of CMS pages you would probably keep those and install Magento in order to provide the e-commerce functionality. Although Magento is based on Zend Framework it has its own template system, so I guess you would have to rebuild your theme with the Magento template system.
The Zend framework from Magento is a little bit different of the official one. The Require(...); files are commented. It means that your web application must implement the autoloader of ZF. Additionally you have to pay attention of the ZF version that you use with Magento and your app, it's not always the last version
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 2 years ago.
Improve this question
I have a lot of codes in libraries, helpers, models of my old codeigniter projects.
I want to start a new project that I think I can use those codes without rewriting them. Also, when I want to update the codes in the libraries, helpers or models, I only have to update them once in one file. However if I copy and paste the file to the new project, I have to update each of them when I have an update in the code.
So how can I do this in best practice?
Thank You
Have a look at theis article by Phil Sturgeon - in it he details a way to create a 'shared' folder, so that you can run multiple codeigniter installations from the same shared folder.
http://codeigniter.com/forums/viewthread/136321/
Since Codeigniter 2.0 you can share same system folder among many projects. In previous versions you can do this with a little tweak. So once you have a common system folder you can keep all you libraries and helpers here which can be used by all the projects. There is no provision to have common models so either you can transform them to helper or library class, which actually makes sense.
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 3 years ago.
Improve this question
I want build an application by using the framework.
the application contains two parts: the Back-End and the Front-End.
Everybody who have experiences can suggest me which ways should I do?:
Develop the Front-End first Or Develop the Back-End first
Or give more tips on the start up project?
thanks
I usually start with the backend to get the major functionality implemented, but even so, it's pretty much inevitable that the frontend and backend will have to be developed at the same time at some point in the project.
People can say what they want about separating presentation and functionality, and that's a good principle, but the reality is that the presentation influences the functionality and vice versa.
You might get the backend mostly written, and then you make the frontend, but you will probably decide to change some things and end up working on both together.