Dumb Apache/LAMP question

Evan Leibovitch evan-ieNeDk6JonTYtjvyW6yDsg at public.gmane.org
Sun Feb 9 07:01:18 UTC 2014


Yup, that was it.

`a2enmod rewrite`, changing the apache conf from  `AllowOverride none`  to
`AllowOverride all` and restarting Apache did it.

Thanks to all who helped me through my stress moments.



On 9 February 2014 00:56, Bob Jonkman <bjonkman-w5ExpX8uLjYAvxtiuMwx3w at public.gmane.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 14-02-09 12:52 AM, Evan Leibovitch wrote:
> > I'm thinking that mod-rewrite wasn't enabled on Apache in this
> > installation. Would that do it?
>
> Yup. If mod-rewrite is installed then a correct .htaccess file will
> enable it; if it's not installed then you need to install it.
>
> - --Bob.
>
>
> > On 9 February 2014 00:39, David Thornton <northdot9-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org>
> > wrote:
> >
> >> Option +Indexes, or possibly DirectoryIndex need index.php for
> >> the path in question.
> >>
> >> David Thornton
> >>
> >>
> >>
> >> On Sun, Feb 9, 2014 at 12:13 AM, ted leslie
> >> <ted.leslie-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org> wrote:
> >>
> >>> gttp://foo.bar/[whatever_path}/  ? above refers to a path not
> >>> content, is this the issue? try to ref. a image in the dir.
> >>>
> >>> It sounds like a MVC issue , just relating it to what i do in
> >>> asp.net on Mono on linux. I assume php can be set up for MVC,
> >>> and the path should relate your controller, and like with
> >>> asp.net (even on apache), it wouldn't be the View of the file
> >>> as per normal apache View (unless the controller passes on it),
> >>> it would be the View dictated by the controller (and thus by
> >>> the path). If you are not doing MVC, then this isn't the
> >>> issue.
> >>>
> >>> -tl
> >>>
> >>>
> >>> On Sat, Feb 8, 2014 at 11:45 PM, Evan Leibovitch
> >>> <evan-ieNeDk6JonTYtjvyW6yDsg at public.gmane.org> wrote:
> >>>
> >>>> I'm having a total brain fart right now with a site.
> >>>>
> >>>> It's running Wordpress. Pages that explicitly end in .php are
> >>>> found and run fine, anything else (which is most of the CMS
> >>>> content) is just giving a file-not-found 404.
> >>>>
> >>>> so
> >>>>
> >>>> http://foo.bar/[whatever_path]/foo.php works fine, but
> >>>> gttp://foo.bar/[whatever_path}/ gives a 404 file not found,
> >>>> even if the path is correct inside the CMS (I know it's
> >>>> inside the CMS because the .php files on the admin side work
> >>>> fine.
> >>>>
> >>>> What's missing? What is done to make the content fetched from
> >>>> the CMS rather than the Apache filesystem?
> >>>>
> >>>> Any help is appreciated.
> >>>>
> >>>> -- Evan Leibovitch Toronto Canada
> >>>>
> >>>> Em: evan at telly dot org Sk: evanleibovitch Tw: el56
> >>>>
> >>>>
> >>>
> >>
> >
> >
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.14 (GNU/Linux)
> Comment: Ensure confidentiality, authenticity, non-repudiability
>
> iEYEARECAAYFAlL3GKMACgkQuRKJsNLM5eo4YQCgxosuV/3GZAt/s8HSKXxBiptD
> xeQAn2jV1QpqQL0o12fZmdpl2DYafLR3
> =XVHz
> -----END PGP SIGNATURE-----
> --
> The Toronto Linux Users Group.      Meetings: http://gtalug.org/
> TLUG requests: Linux topics, No HTML, wrap text below 80 columns
> How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists
>



-- 
Evan Leibovitch
Toronto Canada

Em: evan at telly dot org
Sk: evanleibovitch
Tw: el56
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gtalug.org/pipermail/legacy/attachments/20140209/2b72ea27/attachment.html>


More information about the Legacy mailing list