Bug #58624
closed
InstallTool : migrateAbsoluteFilemounts
0%
Description
Hi,
the UpdateWizard::migrateAbsoluteFilemounts tries to touch a file (/typo3/sysext/core/Classes/Resource/StorageRepository.php line 263)
while testing CaseSensitivity in a directory that does not exist (testCaseSensitivity("/user_upload/news/"))
TYPO3\CMS\Core\Resource\StorageRepository::createLocalStorage(
"News (auto-created)", "/user_upload/news/", "absolute", "... has been created by the TYPO3 upgrade wizards.")
Updated by Markus Klein almost 10 years ago
- Status changed from New to Needs Feedback
So what is the problem?
Why do you have filemounts that do not exist?
Updated by Ronald Wopereis almost 10 years ago
I have the same problem, after upgrading from 6.2.0 to 6.2.2
My site (root) tree is
(1) my own site
(2) bootstrap package
Since my own site doesn't use news, i guess it is from the second root which is the bootstrap package.
Anyway, even when i mkdir /var/www/{mysite}/user_upload/news , the error still occurs
I added for 6.2.2. a reproduction scenario here:
http://wiki.typo3.org/Exception/CMS/1
Updated by Daniel Wagner almost 10 years ago
This filemount is from the bootstrap package (data.t3d contains some filemounts: news, images, documents,...).
But touch tries "/user_upload/news/aAbB" which surely does not exist. Maybe my first try of the upgrade wizard already converted the absolute path and now we are stuck.
Updated by Markus Klein almost 10 years ago
I read the Wiki scenario and I'm asking myself a few questions:
- Why do these wizards show up at all? Did you run all of the wizards when updating to 6.2.0? Or was that a new installation?
- Why do you execute the upgrade wizards for a bugfix update?
First we need to find out why the wizards is showing up, this should not be the case on a clean 6.2 installation.
Updated by Daniel Wagner almost 10 years ago
Actually it does NOT appear anymore. I upgraded to PHP 5.5, but that's should not have solved the problem.
I run the updrade wizard although it was a fresh 6.2 installation because it appeared and I had troubles with the distribution package.
Updated by Markus Klein almost 10 years ago
So if it does not show up anymore, I guess we can't reproduce this.
Updated by Markus Klein almost 10 years ago
- Target version deleted (
next-patchlevel)
Updated by Alexander Opitz over 9 years ago
Hi,
was this issue fixed with TYPO3 6.2.4 or does it still exists?
Updated by Alexander Opitz over 9 years ago
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.