fix incorrect padding with multibyte strings encryption

Access foreign property in Belongs_To through a getter

Allow developers to set the Content-Disposition header in Response::download()

Even more fluent eloquent model via magic setters

Language fix for Validation.

Update .htaccess

Added Dutch translation for validation rules "date_format" and "required_with".

Change link in comment. (2.2 -> current)

Now it is possible to use Eloquent's magic setters in chains. For example:

    $model->set_foo('foo')->take(10)->set_bar(some_function());
    // ...even though setters 'foo' and 'bar' are not defined on the model

Signed-off-by: Evgeny Kovalev <Evgeny.Kovalev@gmail.com>

Fix for both Russian and English.
NB The bug is fixed for English version V4 already. No language files for other languages for V4.
Signed-off-by: Evgeny Kovalev <Evgeny.Kovalev@gmail.com>

As far as encrypting and paddings are concerned, we are talking about **bytes** and not **characters**. So basic strlen/substr functions must be used instead of their mbstring version.

Update migrator.php

when used in a setup task. The output created didn't add a line ending.

modified IoC::registred()

Returns true if the instance was registered with IoC::instance

Incremented version from 3.2.13 to 3.2.14

Fixed a typo in "Contributing" chapter

Signed-off-by: aeberhardo <aeberhard@gmx.ch>

Signed-off-by: aeberhardo <aeberhard@gmx.ch>

Check application.ssl when setting a secure cookie

Changed Laravel\ namespace prefix in some classes calls in helpers to global.

global, to allow aliases to work, and allow class extending.

Add Macros to tables

get_dirty() comparison is not type safe

get_dirty() must compare using Not Identical (!==) on place of Not Equal (!=).
For example, changing null to false don't make the model dirty.

Most SLL-related code in Laravel checks to see if `application.ssl`
is true before doing an action requiring it. `Cookie::put()` is the
only exception that I've found, to date, that doesn't test for SSL.

This checks to see that the SSL is enabled when attempting to set a
secure cookie.

To verify, set `application.ssl` to false (without this patch) then
run:

	Cookie::put('foo', 'bar', 0, '/', null, true);

You will get an exception because of line 90 in `cookie.php`:

		if ($secure and ! Request::secure())
		{
			throw new \Exception("Attempting to set secure cookie over HTTP.");
		}

With this patch you will not get this error unless both `application.ssl`
is true, and the cookie `$secure` flag is set.