- Is oro/layout-cache a Laravel package?
- No. It is an OroCommerce/Symfony bundle called OroLayoutCacheBundle that provides render caching for OroCommerce storefront layouts. It does not follow Laravel package conventions such as service providers, facades, or Laravel cache contracts. Laravel teams should not treat it as a drop-in Laravel view or response cache.
- Can I install oro/layout-cache in a Laravel app with Composer?
- Composer may install the PHP code, but bootstrapping it in Laravel would require bridging Symfony dependency injection, Oro platform dependencies, layout metadata, storefront context, and cache-key semantics. That bridge would be fragile and likely larger than a Laravel-native cache implementation. It is only materially feasible inside a compatible OroCommerce stack.
- What does oro/layout-cache actually cache?
- It caches OroCommerce storefront layout resolution and render data or metadata to reduce repeated layout overhead. Its behavior is tightly coupled to Oro's layout rendering model, storefront context, and cache invalidation rules. It is not a generic Laravel view, fragment, or response cache.
- How do I configure TTL for oro/layout-cache in Laravel?
- There is no documented Laravel configuration path because the package does not follow Laravel config or service provider patterns. TTL and cache behavior are Oro/Symfony bundle concerns rather than Laravel cache store settings. For Laravel, configure TTL directly on Laravel cache repositories or response and fragment caching layers.
- How do I clear or invalidate oro/layout-cache?
- The bundle provides Oro-specific cache invalidation helpers tied to layout changes and storefront context, with details depending on the OroCommerce version and deployment. Incorrect invalidation can serve stale prices, promotions, localized content, or customer-group-specific layouts. In Laravel, use explicit cache keys, tags where supported, and invalidation on content, price, or rule changes.
- Does oro/layout-cache support Laravel 10 or Laravel 11?
- There is no meaningful Laravel compatibility matrix because the package does not target Laravel. It is an OroCommerce/Symfony bundle, so compatibility should be assumed unproven until checked against PHP, Symfony, OroCommerce constraints, and deprecated Oro layout APIs. For Laravel 10 or 11, use native cache, response caching, and fragment caching mechanisms.
- What are Laravel alternatives to oro/layout-cache for view and layout caching?
- Use Laravel Cache with tags where the store supports them, response caching middleware, fragment caching, cache locks, and explicit invalidation on content or rule changes. For layout path resolution, cache resolved paths and render metadata with application-specific keys and TTL. These Laravel-native approaches avoid bridging Symfony DI and Oro platform dependencies.
- Is oro/layout-cache safe for production in 2026?
- It is high risk for Laravel production because it has 0 stars, 0 dependents, a score of 0, no release since 2020-09-11, NOASSERTION license ambiguity, and no visible community or vendor support. Oro-specific cache invalidation is also high risk if stale prices, promotions, localized content, or customer-group layouts are served. Validate license status, version compatibility, cache backend assumptions, invalidation events, and support path before any production use; for Laravel, do not use it.
- How do I test oro/layout-cache cache hit and miss behavior?
- Testing would require an OroCommerce/Symfony test setup with layout metadata, storefront context, a configured cache backend, and invalidation events; it is not a Laravel test harness. Measure cache hit ratio, invalidation latency, and tenant or store isolation as part of that Oro-specific setup. In Laravel, test native cache keys, TTL, and invalidation with a fake cache store and feature tests instead.
- Should we migrate from OroCommerce to Laravel and reuse oro/layout-cache?
- There is no credible migration path from this package into Laravel. Treat it as a reference for cache-key and invalidation concepts, not as a port target, and reimplement the required behavior against Laravel's cache and rendering pipeline. If the organization remains on OroCommerce, use the bundle only after validating version compatibility and license status, or prefer Oro-supported caching features and an internal implementation aligned to the deployed Oro version.