Bug #34124
Enhance upgrade wizard to take care of flexform content
| Status: | Closed | Start date: | 2012-02-20 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | 6.0 beta1 | |||
| Votes: | 0 |
Description
Enhance upgrade wizard to take care of flexform content
Related issues
| related to File Abstraction Layer - Task #33951: Carefully check behaviour of upgrade wizards | Resolved | 2012-02-15 |
History
Updated by Steffen Ritter over 1 year ago
what do you mean by this? currently the upgrade wizards do not take of custom field fields within extensions.
Therefore "the missing transformation of file fields within flexform" does not apply?
Updated by Oliver Hader over 1 year ago
Steffen Ritter wrote:
what do you mean by this? currently the upgrade wizards do not take of custom field fields within extensions. Therefore "the missing transformation of file fields within flexform" does not apply?
At a later point the question will be raised on how to deal with FAL in custom extensions.
However, this issue is about the core disposal of files in flexform data structures - the media conent element for instance stores files in XML.
Updated by Ingmar Schlecht over 1 year ago
- Status changed from New to Closed
OK, can we close this issue then and make new issues for the higher level problems (i.e. migration wizard for media field)?
As Steffen already wrote, at the moment the upgrade wizard takes care of no custom fields anyway.
Updated by Oliver Hader over 1 year ago
Ingmar Schlecht wrote:
OK, can we close this issue then and make new issues for the higher level problems (i.e. migration wizard for media field)?
As Steffen already wrote, at the moment the upgrade wizard takes care of no custom fields anyway.
I personally don't care how the issue is called - however it needs to be done.
Are you going to create a new issue then since you already closed this one?