Today we need an extended predi, and then
1. When you get down the local update, there is a problem: a controller is repeated, and then leave it alone. Delete the duplicate,
2. Then up vendor"s predis directory online through svn;
3. But one problem found is to prompt class for this controller does not exit;
I would like to ask if it is because of the direct svn up predis folder problem, rather than the online composer require predis; that just repeated the autoload did not find this controller?