http://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692015-10-22T14:55:55ZTYPO3 ForgeTYPO3 Core - Task #70899: Streamline FAL "status"http://forge.typo3.org/issues/70899?journal_id=2826302015-10-22T14:55:55ZXavier Perseguersxavier@typo3.org
<ul><li><strong>Category</strong> set to <i>File Abstraction Layer (FAL)</i></li></ul> TYPO3 Core - Task #70899: Streamline FAL "status"http://forge.typo3.org/issues/70899?journal_id=3321072017-05-04T17:48:29ZBenni Mackbenni@typo3.org
<ul><li><strong>Target version</strong> changed from <i>8 LTS</i> to <i>Candidate for patchlevel</i></li></ul> TYPO3 Core - Task #70899: Streamline FAL "status"http://forge.typo3.org/issues/70899?journal_id=3962132019-03-06T21:40:13ZSusanne Moogsusanne.moog@typo3.org
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Needs Feedback</i></li></ul><p>I would not do this, this will break backwards-compatibiltiy - because people might actually store strings in the existing status field - for no good reason. Additionally it would involve writing a migration as the field type cannot be changed while there is data stored in the field (tested on mariadb). I'd say it's not worth the hassle.</p> TYPO3 Core - Task #70899: Streamline FAL "status"http://forge.typo3.org/issues/70899?journal_id=3962152019-03-07T08:40:20ZXavier Perseguersxavier@typo3.org
<ul><li><strong>Status</strong> changed from <i>Needs Feedback</i> to <i>Rejected</i></li></ul><p>Fine then, it's pretty old anyway.</p>