-
-
Notifications
You must be signed in to change notification settings - Fork 356
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Workspace problem: news image is not shown to regular editor in preview, only to admin #2016
Comments
thanks for creating the issue. IMO this is more a core issue than news as everything there is core. do you agree? |
thanks for your quick response. |
tt_content uses a dataprocessor, news uses extbase. what about just using extension builder, setting ab a minimalistic extension and retest. that would be awesome as well for later debugging in core without requiring the news ext |
I don't understand - why building an own extension? It's a regular news setup, which works perfectly, except this little issue in combination with workspaces |
the question is: is it a news issue or an extbase issue and to answer that a tiny simple MVP extension would make sense to test this. if it is a core issue, this is the wrong issue tracker |
OK understood. I built a simple MVP extension - the file relation works within the draft workspace for a non-admin editor. |
wanna share the ext? thanks a lot! |
sure: it's just a very simple extension - build with extensionbuilder in 2 minutes. |
If it helps, I checked the issue also with "mask" (repeating content - so its stored not directly in tt_content) - the issue does not appear there |
The issue also remains in news version 11.0.0 |
Current Behavior
As an draft-editor, who can create news items everything works fine, except the rendering of the news image (falMedia) in draft preview (list and detail view).
To an admin user the image is rendered.
By adding <f:debug>{newsItem}</f:debug>, I can see:
the falMedia node is empty for the regular editor - to the admin everything is fine (falMedia contains all informations)
The same behavior occures with related files (falRelatedFiles).
In LIVE workspace - there are no errors at all.
Expected behavior/output
There must be a difference between admins and editors, how the extension handles the rendering of attached references (falMedia. falRelatedFiles, .... ), which are not in LIVE workspace.
Environment
Possible Solution
When I manually change the values t3ver_state and t3ver_wsid from 1 to 0 in sys_file_reference, the images are rendered for the normal editor.
The text was updated successfully, but these errors were encountered: