• Resolved TRILOS

    (@trilos)


    The notice
    define(‘WP_CACHE’, true); is not set in wp-config.php.
    still appears, even when the definition is definitely containd in wp-config.
    It works when inserted directly after <?php
    This is known since at least a year… please get it fixed.

    • This topic was modified 5 years, 8 months ago by TRILOS.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Anonymous User 16850768

    (@anonymized-16850768)

    There are a few reasons why this may be occurring. Is the notice still shown if you deactivate the Cache Enabler plugin and then activate it again? If yes, do you have any other settings defined in your wp-config.php file by a previously used caching plugin? If no, does your hosting provider allow the Cache Enabler plugin?

    Thread Starter TRILOS

    (@trilos)

    The notice is still shown if I deactivate the Cache Enabler plugin and then activate it again.

    Now, with Plugin Version 1.3.3, it does not seem to be necessary to place
    define('WP_CACHE', true);
    at the beginning of wp-config.php.
    But it does not work when we place it at the end of wp-config.php!
    If I do place the line after the former last line
    require_once(ABSPATH . 'wp-settings.php');
    the notice appears again.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘define(‘WP_CACHE’, true); is not set in wp-config.php.’ is closed to new replies.