Bug #46090
closed
Contentobject data Image/Link broken or missing
Added by Martin Muzatko over 11 years ago.
Updated almost 11 years ago.
Description
On update to 6.0.3, the contentobject data did not return any expected values ($this->cObj->data;)
The same issue can be found on stackoverflow -> http://stackoverflow.com/questions/15250351/missing-image-in-typo3-this-contentobj-in-6-0-3
$this->contentObj = $this->configurationManager->getContentObject();
$data = $this->contentObj->data;
print_r($data);
This will return a tt_content - object including image => /path/to/image. Everything fine.
[bodytext] => Lorem ipsum dolor
[image] => ../../fileadmin/user_upload/images/businessman.jpg
Today changing source to TYPO3 6.0.3 everything the same but the image is just a "1".
[bodytext] => Lorem ipsum dolor
[image] => 1
- Project changed from 2559 to 534
- Category deleted (
Fluid)
- Target version deleted (
Fluid 6.0)
- Subject changed from Data Image/Link broken or missing to Contentobject data Image/Link broken or missing
- Priority changed from Must have to Should have
- Status changed from New to Needs Feedback
You mean you enabled the normal image field for a plugin content object?
The data array is comming direct from core and was not touched by extbase.
IMHO this should be the number of attached images because the image
field is a reference record to the file record since 6.0.
- Project changed from 534 to TYPO3 Core
Some more details are needed:
- did you start the site with 6.0 did you updated from a 4.x?
- if update, did you run the wizard to transform the images to file references
- changes in tca configuration?
I noticed this problem also. Started the site with a 6.0 installation - no update from a 4.x. Also no changes in the TCA config. I just want to render a new content element (own ctype) with fluid - using the standard tt_content image field. With 6.0.2 [image] contained the url, after an update to 6.0.3 it contains "1". Actually this is the amount of images that were selected in the content element.
I searched for the change that introduced the new behaviour and found it: http://forge.typo3.org/issues/45415 - if I use typo3/sysext/core/Classes/Resource/Service/FrontendContentAdapterService.php from 6.0.2 everything works like before. Don't know if this changed behaviour is intended or just a side effect that can be fixed.
Do you get you right, that you are using a custom content element, meaning a new CType in tt_content or another table?
Than it's the problem described here: #46067.
Thank you for the hint on #46067. That's exactly the problem in my case.
- TYPO3 Version set to 6.0
- Is Regression set to No
Hi,
is this issue solved with newer versions of TYPO3 CMS? Latest one is 6.1.5 at the moment.
- 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.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by