Using ‘DirectoryIndex’ : Cache Enabler stops working

  • Resolved aplusdesign

    (@aplusdesign)


    7 years, 3 months ago

    I ran into a problem I have not been able to fix. I usually remove the root index.php from WordPress installs for extra security and force Apache to look for a differently named file.

    For example in .htaccess

    # Load blog.php first if it exists.

    DirectoryIndex blog.php index.php index.html

    This works fine on WordPress so long as you also use

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^blog\.php$ – [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /blog.php [L]
    </IfModule>
    # END WordPress

    When doing this though, cache enabler never creates a cache. No I’m not logged in.

    Do you have a fix in mind or any solution to this, because to me that seems like an oversight to be requiring index.php to be your main/first call to action on Apache.

    I can think of a few more examples where you wouldn’t want an index.php file, but potentially still benefit from the caching of cache enabler.

    ??

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Thread Starter aplusdesign

    (@aplusdesign)

    What are the odds of a setting in admin area for Cache Enabler to set the “basename” for our root directory.

    So that _is_index() can use an override and not be locked to index.php

    private static function _is_index() {
    return basename($_SERVER[‘SCRIPT_NAME’]) != self::$options[‘basename’];
    }

Viewing 1 replies (of 1 total)
  • The topic ‘Using ‘DirectoryIndex’ : Cache Enabler stops working’ is closed to new replies.

Tags