TYPO3 Core

Sure, I did not change the core… but the wizard is not shown in the install tool. Is there a condition for that?

I finally got it migrated now. The following things I had to do:

- in public function checkForUpdate, line 138:

    return true;

- in protected function migrateField, line 298:
comment the line

$file = $this->storage->getFile($this->targetPath . $item);

and instead

$resourceFactory = \TYPO3\CMS\Core\Resource\ResourceFactory::getInstance();
$storage1 = $resourceFactory->getStorageObject(1);
$file = $storage1->getFile($this->targetPath . $item);

Otherwise no files where found.

Btw $storageUid = (int)$this->storage->getUid(); alwas returned 2, but it should be 1 (1 is my public storage named files, not fileadmin, 2 is a non public storage).

It seems that this migration wizard is buggy. Is there noone else having such difficulties with it?

I can confirm this behaviour. This is related to #81180 and the "wizard is done" check changed in that issues. It always returns false. After reverting this change, i got the wizard visible again.

Also when getting the file storages from the system, the wizards assumes the default fileadmin storage is the first. This wasnt the case in my installation. I had to change the line from "$this->storage = $storages⁰;" to "$this->storage = $storages¹;". So either a better check for fileadmin storage should be implemented or let the user choose the storage.

I just tried the update again, wizard is shown, but files are not migrated:
File 'uploads/pics/file.jpg' does not exist. Referencing field: fe_users.15.image. The reference was not migrated.

But the files exist.

@Eckl please create a new ticket for this issue. Thanks

@Eckl I retested this on current v8 branch and it worked. Please test again with the latest version from git and create a new ticket if it really does not work. Thank you.

I just migrated the images manually (some images where successful by the updater, the other i have done myself). I think it was because of different sha1 for the images. Sorry, I didn’t have time to wait for a fix for another year since TYPO3 7 is not supported anymore.

I digged into the code and if I could solve it I would have provided a patch, but I couldn’t solve it. I think it is because I have different sha1 saved in sys_file. Some images where updated, some not. So I think this is just on my system since nobody else has this problem. And because I had no time for this (TYPO3 7 is not supported anymore) and I have 1000 other things to do, I decided to fix it manually to get version 8 finally. Keep calm. Just saying.