[BUGFIX] Prevent error when be:uri.editRecord is used in preview template #549
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Without the request on the rendering context, the uri.editRecord and link.editRecord ViewHelpers of the backend module are unable to automatically generate a returnUrl.
In the case of uri.editRecord we get an exception in the page module, and with the link.editRecord we'll end up on a blank page, when trying to use the close button to return to the previous page.
Not sure if there is a better way to get the TYPO3_REQUEST than through $GLOBALS. Maybe injection?
Also not sure if that perhaps is more of a TYPO3 core bug.
Anyway, I encountered this, because I like to add direct links to nested Content Elements if present right in the Page Module.
An example preview template taken from an Accordion Element:
If it wasn't the uri-ViewHelper but the link one instead, I'd probably never have noticed this error.