Re: Applications build with 1.2.6 could run with 1.2.8?

Write permission is needed only for directories/files you write to.
That would be only the app/tmp directory if you're not using file
uploads. The rest of the files should be read-only for the web server
to prevent accidental or malicious writes. The "execute" permission is
really only needed for directories where it means "permission to list
files."

If you don't have CSS there's probably something wrong in your
mod_rewrite configuration.

On Aug 27, 10:33 pm, saidbakr <said....@gmail.com> wrote:
> I found that it is a matter of permissions. However the Cake
> documentation does not offer clean and detailed explanation for
> permissions. I changed all permissions to read, writeand execute for
> all users after that it worked with my application. However, the
> default cake app is not rendered as exepected, it returns some errors
> in the header of the page and there is no CSS layout for it as
> gollows:
> *******************
> Strict Standards: Redefining already defined constructor for class
> Object in ...cake/libs/object.php on line 62
> Deprecated: Assigning the return value of new by reference is
> deprecated in .../cake/libs/inflector.php on line 130
> Deprecated: Assigning the return value of new by reference is
> deprecated in ../cake/libs/configure.php on line 135
> ...
> ******************
> By the way I use XAMPP - LAMPP - on Ubuntu 10.04
>
> On Aug 27, 8:10 am, jsalonen <joni.salo...@gmail.com> wrote:
>
>
>
> > I've upgraded an application through many versions of Cake 1.2.x,
> > starting with one of the release candidates, and there have never been
> > any problems. Is it possible you had changed the default include path
> > in index.php or in app/webroot/index.php? The upgrade might have
> > overwritten those files and now the application is using the default
> > paths again.
>
> > This is one reason why you should always work under version control:
> > you would immediately see what has changed and would be able to revert
> > inadvertent changes.
>
> > On Aug 27, 2:54 am, saidbakr <said....@gmail.com> wrote:
>
> > > Hi,
> > > I have an application build with CakePHP 1.2.6. I downloaded CakePHP
> > > 1.2.8 and then I replaced the current cake folder with the new cake
> > > folder, where all paths are kept without change. However, the cake
> > > does not able to work with the new 1.2.8.
>
> > > In other word: my cake 1.2.6 library was found in /home/myuser/www/
> > > cake at which there are 3 folders and two files with the following
> > > structure:
> > > app, cake, vendors, index.php and README
>
> > > The new 1.2.8 has been copied to the same path with the same folder
> > > structure, but It does not work and give out the following error
> > > message:
> > > *********************************
> > > Warning: include(cake/bootstrap.php) [function.include]: failed to
> > > open stream: No such file or directory in...
> > > ...
> > > Fatal error: CakePHP core could not be found. Check the value of
> > > CAKE_CORE_INCLUDE_PATH in APP/webroot/index.php. It should point to
> > > the directory containing your /cake core directory and your /vendors
> > > root directory. in...
> > > ************************************
> > > Is there any confilict or missing something between 1.2.6 and 1.2.8?

Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions.

You received this message because you are subscribed to the Google Groups "CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en