I have been trying to set up cake 1.3.8 with an "advanced
installation" configuration on a subdomain of a shared host, without
success. I got very close, with everything working except that some
pages would not open when clicking the link. This was especially the
case when switching
Apologies if this has already been discussed in the group, but I could
not find it. I have an advanced installation on Windows running wamp,
which I tested first with the app folder containing webroot at the
document root and the cake libraries above the document root. The
initial test setup
"under the surface"
> only /home/app[0|1]/webroot is public
>
> therefore no changes have to be made to any index.php or .htaccess
> files
> and you could use several domains or subdomains.
>
> On 17 Jun., 16:59, Felix wrote:
>
>
>
> > Hi,
>
> > I
fore no changes have to be made to any index.php or .htaccess
files
and you could use several domains or subdomains.
On 17 Jun., 16:59, Felix wrote:
> Hi,
>
> I new to cake and trying to install it using the advanced installation
> so only have one copy of the 'cake' d
Hi,
I new to cake and trying to install it using the advanced installation
so only have one copy of the 'cake' directory to use for all my
projects.
The directory structure I use is:
/home
/protected (- location of '/cake' directory)
/public (- where all
ng to install cake on my server using the advanced
> installation instructions. When I do a normal install everything
> appears to work correctly. However, when I attempt to move the cake
> folder all I get is a blank screen.
>
> Here is the configuration I am trying to achieve:
&g
0, at 9:15 AM, Raydon wrote:
> Hi,
>
> I'm attempting to install cake on my server using the advanced
> installation instructions. When I do a normal install everything
> appears to work correctly. However, when I attempt to move the cake
> folder all I get is a blank screen.
Hi,
I'm attempting to install cake on my server using the advanced
installation instructions. When I do a normal install everything
appears to work correctly. However, when I attempt to move the cake
folder all I get is a blank screen.
Here is the configuration I am trying to achieve:
folder).
I have read the following: http://book.cakephp.org/view/35/Advanced-Installation
but I cannot seem to get it to work.
I have modified the index.php file (webroot) and know I will need to
modify the core "paths.php" file. If anybody has done anything similar
and could post th
sed, so the tmp folder needs to be moved to the webroot (as
> well as the config folder).
>
> I have read the following:
> http://book.cakephp.org/view/35/Advanced-Installation
> but I cannot seem to get it to work.
>
> I have modified the index.php file (webroot) and know I will
Yes, having CakePHP and the applications on the same level works!
Enjoy,
John
On Apr 7, 10:34 am, Ernesto wrote:
> Hello.
>
> i have the following situation
>
> www (where apache points to)
> some_stuff
> cakephp
> apps
> cake_app_one
>
Hello.
i have the following situation
www (where apache points to)
some_stuff
cakephp
apps
cake_app_one
cake_app_two
cake_app_three
other_stuff
i tried to modify the app/webroot/index
Cool - got it working (at least locally). here's my setup:
AppServ\www\cake\
AppServ\www\cake\cake\
AppServ\www\cake\docs\
AppServ\www\cake\vendors\
AppServ\www\cake\index.php
AppServ\www\acakesite\app\config\
AppServ\www\acakesite\app\controllers\
AppServ\www\acakesite\app\models\
AppServ\www\
> Once the local testing is done, how would the actual production site
> be configured?
> can the cakephp libs/core be hidden one directory above the www on the
> production servers?
yes, this I think would be considered best practice. Just move the
cakephp dir to the same level as www (not insid
Once the local testing is done, how would the actual production site
be configured?
can the cakephp libs/core be hidden one directory above the www on the
production servers?
on a related note, are there any disadvantages of the cakephp libs/
core being placed one directory above the public_html
> D:\AppServ\www <-- http docs root (localhost)
> D:\AppServ\www\onesiteroot <-- one web project
> D:\AppServ\www\anothersiteroot <-- another web project
> D:\AppServ\www\heresanothersite <-- yet another web project
this is very easy, place cakephp dir (inc app, webroot etc) in the
root of yo
Thanks for the reply, guys...
Well, I use AppServ at home (much smaller and 'simpler' than Xampp...
www.appservnetwork.com ).
Been using that for the past 4 years (all PHP stuff)...
Since a lot of my projects are becoming quite large and complicated,
instead of myself building my own framework, I
I'm with kabturek on this one. I'd stick with the initial download
setup until you learn the ins and outs of cake and its structure. It's
simple, just drop the whole download into a folder accessible by your
browser, make sure mod_rewrite is on, set up your database.php file
in /app/config/ and yo
>From what you've written you seem to want to develop an app - woudn't
it be wiser to use the *developement* setup ? ;) probably on your home
machine ? You want a production setup for dev ... imo you should
stick with the basic setup for now - and when you actually learn cake
- there is no proble
What if I did NOT want the webroot files to be at the actual webroot
(at least during develpment/testing, where there are multiple websites
on a shared server?)
i.e. How can I move the /cake_install/app/webroot files into /
public_html/app/webroot WITHOUT having to set the actual www webroot
to b
This is the structure that I was thinking of...
/cake/cake/
/cake/cake/config/
/cake/cake/docs/
/cake/cake/libs/
/cake/cake/scripts/
/cake/cake/app_controller.php
/cake/cake/app_model.php
/cake/cake/basics.php
/cake/cake/bootstrap.php
/cake/cake/dispatcher.php
/cake/vendors/
/public_html/app/ <-
I'm new to CakePHP - ready to learn it - so I'm trying to set it up on
a shared hosting account.
currently, when I log into my account via FTP, i get into one level
above the public_html (webroot).
I'd like to put the CakePHP libraries/framework there... and all of
the site's stuff (i.e. "apps/v
hey work fine, no problems at all.
>
> My personal site is installed slightly differently, with htdocs being
> alongside the other folders (I originally followed the advanced
> installation tutorials on the Wiki, and wanted to keep the application
> files out of public access).
&g
docs. They work fine, no problems at all.
My personal site is installed slightly differently, with htdocs being
alongside the other folders (I originally followed the advanced
installation tutorials on the Wiki, and wanted to keep the application
files out of public access).
Now though, I want
24 matches
Mail list logo
