Bug #17331
closed
TYPO3: 4.1.1
dam 1.0.100
dam_tweaks 0.0.0
dam_catedit 1.0.5
dam_index 1.0.100
dam_info 1.0.100
dam_downloads 1.1.0
dam_fileicons 0.0.0
This looks like it may not be a DAM issue. I've discovered that I also get this error when creating a, "mail form", but, not any other content element. Is it possible to change the category for this issue?
"Is it possible to change the category for this issue?"
Can you please give us more details (examples) what you want change and how?
Thnx.
"Is it possible to change the category for this issue?"
I should have been more precise. Since this error also occurs with the mail form content element I was wondering how the category for this mantis issue could be changed from tx_dam to TYPO3 Core (or whatever is most appropriate).
Thanks,
Eric
Some more information on this problem.
When in the Media -> File: List view there are seven icons for each file. Some of these icons work while others do not.
Edit Record: works
View File: works
Edit File: not click-able
Display Information: works
Rename: Service Temporarily Unavailable
Replace File: Service Temporarily Unavailable
Delete: Service Temporarily Unavailable
I also tried the batch edit operations; copy, move, and delete all generated Service Temporarily Unavailable errors.
I think I've tracked the problem down to the returnUrl parameter. If I remove it from the URL and reload the page that said, "Service Unavailable" the page loads properly. I've tried this for the new category and rename links.
The followign is the returnUrl parameter I removed from the rename URL.
&returnUrl=http%3A%2F%2Fpiap.com%2Ftypo3conf%2Fext%2Fdam%2Fmod_file%2Findex.php
The following is the returnUrl parameter I removed from the new category URL.
returnUrl=http%3A%2F%2Fpiap.com%2Ftypo3conf%2Fext%2Fdam_catedit%2Fmod1%2Findex.php&
Eric
Hum . . .
Since I'm not a core member . . .can someone 'unassign' me please?
Cheers,
Michiel
Double Encoding:
I think it has to do that the return url has double encoded characters, instead of HEX encoded: ie "%252F" instead of "%2F" for the / character.
I've lodged a new bug report 0009572.
Closed as duplicate of 9572
Also available in: Atom
PDF