Manager Bundle Laravel Package

Getting Started

First Steps

1. Check Deprecation Notice

   • This package (byscripts/manager-bundle) is deprecated in favor of byscripts/object-manager-bundle.
   • Action: Do not use this package in new projects. Migrate existing usage to the successor bundle.

2. Legacy Codebase?

   • If maintaining an old Laravel 4.x project using this bundle:
     • Review composer.json for dependencies.
     • Locate bundle registration in AppKernel.php (Symfony2-style) or config/app.php (Laravel 4).
     • Replace with byscripts/object-manager-bundle (if compatible with your Laravel version).

3. Quick Verification

   • Run composer show byscripts/manager-bundle to confirm installation.
   • Check vendor/byscripts/manager-bundle/README.md for legacy docs (if any).

Implementation Patterns

Legacy Usage (Laravel 4.x)

If forced to work with this bundle in an old project:

1. Service Registration

   // config/app.php (Laravel 4)
   'providers' => [
       'Byscripts\ManagerBundle\ByscriptsManagerBundle',
   ],
   

2. Manager Service Access

   // In a controller or service
   $manager = $this->get('byscripts.manager');
   // Hypothetical usage (check original docs for actual methods)
   $result = $manager->doSomething();
   

3. Configuration

   • Look for config/packages/byscripts/manager.yml (Symfony2-style).
   • Override settings via app/config/config.yml:

     byscripts_manager:
         some_setting: value
     

4. Event Listeners

   • If the bundle dispatched events (e.g., byscripts.manager.event), bind listeners in app/config/config.yml:

     services:
         my_listener:
             class: My\Listener
             tags:
                 - { name: kernel.event_listener, event: byscripts.manager.event, method: handle }
     

Gotchas and Tips

Critical Issues

1. Deprecation Risk

   • No active maintenance (last release: 2014). Avoid in new projects.
   • Breaking changes likely in Laravel 5+ (this bundle targets Laravel 4.x).

2. Laravel 5+ Incompatibility

   • Uses Symfony2 components (e.g., DependencyInjection). Laravel 5+ dropped Symfony2-style bundles.
   • Migration Path: Replace with byscripts/object-manager-bundle or a modern alternative like:
     • Laravel Object Manager (if functionality overlaps).
     • Custom service containers or repositories.

3. Configuration Quirks

   • No clear docs: Assume YAML-based config (Symfony2 style).
   • Service names: Hypothetical; verify with php app/console container:debug (if Symfony CLI is available).

4. Debugging

   • Dump the container:

     $this->app->bind('debug.container', function() {
         return $this->app;
     });
     dump($this->app['byscripts.manager']);
     

   • Check for deprecated calls in logs (Laravel 4’s deprecation channel).

Extension Points (Legacy)

• Override Services:

  # app/config/config.yml
  services:
      byscripts.manager:
          class: My\CustomManager
          arguments: [...]
  

• Monkey-Patch Methods: Use Laravel 4’s App::extend() or Symfony’s compiler_pass (if available).

Migration Checklist

1. Replace byscripts/manager-bundle with byscripts/object-manager-bundle in composer.json.
2. Update service bindings (check new bundle’s docs for API changes).
3. Replace Symfony2-style config with Laravel’s config/manager.php.
4. Test all manager-dependent features.