Symfony4安装cache/cache-bundle遇dotenv布尔类型解析报错求助

I’ve run into this exact problem before with older Symfony 4 Flex projects and third-party cache bundles, so let’s break down what’s happening and how to fix it.

The Root Cause #

The error Invalid type for path "cache.session.enabled". Expected boolean, but got string happens because even though you’re using %env(bool:SESSION_CACHE_ENABLED)%, either:

1. The cache/cache-bundle’s configuration validator doesn’t properly handle Symfony’s environment variable type conversion, or
2. Your Symfony 4.0 installation uses an older version of the env processor that doesn’t reliably convert string "true"/"false" values to booleans when referenced directly in bundle config.

Even though your .env file has the correct values, the bundle’s config system is still seeing the raw string instead of the converted boolean.

Fixes & Workarounds #

1. Use Parameter Conversion (Most Reliable)

Symfony’s parameter system handles type conversion better than direct env references in bundle configs. Here’s how to set it up:

First, add parameter definitions in config/services.yaml to convert the env strings to booleans:

parameters:
    session_cache_enabled: '%env(bool:SESSION_CACHE_ENABLED)%'
    router_cache_enabled: '%env(bool:ROUTER_CACHE_ENABLED)%'

Then update your config/packages/cache.yml to use these parameters instead of direct env calls:

cache:
  session:
    enabled: '%session_cache_enabled%'
    service_id: "cache.provider.default"
    use_tagging: true
    ttl: 7200
  router:
    enabled: '%router_cache_enabled%'
    service_id: "cache.provider.default"
    ttl: 86400
  logging:
    enabled: '%env(bool:APP_DEBUG)%'
    logger: "logger"
    level: "info"

This ensures the boolean conversion happens before the bundle’s config validator checks the value.

2. Use Expression Language for Direct Conversion

If you want to skip adding parameters, you can use Symfony’s expression language to convert the env string to a boolean directly in the cache config:

cache:
  session:
    enabled: "=bool(%env(SESSION_CACHE_ENABLED)%)"
    # ... rest of your config
  router:
    enabled: "=bool(%env(ROUTER_CACHE_ENABLED)%)"
    # ... rest of your config

The expression =bool(...) explicitly converts the string value from .env to a boolean, which the bundle’s config system will accept.

3. Ditch the Third-Party Bundle (Recommended for Your Use Case)

Since you already have symfony/cache in your dependencies, you don’t need cache/cache-bundle to implement an in-memory "pseudo database" for arrays. Symfony’s native cache component is more integrated and easier to use for this purpose.

Here’s a quick example of how to cache an array using Symfony’s built-in CacheInterface:

1. Inject the cache service into your controller or custom service:

use Symfony\Contracts\Cache\CacheInterface;

class PseudoDatabaseService
{
    private $cache;

    public function __construct(CacheInterface $cache)
    {
        $this->cache = $cache;
    }

    public function getCachedData(): array
    {
        // The cache will return the stored array if it exists; otherwise, it runs the callback to generate it
        return $this->cache->get('pseudo_db_data', function () {
            // Replace this with your array data (simulated database content)
            return [
                'users' => [
                    ['id' => 1, 'name' => 'Alice'],
                    ['id' => 2, 'name' => 'Bob']
                ],
                'products' => ['Laptop', 'Phone']
            ];
        });
    }
}

2. If you want to ensure it’s stored in memory (not persisted), use the cache.system pool instead of the default cache.app (which may use files depending on your config). You can inject it explicitly by configuring the service:

# config/services.yaml
services:
    PseudoDatabaseService:
        arguments:
            $cache: '@cache.system'

This approach is more aligned with Symfony 4’s best practices and avoids the third-party bundle’s config issues entirely.

Final Note #

This is almost certainly a problem with the cache/cache-bundle recipe or the bundle’s own configuration handling, not Symfony itself. The recipe uses env syntax that the bundle doesn’t properly validate, leading to the type mismatch error.

内容的提问来源于stack exchange，提问作者3d0