Commits
-------

e35830cf added missing php command

Discussion
----------

Added missing php command

---------------------------------------------------------------------------

by stof at 2012-06-17T20:34:18Z

if you make the phar executable, it will work without using ``php``, thanks to the shebang. But adding the command is indeed a good idea for windows users.

Commits
-------

64cb149a Added a default translator.domains
c0321197 [Doc] Fixed typo in translator recipes

Discussion
----------

Fix translation

Fixed a typo in the doc + Added a default translator.domains :

If someone registers its translations via yaml, he will not provide $app['translator.domains'], so pimple will raise an exeption.

I don't know if it's better to set a default $app['translator.domains'] or to checks if it set before using it.

If someone registers its translation via yaml,
he will not provide $app['translator.domains'],
so pimple will raise an exeption.

Commits
-------

ebd3bbca [docs] Add config example for lighttpd

Discussion
----------

[docs] Add config example for lighttpd

---------------------------------------------------------------------------

by fabpot at 2012-06-15T17:11:49Z

This is a very specific configuration (assets, ...). I don't see any value to add that to the Silex documentation.

---------------------------------------------------------------------------

by j0k3r at 2012-06-16T11:06:48Z

I can remove the assets & favicon part.
I know that few people were looking for the lighttpd configuration for Silex. I put this few lines in the readme file of one my little project so I thought it would be worth it in the official documentation.

Commits
-------

51596d47 Fixed a bug when using http authentication on the security service provider

Discussion
----------

Fixed a bug when using http authentication on the security service provider

Hi Fabien,

When I added HTTP authentication to my Silex application an exception was thrown. Due the exception I wasn't able to use HTTP authentication when I accessed the application through the browser.

I used the following security firewall:
```php
'http-auth' => array(
    'pattern' => '^.*$',
    'http' => true,
    'users' => array(
        // password is foo
        'admin'  => array('ROLE_ADMIN', '5FZ2Z8QIkA7UTZ4BYkoC+GsReLf569mSKDsfods6LYQ8t+a8EW9oaircfMpmaLbPBh4FOBiiFyLfuZmTSUwzZg=='),
    ),
)
```

The following exception was thrown:
```
InvalidArgumentException: Identifier "security.entry_point.http" is not defined
```

It's a small fix and I also added some tests. All tests passed before I committed my changes.

I would appreciate it when you take a look at this pull request.

security service provider

Commits
-------

1c41a6be Removed the swiftmailer autoloading from the service provider

Discussion
----------

Removed the swiftmailer autoloading from the service provider

It is now handled by composer directly once swiftmailer/swiftmailer#212 is merged.

It is now handled by composer directly.

Commits
-------

e4641d41 made the code more readable
c89133e8 simplified some code

Discussion
----------

Code simplification

I propose to simplify some code. What do you think?

---------------------------------------------------------------------------

by stof at 2012-06-15T12:02:47Z

👍

---------------------------------------------------------------------------

by igorw at 2012-06-15T13:06:12Z

Fine with me. But please add an assignment before `setResponse` to keep the lines a bit shorter.

moved the setting of provider values after the registration to avoid having isset calls everywhere in the provider code

Before, the behavior was not consistent. Some values could be overridden
by passing an array as a second argument to the register() method, but
for most of them it did not work (we would have to wrap all definitions
with an isset()). Now, this is more consistent as you can override
everything that is defined in the provider.

If not, defining the Swiftmailer class_path after registering the
provider does not work.

moved the checks for *.class_path parameters to the boot method as people might have defined the parameter after the register method is called