I want to see all Bug fix of cakephp framework. for other php framework Bug fixes are located in change log file in framework, but in cakephp i can't find any changelog file. where i cat find this file?
Cakephp doesn't have a changelog file in the repository.
You can either browse trough the github versions for a short textual changelog:
https://github.com/cakephp/cakephp/releases
Alternatively you can read the changes in the cakephp news:
http://cakephp.org/pages/news
Or if you want see the granular changes you can browse the source code by tags: https://github.com/cakephp/cakephp/tree/2.6.6
CakePHP Folder Structure
bin
config
logs
plugins
src
tests
tmp
vendor
webroot
.htaccess
composer.json
index.php
README.md
The logs folder normally contains your log files, depending on your Logging Configuration.
Make sure that the tmp and logs folders exist and are writable, otherwise the performance of your application will be severely impacted. In debug mode, CakePHP will warn you, if it is not the case.
Related
I have a Laravel 5.3 project versioned, and files in this folder are constantly changing.
Is safe to remove from version control system?
If I delete that folder from my working copy, Laravel can keep working?
folder structure
You'll notice in a default Laravel 5.3 install there are 3 folders within storage. It looks like this:
+ storage
+ app
+ framework
+ logs
And each of those subfolders has a .gitignore as well as other folders (also usually with gitignores. Those .gitignore files generally say to ignore all files except for the .gitignore. For example, this is the .gitignore inside storage/logs:
*
!.gitignore
That means that you can keep this in version control, but any file written to that folder (except for the .gitignore file itself) will NOT be in your git repository.
Also, it might help to know that these folders have a specific purpose:
app: Designed to be used as storage for files outside of your root public folder
framework: By defaut, this is where Laravel writes a lot of its files for cache and views
logs: Where the error logs are written
If you delete the root storage folder or these subfolders, the framework will have trouble finding these files and you'll get errors.
I'm trying to copy an existing Symfony project to another directory, so I can test changes before applying them to the live version.
I get a 404 error whenever I try to access the project on the copy via app.php or app_dev.php, and I can't pin down why. The live project is in a folder called representation/mvcrep and the copy is in a folder called representation_dev/mvcrep, and they are both on the same hierarchy in the directory tree.
I've already successfully cleared the cache for both the dev and prod environments in the copy, with no decipherable result. There are no errors in the Symfony logs, and the 404 is one for the site not for Symfony, so I'm assuming it's a problem with the server. Both projects have the exact same permissions as well.
Anyone have any clue to what the problem could be?
Edit: To clarify, the web directory has not been renamed or modified.
As you reported that you use two subfolders in the same virtual host, the web server configuration is probably not the issue here.
Since I suspect permissions issues, I suggest you to debug by creating a base text file in the /representation_dev/mvcrep/web folder, e.g. hello.txt, and see if you can get that via browser.
If not, check the permissions on the newly created folder.
There is not enough info for a precise answer, but this sounds definitely more like a server configuration issue than a Symfony issue,
If you make a copy of your Symfony folder, you also need to create a new web site that points to the new installation.
I.e. previously you browsed the site
http://representation.local/
which has its web root in
.../representation/mvcrep/web
Now you need to create a new site
http://representation_dev.local/
which has its web root in
.../representation_dev/mvcrep/web
I am created a Symfony2 project in NetBeans 7.3 .
The project created successfully but NetBeans shows syntax errors in some of vendor package files of my Symfony2 project.
All things that i did was :
1.Download netbeans 7.3(php) and install it.
2.Download "Symfony 2.3.2 with vendors" zip file.
3.Insert into tools-->Symfony2 the adress of zip file.
4.Created the project.
Errors are from 5 or 6 file on vendor package files , some of them are PHP files and others are twig files.
i apperciate for any bit of help.thansk
Netbeans will show errors in some of the vendor files because, well, they contain "errors". For example, under the Sensio generator bundle, there are some template type controller files with a php extension. The files themselves are not valid php and hence get flagged by netbeans.
It is annoying but it's just something you have to ignore. Or maybe coax the vendors to tweak their code. Some folks are trying to get netbeans to skip these sorts of errors but no luck so far.
More info here: https://netbeans.org/bugzilla/show_bug.cgi?id=226954
As Cerad pointed, those files are not valid PHP files (for instance, skeleton files).
In Netbeans 7.3 you can ignore folders which means Netbeans won't show them in the UI or index or scan them.
So, If you don't need to work with those files, just go to projects properties -> Ignore folders, and add the problematic folders there (in your case, "vendors").
More info: https://blogs.oracle.com/netbeansphp/entry/ignored_folders_sure
I am trying to deploy a Lithium app on Heroku, but Heroku uses a read-only file system for apps. This causes a problem with the app/resources folder. I've tried looking for a setting the lithium config to change the path to this folder, but it appears to be hard coded.
Can anyone recommend how to resolve this issue?
Lithium uses the /resources folder for writing temporary files such as logs, file caches, compiled PHP templates, etc.
The path is configurable through Libraries::add() when the application is initialized. In config/bootstrap/libraries.php, you can replace your application's Libraries::add() call with one like the following: https://github.com/orchestra-io/sample-lithium/blob/master/app/config/bootstrap/orchestra.php#L10
This configuration uses the system's temp directory, and checks for/initializes the subdirectories Lithium will use.
Let's say you have a big web app with large visits, but you don't want your app to crash & you don't want people to see the php or mysql errors that happens during replacing files using FTP, How to avoid that? How to just execute the old version of file until the replacing is done?
Thanks
you can follow at least one of this 2 rules:
to use accelerators (like APC) with turned off mtime checking. so until you clear cache manually - old versions will be used from memory
to use virtualhost symlinked to directory with your project: let's examine you store yout project at /home/project/www. and /home/project/public_html is your real webroot and symlinked to www. so - create /home/project/www2, checkout files there, setup and do whatever you want. after this - just change symlink.
I use git to upload my changes to a staging website on the same server, after testing I then push it to the production website. None of the files are changed until they are all received. On the plus side, it only sends the changes compressed, so I don't even have to send an entire file.
The staging area isn't required. I work with a lot of servers and sometimes some of the specific configurations on that server (mostly just find that an extension isn't installed)/
I'm sure you can do the same with another version control system. You need to be careful though. The tutorial I linked specifically stores the git information OUTSIDE the document root. Otherwise someone can just clone all the source code for your website.
If you like SVN, the .svn being in every directory can be a little annoying. Make sure that people can't download what they shouldn't be able to.
Deploy your app into the temporary directory. Then after you done, just rename the original app directory to app.old and the directory where you deployed your files into app
Note this should work okay in Unix environments. Also this will only work if all of the above directories are on the same file systems. In rare case users might see 404 error if they happen to access the app after your renamed the original app into .old and before you renamed temp dir into the original app directory.