Bug #37318
No result image was created. ResultImagePath:
| Status: | Closed | Start date: | 2012-05-20 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | YAG 1.5.1 | |||
| Votes: | 3 (View) |
Description
Typo3 Error No result image was created. ResultImagePath:
in backend whenever I click on "Gallery" in the menu.
I migrated a fully working Typo3 4.5 LTS site including yag 1.4.5 + yag themepack jquery 0.5 to another directory within the same server.
First it did work. I decided to update the gallery to 1.5.0.
This is when I get the error everytime I try to click on "Gallery" in the backend.
I deleted the yag and yag themepack extension from the server including the database tables
tx_yag_domain_model_album
tx_yag_domain_model_gallery
tx_yag_domain_model_item
tx_yag_domain_model_itemmeta
tx_yag_domain_model_resolutionfilecache
tx_yag_domain_model_tag
tx_yag_item_tag_mmin order to try a clean new installation. But I get the same error after reinstalling.
Are there any other database tables or entries in tables affected by yag that I should delete before reinstallation ?
Kind regards
Related issues
| related to YAG - Yet Another Gallery - Bug #39466: Problem with result image creation in BE | Closed | 2012-08-02 |
History
Updated by Daniel Lienert about 1 year ago
- Status changed from New to Needs Feedback
Have you tried a look at the reporting tool section about YAG? Are all tests there green?
My first guess would be, the source file directory, the directory for the resolution file images or the typo3_temp directory are not writable.
Updated by Daniel about 1 year ago
- File Unbenannt.png added
The post_max_size is too small, but that couldn´t be the problem, could it ?
Before reinstallation I deleted the typo3temp/yag and the fileadmin/yag folder. Maybe there are some old references in the database other then
the tables I posted above ?
Updated by Daniel Lienert about 1 year ago
Nope the error should not be caused by the post_max_size.
Try to hit the update button in the plugin configuration in the extension manager again.
This error is thrown while yag wants to receive the generated image from the TYPO3 image generation process - maybe this process fails -> check the image generation in the install tool.
Updated by Daniel about 1 year ago
- File jesus.PNG added
- File currentimg.PNG added
Ok I hit the update button but nothing change.
The problem really seems to be the image generation process.
I tested the read/write functionality for png´s and the test failed (see attached image)
I also attached the current configuration of the image processing.
But I´m wondering why it did work in the first place and refuses to work now.
On my second TYPO3 Installation, same server, the image processing test fail the same way but YAG does work.
So this cant be the issue.
Updated by Daniel about 1 year ago
Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1300205628: No result image was created. ResultImagePath: /kunden/homepages/25/htdocs/dgt3/ | Exception thrown in file /homepages/25/htdocs/dgt3/typo3conf/ext/yag/Classes/Domain/ImageProcessing/Typo3Processor.php in line 77
Updated by Rafal Brzeski 12 months ago
I had the same problem after moved folders with images to another directory,
when I moved back folders to first destination everything started to work again,
maybe this help :)
Updated by Sean Donovan 11 months ago
There is a duplicate on this bug - http://forge.typo3.org/issues/35934
A quick solution is to return/upload the JPEG file that was moved/deleted. The original problem is that I had "`" in the filename which YAG gagged on. If you want to get rid of the JPEG, delete it via YAG first, then via FTP.
Updated by Michael Knoll 9 months ago
- Status changed from Needs Feedback to Closed
- Target version set to YAG 1.5.1
Fixed in version 1.5.1. See http://forge.typo3.org/issues/35934 for what had been changed.