- Is stealth35/apc-profiler-bundle compatible with Laravel?
- No. It is a Symfony bundle built on Symfony's Bundle class, a DI extension, and a profiler DataCollector that hooks into the Web Debug Toolbar, and it ships no Laravel service provider, facade, or config file. Making it work in Laravel would be a framework substitution problem rather than a normal integration, so it is effectively out of scope for a Laravel application.
- How do I install stealth35/apc-profiler-bundle?
- You install it with Composer and then register the bundle in your Symfony AppKernel, which is the standard Symfony 2 workflow. There is no Laravel package discovery or auto-registration, so nothing happens automatically in a Laravel app. It is only a drop-in fit for a legacy Symfony 2.x project running PHP 5.4 to 5.6 with APC available.
- Which PHP and Symfony versions does this bundle support?
- It targets the Symfony 2.0 to 2.8 era and PHP 5.4 to 5.6, when the original APC extension was still available. APC was removed in PHP 7, so modern environments expose only APCu and OPcache. Symfony 3 and later also require patching because the bundle depends on Symfony 2 HttpKernel, Profiler, and DI APIs that are end-of-life.
- Does the bundle call apc_* or apcu_* functions?
- Given its PHP 5.x and Symfony 2 vintage, it is written against the original apc_* functions rather than the apcu_* equivalents. On PHP 7 and above those functions are undefined unless someone has installed an alias shim, and a shim typically makes the calls silently no-op instead of returning stats. There is no evidence of function_exists guards, so verify this before considering it on any modern runtime.
- What should Laravel developers use instead to inspect APC or APCu cache stats?
- Enable the cache collector in barryvdh/laravel-debugbar, which already surfaces cache hits, misses, and keys inside the debug toolbar. If you need APCu-specific numbers such as memory usage and fragmentation, register a small custom Telescope watcher that calls apcu_cache_info() and apcu_sma_info(). That is roughly 50 lines of code and avoids adding an unmaintained Symfony dependency to your composer.json.
- Does modern Symfony already have a cache profiler panel?
- Yes. Symfony 4.1 and later ship a built-in Cache profiler panel that shows cache adapters, hits, misses, and calls in the Web Debug Toolbar. That panel supersedes this bundle entirely for any supported Symfony version. The bundle only makes sense for legacy Symfony 2 applications that cannot upgrade.
- Is stealth35/apc-profiler-bundle still maintained?
- No. It has around 19 stars, zero dependents, and a maintenance score near 0.285, with no evidence of CI, tests, or recent commits. There is no upstream fix path, no CVE response process, and no upgrade story, so treat it as abandoned code. If you genuinely need the capability, budget for maintaining a fork yourself.
- Can I install this bundle in a Laravel 10 or Laravel 11 project?
- No, and you should not try. The bundle's Symfony 2 component constraints conflict with the Symfony 6 and 7 components that modern Laravel pulls in, so Composer will fail with unsatisfiable requirements or a framework conflict. Adding it to a composer.json that resolves modern constraints is a dead end.
- Why does my app fatal with undefined function apc_cache_info after upgrading PHP?
- The original APC extension was removed in PHP 7, so any apc_* function call becomes an undefined function fatal error on PHP 7 and 8. The replacement is APCu, which exposes apcu_* functions, and OPcache handles the bytecode caching that APC used to do. Any legacy APC introspection code, including this bundle, needs porting to apcu_* before it will run on a supported PHP version.
- How do I safely test the profiler panel without breaking production?
- Install and register the bundle only in a development environment, never in production, and pin the exact legacy versions it was built against. Load the application, confirm the toolbar panel renders and shows cache stats, then repeat the test on an environment where APC or APCu is not enabled to confirm there is no fatal error. If the runtime is PHP 7 or newer, stop and port the capability to a Debugbar or Telescope approach instead.