I am hosting with StoneRocket.net

On 30 mar, 06:20, Stephen Orr <[EMAIL PROTECTED]> wrote:
> Which, so long as your RewriteBase directive takes the form of:
>
> RewriteBase /directory
>
> Will be exactly right. If this isn't working for you, I suggest
> contacting your hosting company for further support. Cake has worked
> successfully for me every time, deploying onto many different servers
> and hosting environments, in most cases without having to change a
> single line of core code.
>
> Out of interest, who are you hosting with?
>
> On Mar 30, 2:47 am, Raistlin Majere <[EMAIL PROTECTED]> wrote:
>
> > The log file says:
>
> > RewriteBase takes one argument, the base URL of the per-directory
> > context
>
> > On Mar 29, 1:03 pm, "Dardo Sordi Bogado" <[EMAIL PROTECTED]> wrote:
>
> > > Then go and read the server error log as the message suggests.
>
> > > On Sat, Mar 29, 2008 at 12:04 PM, Raistlin Majere <[EMAIL PROTECTED]> 
> > > wrote:
>
> > > >  I got:
>
> > > >  "500 Internal Server Error"
>
> > > >  "More information about this error may be available in the server
> > > >  error log."
>
> > > >  "Additionally, a 500 Internal Server Error error was encountered while
> > > >  trying to use an ErrorDocument to handle the request."
>
> > > >  On Mar 28, 7:45 pm, Галкин Николай <[EMAIL PROTECTED]> wrote:
> > > >  > I think yes! Create the file .htaccess in the root directory and 
> > > > write
> > > >  > string:
> > > >  > RewriteBase /new_root_folder
> > > >  > But in your hosting must be enabled module mod_rewrite.
> > > >  > Sorry for my English. I am from Russian.
>
> > > >  > > Can I change document root in shared hosting?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake 
PHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to