Bug #30215
No import or uplaod possible
| Status: | Resolved | Start date: | 2011-09-23 | ||
|---|---|---|---|---|---|
| Priority: | Should have | Due date: | |||
| Assignee: | - | % Done: | 90% |
||
| Category: | - | ||||
| Target version: | YAG 1.3.0 | ||||
| Votes: | 0 |
Description
Hello,
I've installed yag on a new website (TYPO3 4.5.5) and if I try to import/upload images with any of the three methods (multiupload, zipupload, DirectoryOnServer) I get follwoing errors:
multiupload: after selecting the images the upload boxes appears and all of them throw error 500
zipupload: after uploading the zipfile the server throw a blank page
directory on server: blank page after submit
I've also tried http://forge.typo3.org/issues/29161 but there is no configured compression (0).
-The only thing I have seen is that Register Globals is On.
-PHP Safe Mode is off
-No functions disabled
-Memory limit 128MB
-Execution time 30 sec
-alle benötigten ordner sind writeable bzw. wurden per fileadmin angelegt
Are there any possibilities to display detailed errors. There are no TYPO3 log entries.
Maybe anyone can provide some tipps?
thx in advance,
jousch
History
Updated by Josef Florian Glatz over 1 year ago
NOTE: Flashuploader within the TYPO3 Filelist works correctly.
Updated by Josef Florian Glatz over 1 year ago
After enabling some errormessages I get this error after adding images from fileadmin:
Fatal error: Call to undefined function exif_read_data() in /srv/www/htdocs/domain.com/www/typo3conf/ext/yag/Classes/Domain/Import/MetaData/ExifParser.php on line 43
Updated by Michael Knoll over 1 year ago
OK - seems like your server's PHP is compiled without EXIF support. You can either fix this by installing the corresponding packages for PHP (you have to refer to your package system's documentation on how to do that), or you can fix this by disabling exif parsing in
Classes/Domain/Import/MetaData/ExifParser.php
by commenting out the following line:
public static function parseExifData($filePath) {
$exifArray = array();
# $exifArray = exif_read_data($filePath);
return $exifArray;
}
We will hopefully fix this in a following version by checking whether the method exists or not.
Updated by Josef Florian Glatz over 1 year ago
Thank you for your help. I havn't seen a PHP 5.3 without exif before. I miss my dedicated typo3host, where none of such stupid errors occurs.....
THX
Updated by Josef Florian Glatz over 1 year ago
Import after activating the exif module:
Directory import succesfull! Items were added to your album. PHP Warning PHP Warning: simplexml_load_string(): Entity: line 1: parser error : Start tag expected, '<' not found in /srv/www/htdocs/domain.com/www/typo3conf/ext/yag/Classes/Domain/Import/MetaData/XmpParser.php line 50 PHP Warning PHP Warning: simplexml_load_string(): ���� in /srv/www/htdocs/domain.com/www/typo3conf/ext/yag/Classes/Domain/Import/MetaData/XmpParser.php line 50 PHP Warning PHP Warning: simplexml_load_string(): ^ in /srv/www/htdocs/domain.com/www/typo3conf/ext/yag/Classes/Domain/Import/MetaData/XmpParser.php line 50 PHP Warning PHP Warning: simplexml_load_string(): Entity: line 1: parser error : Start tag expected, '<' not found in /srv/www/htdocs/domain.com/www/typo3conf/ext/yag/Classes/Domain/Import/MetaData/XmpParser.php line 50 PHP Warning PHP Warning: simplexml_load_string(): ���� in /srv/www/htdocs/domain.com/www/typo3conf/ext/yag/Classes/Domain/Import/MetaData/XmpParser.php line 50
Fehlt hier auch noch ein Modul? Konnte über Google hier auch nichts weiter passendes/aussagekräftiges in Verbindung mit dem Problem erörtern.
Liegt da evtl. noch etwas an der PHP-Konfig falsch?
Updated by Michael Knoll over 1 year ago
- Status changed from New to Accepted
- Target version set to YAG 1.3.0
We will check all dependencies for importing meta data and catch errors, if functionality is missing. Furthermore, there will be a TS switch to turn off all metadata processing and we will check that it works.
Updated by Michael Knoll over 1 year ago
- Status changed from Accepted to Needs Feedback
- % Done changed from 0 to 90
You can now disable meta data parsing completely via TS if you want. Furthermore, we have checks for external libraries. Bug seems to be caused by wrong metadata. We worked a lot of this, please try again!
Updated by Daniel Lienert over 1 year ago
- Status changed from Needs Feedback to Resolved