<div dir="ltr"><p dir="ltr" style="font-family:arial,sans-serif;font-size:13px">For the sys_file to sys_file_metadata conversion you need the old sys_file structure till after you run the wizard. So analyzer step is OK as long you do not drop fields.</p>
<p dir="ltr" style="font-family:arial,sans-serif;font-size:13px">Gr. Frans</p></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/11/22 Markus Klein <span dir="ltr"><<a href="mailto:klein.t3@mfc-linz.at" target="_blank">klein.t3@mfc-linz.at</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi!<br>
<br>
I just read the beta2 release article on <a href="http://typo3.org" target="_blank">typo3.org</a> [1].<br>
<br>
There it is recommended to upgrade in the following order:<br>
1) "Important Actions" and delete the whole cache content (make sure this deletes the whole typo3temp/Caches/* files and also the content of Extbase Reflection Caches - do it manually if not working otherwise!)<br>
2) "Important Actions": Use the "Database Analyser" and let it migrate the data structure<br>
3) "Upgrade Wizards": Walk through all Upgrade Wizards<br>
<br>
On the other hand the Upgrade Wizards suggest the Database Analyzer as the last step to run.<br>
Moreover we got a bug report [2] that reports a problem when not running the Analyzer first.<br>
<br>
So my question: Does the order matter?<br>
In the sense of: Could the Analyzer delete fields that might be necessary to do proper migration in the Upgrade Wizards afterwards?<br>
<br>
If this is the case, we have a chicken-egg-problem and we need a solution for this. One that comes to mind would be to ensure the proper table structure necessary for the wizards in the wizards themselves and let the Database Analyzer do the cleanup in the end.<br>
<br>
Thanks for your feedback.<br>
<br>
Kind regards<br>
Markus<br>
<br>
[1] <a href="http://typo3.org/news/article/typo3-cms-62-lts-beta2-released/" target="_blank">http://typo3.org/news/article/<u></u>typo3-cms-62-lts-beta2-<u></u>released/</a><br>
[2] <a href="http://forge.typo3.org/issues/53810" target="_blank">http://forge.typo3.org/issues/<u></u>53810</a><br>
<br>
------------------------------<u></u>------------------------------<br>
Markus Klein<br>
TYPO3 CMS Active Contributors Team Member<br>
<br>
<br>
______________________________<u></u>_________________<br>
Before posting to this list, please have a look to the posting rules<br>
on the following websites:<br>
<br>
<a href="http://typo3.org/teams/core/core-mailinglist-rules/" target="_blank">http://typo3.org/teams/core/<u></u>core-mailinglist-rules/</a><br>
<a href="http://typo3.org/development/bug-fixing/diff-and-patch/" target="_blank">http://typo3.org/development/<u></u>bug-fixing/diff-and-patch/</a><br>
______________________________<u></u>_________________<br>
TYPO3-team-core mailing list<br>
<a href="mailto:TYPO3-team-core@lists.typo3.org" target="_blank">TYPO3-team-core@lists.typo3.<u></u>org</a><br>
<a href="http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-team-core" target="_blank">http://lists.typo3.org/cgi-<u></u>bin/mailman/listinfo/typo3-<u></u>team-core</a><br>
</blockquote></div><br></div>