Bug #49520
closed
fileadmin&sslproxy
Added by Loon Buster over 11 years ago. Updated over 10 years ago.
0%
Description
[1] fileadmin
if file = 0 byte => error
[2] ssl-proxy only for t3be
=> doesn't work!
https://ssl.tld/sub.domain.tld/typo3/ [okay]
sub.domain.tld/ [switch] sub.domain.tld/sub.domain.tld/index.php?id=[linkedPage@firstDomainInTree]
.loon
Updated by Chris topher over 11 years ago
- Status changed from New to Needs Feedback
Please tell us with more words, what problem you have. Complete sentences are prefered.
- Are you reporting two different problems here?
- Do you mean you put a file in fileadmin, which has a size of 0 bytes and then you get an error? Where and what error?!
- What do you mean with "doesn't work" in the second point? Does that somehow have to do with the 0 byte file or is it something separate?
Apart from that, the solution for that kind of problem always is 42. ;-)
Updated by Loon Buster over 11 years ago
~believe me, complete sentences from me makes less sence ;D
yes; two different problems:
[1] exactly. error is:
Uncaught TYPO3 Exception
#1314354065: Could not find row with uid "2" in table sys_file_storage (More information)
RuntimeException thrown in file
(..)/typo3/sysext/core/Classes/Resource/AbstractRepository.php in line 194.
[2] separate. i tried all opportunities. i think; the problem is that my hoster didn't transport a ssl-proxy-ip to php.. only a domain. it would be better i can set also $_SERVER variables at the install tool instead a ip.
.loon
Updated by Alexander Opitz over 11 years ago
For [1], please tell us, what you do and where this error happens.
For [2], please open another issue, as one problem per issue is enough.
Updated by Loon Buster over 11 years ago
if i create a file in the fileadmin or upload a zero-file.
..and under this directory the error comes.
.loon
Updated by Alexander Opitz over 11 years ago
if i create a file in the fileadmin or upload a zero-file.
Ok done. Created a file in /fileadmin
..and under this directory the error comes.
I don't understand. I viewed /fileadmin again, but nothing happened.
Updated by Loon Buster about 11 years ago
really? then must be everything okay.. :)
..not!
.loon
Updated by Chris topher about 11 years ago
Not reproducable; like for Alexander this works fine for me.
Updated by Loon Buster about 11 years ago
zero files = error:
#1314354065: Could not find row with uid "2" in table sys_file_storage (More information)
RuntimeException thrown in file
[..]/typo3/sysext/core/Classes/Resource/AbstractRepository.php in line 194.
Updated by Alexander Opitz about 11 years ago
It would be really nice to get complete sentences, which describe what are you try to do. Which TYPO3 Version are you using, is it a complete fresh installation or an updated one.
Updated by Mathias Bolt Lesniak about 11 years ago
Hi!
I have also had this error, and it was caused by sys_file_storage having a row (uid=2) with the deleted field set to "1". Removing the deleted flag solved the issue.
I had created a File storage within another File storage, and noticed my mistake. That's why I originally deleted it. It seems there's some record left that references the File storage, or the deleted flag is not heeded in an earlier query.
- Mathias
Updated by Alexander Opitz about 11 years ago
- Is Regression set to No
So this issue is then same as #51562 ?
Updated by Mathias Bolt Lesniak about 11 years ago
Updated by Alexander Opitz almost 11 years ago
Hi,
you wrote "I had created a File storage within another File storage, and noticed my mistake.", my question is, how did you do that?
I have my default storage for fileadmin and I created another one for fileadmin/user_upload ... afterwards I deleted this storage. And I hadn't any problem.
So maybe I did the testing wrong or it is the version I tried (TYPO3 CMS 6.1.7).
Can you test this with latest TYPO3? And if it crashs, can you write the an "Click-by-Click" instruction for me? :-)
Updated by Alexander Opitz over 10 years ago
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this ticket.
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.