I have been working on a Cake project that was developed and setup by an outside company some time ago. It was setup with Cake 1.3.7 and seems OK for now.
I see that the 1.3 stream of Cake is now up to .17 and think it is about time I applied the update. But How??
I have googled for hours and can find masses of info on migrating to the V2 stream, but we are not ready to do that yet.
So how do I apply the latest patch of 1.3.17 to my environment? I thought it was just a case of replacing the cake folder with the new one but the .17 download has files in other places too, not just the cake folder.
Can anybody tell me what the process is to do this pls?
Thanks
Mark
I think you just have to replace the cake folder with the new version.
Related
I have been upgrading my application from cakephp 3 to cakephp 4. I was using fheider/cakephp-datatables and I have come across ypnos-web/cakephp-datatables where both support cakephp 3.
I am currently looking for a cakephp-datatable plugin which supports cakephp 4.
If anybody has an idea, I would be happy.
Thanks in Advance.
Isn't the built-in pagination is what you are looking for ? you can do advanced dynamic database links with your HTML tables.
I successfully use ypnos-web/cakephp-datatables on CakePHP 4.2.7. It works very well for me.
You might have to play around a bit to get it working correctly. Read some of the issues (open and closed) on the ypnos-web/cakephp-datatables github repository and you can likely get it working.
Good Luck!
I am lost with this and I need help. A point where start. I have been reading other stackoverflow questions but they are all about Joomla 1.5 whose XMLRPC is deprecated. i am working with Joomla! 3.45
I have also read this but it does not explain a thing about how to deal with the request. I have download the example at the end of the page but when I try to install it and see how it works, I get a JInstaller: :Install: Can't find Joomla XML setup file expection.
Could somebody help me? Thanks
Search extensions.joomla.org there is an an extension already for this. you can read the PHP code for that
The CakePHP community has frequent minor release cycles. Can anyone suggest a strategy for selecting an LTS version - specifically a minor version.
Or would the best strategy be to upgrade as frequently as the minor versions are released?
We can assume that the 2.x and 3.x branches get updates for the next few years (i'm not sure, but i think even 1.3 still get security updates if leaks are found)...
So your choice is between 2.x and 3.x where 3.x is cleaner/faster and easier extendible in form of 3th party libraries and 2.x is more wide spread(plugins, tutorials,... ). I would definitely recommend you to go with 3.x due to a higher php version(it's sooo much faster).
Cakephp releases in minor versions (3.0.x) are bug and security fixes. So if you select:
"require": {
"cakephp/cakephp": "3.0.*"
}
you should be just fine for the next few years.
If you than feel like a feature is missing which is present in a newer 3.x release you can always find a migration guide for the newest version in the cookbook: http://book.cakephp.org/3.0/en/appendices/3-0-migration-guide.html as you can see from 2.x to 3.x there are a lot of breaking changes and an update is most likely really time consuming.
In comparison a update from 2.x to 2.6 is less complex as there are primary smaller feature improvements, renaming of functions and stuff like that: http://book.cakephp.org/2.0/en/appendices/2-6-migration-guide.html
CakePHP 3.0.x is the most current branch of CakePHP and if you're starting out with Cake is the best place to start (CakePHP 2.6.x is still being supported for the foreseeable future, but will eventually get dropped).
The recommended way of installing CakePHP is using Composer. If you want to install the current stable release then you want the following in your composer.json file:-
"require": {
"cakephp/cakephp": "3.0.*"
}
This will insure that every time you do a composer update you'll only get bug fixes and minor changes that shouldn't break your app. Ideally you want to ensure your app is bug free so it is a good idea to periodically update Cake with these minor version changes.
When CakePHP 3.1.x is released in the future it is likely to introduce new features that have the potentially to break an app's existing functionality. In this case upgrading needs to be done with caution. You will easily be able to update by modifying your Composer requirement, but the app will need thorough testing. This can potentially be time consuming, so unless you really need the new features is unnecessary.
I would highly recommend CakePHP 3.x if you are starting a new project. However, I was just at the CakePHP Conference in New York and the CakePHP Core Developers indicated they would be supporting 2.x for 2-3 years. That time period greatly hinges upon the community to some degree, they are not just going to stop supporting 2.x. any time soon. They are actually going to backport some of the 3.x features into 2.x. They tentatively plan to Release CakePHP 2.7 and CakePHP 3.1 sometime this summer.
I would also ask have you been using 2.x and what is your comfort level with CakePHP? Depends on the size of the project. I haven't made the jump to 3.x yet, haven't had a new project to try it on yet. I have a ton of code for 2.x like bake scripts and plugins that I have customized, so for profitability on a project I still might consider using 2.x.
There will be some learning with CakePHP 3.x especially if you are coming from 2.x, the ORM is awesome, but it much different than 2.x. So you have to weigh your options. They mentioned tools for upgrading from 2.x to 3.x that might help if you start with 2.x and jump to 3.x later. I don't think at this point I would do that, that is more for people upgrading from 2.x to 3.x. that have existing 2.x projects. I would pick a version and run with it.
The the other answers suggest use composer to install CakePHP. I started using composer about 8 months ago with CakePHP 2.x and love it. With CakePHP 3.x, I recommend using composer, like this if it is installed globally: composer create-project --prefer-dist cakephp/app [app_name]
I am using "tcpdf" vendor file in cakephp 2.X but it is not looking good view. I want every html tag convert properly in pdf file. Please help.
I have found the a blog for you. its will be help you to find your problem.
Read the following blog
Generating PDFs with CakePHP
You will be find a link for demostration of different PDF file generator.
May be I help you.
I have built my own plugins in the past using MPDF, they worked for years, kinda slow on some environments. Recently, I switched to WkHtmlToPdf and love it. I built my own plugin then a few weeks later realized that one already existed. I would recommend using this plugin by Friends of Cake: https://github.com/FriendsOfCake/CakePdf
A lot of the contributor for Friends of Cake are also Core CakePHP developers, so its usually very well coded, tested & documented.
This plugin also works with several PDF generation engines, which is a nice touch!
I am using wkhtmltopdf for few years and it's working very good, quality of PDF you can get from a html is very good, I am also using the cakephp for PDF generation.
I am running this command from cakephp controller
shell_exec("/usr/bin/wkhtmltopdf < SOURCE_HTML_PATH/URL > < DESTINATION_PDF_PATH> ");
You can install stable version wkhtmltopdf for your linux distribution from this link
http://wkhtmltopdf.org/downloads.html#stable
I have been fighting with ACL for two days now and just recently i came across this plugin
alaxos
My question is: Does anyone know if it works with Cakephp 2.3 or higher?
The version that is currently online is not up to date. I won't give any excuse even if I have hundreds, but well, you know, bla bla bla...
That said, I have an updated version that I use with Cake 2.3 projects. I just made a quick download link on my server: you can find it here: http://www.alaxos.org/download/alaxos_acl_2.3.0.zip
And I promise, I'll update my website. Tomorrow...