[TYPO3-core] RFC #2126: Updating encryption key sets compat version to same value

[Michael Stucki]

Hi Sebastian,

of course and +1!

Well, I think for so obvious things it is not neccessary to request a change 
permission. Just do that next time, and don't forget to mention it in the 
ChangeLog...

- michael

Am Donnerstag, 29. Dezember 2005 20.44 schrieb Sebastian Kurfuerst:
> This is a CVS patch request.
>
> Type: Bugfix (trivial)
>
> Branch: 4.0
>
> Description:
> After login the wanring box showed me that my encryption key was not
> set. So it set it, and this is the output I got (key is shortened):
>
>  $TYPO3_CONF_VARS["SYS"]["encryptionKey"] = '892c...c83d'
>  $TYPO3_CONF_VARS["SYS"]["compat_version"] = '892c...c83d'
>  Configuration written to typo3conf/localconf.php
>
> Solution:
> forgot a "break". see attached patch.
>
> Trivial change...
> Greets, Sebastian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20051229/eb1e43a8/attachment.pgp