Re: Re: How to browse to index.php OR index.html on WordPress site?

[Kent West <westk@xxxxxxx>]

On Thu, Feb 22, 2018 at 11:14 PM, @lbutlr <kremels@xxxxxxxxx> wrote:

On 22 Feb 2018, at 20:52, Kent West <westk@xxxxxxx> wrote:
> On Thu, Feb 22, 2018 at 7:32 PM, @lbutlr <kremels@xxxxxxxxx> wrote:
>
> If I'm understanding you, this is not what I want; both index.html and index.php exist. I just need a means of picking either via URL.

Which I am able to do. In fact, something has to specifically tell apache to NOT load a file that is specified by a full path. DirectoryInde only affects what loads the you laid a path ending in /

Okay, I added those three lines to my /etc/apache2/sites-enabled/sitename.conf file:

 .

 .

 .

                DirectoryIndex index.html

#              DirectoryIndex index.php

                AllowOverride None

                Require all granted

        </Directory>

        <IfModule dir_module>

            DirectoryIndex index.php index.html

        </IfModule>

        ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/

        <Directory "/usr/lib/cgi-bin">

                AllowOverride None 

 .

 .

 .

and restarted Apache2.

Now when I browse to sitename.org, I get the index.html file, and when I browse to sitename.org/index.php, I still get the index.html file. So nothing has changed.

I'm still doing something wrong?

>> Wordpress has a pretty complicated .htaccess file, did you check there?
>
> No; it's my understanding that anything I can do in an .htaccess file I can do in the main global config files, that they're mostly just for overrides to those global config files, so I've just focused on the main global config files.

The global config files will not override index.html to index.php, but the .htaccess might.

Googling for a wordpress .htaccess I see the default config contains MANY rewriting conditions.

<IfModule mod_rewrite.c>
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{HTTP_HOST} !^webdav
RewriteRule . /index.php [L]
</IfModule>

I'd be happy to go the .htaccess route, but at this point, I don't have a clue as to where to begin with this information you've provided. I think you've only demonstrated that .htaccess has complexity, not that you've demonstrated the specific complexity I'm needing to reach my goal?

Thanks! 

--

Kent West                    <")))><
Westing Peacefully - http://kentwest.blogspot.com