Bug #13572
closedpreview js is loaded in live workspace frontend preview - causes js error
0%
Description
When you're in live workspace and press the preview icon of a page the frontend contains javascript of the preview.html of workspace extension. This javascript causes an error because of the document.domain setting.
Solution would be to make sure that these code is not loaded in frontend preview as soon as the user is in live workspace
Files
Updated by Tolleiv Nietsch over 13 years ago
Updated by Tolleiv Nietsch over 13 years ago
- Status changed from Accepted to Under Review
Updated by Sonja Schubert over 13 years ago
Patch works very well for me. +1 by reading and testing
Updated by Anonymous over 13 years ago
Hi,
I tested it and it works in the frontend if I'm not in the workspace in the backend.
When I'm in the workspace in the backend, it breaks again.
Is it really usefull to have a "echo" there? Wouldn't it be better to have some kind of wrapper? I didn't figure out where it has to be put to work properly, at the end of the body doesn't seam to work. Can someone check where the javascript has to be to work properly?
Greets
Tizian
Updated by Anonymous over 13 years ago
Maybe there should be checked if the frontend mode is the workspace frontend preview, is this possible?
Currently I fixed it with this:
if ($pObj->fePreview != 2 || $pObj->whichWorkspace() === 0 || !t3lib_div::_GP('tx_workspaces_web_workspacesworkspaces')) { return; }
This may be the solution but I think there is a possibility to know in which frontend mode we are and it should probably be checked with this an not with this "ugly" fix.
Updated by Tolleiv Nietsch over 13 years ago
nope t3lib_div::_GP('tx_workspaces_web_workspacesworkspaces') is always true in that context ;) - atm. we can't distinguish between standalone or "within preview window"
the "echo" is replaced in #13446 - please see https://review.typo3.org/#change,1058 for the latest patch update
Updated by Oliver Hader over 13 years ago
- Target version changed from 4.5.3 to 4.5.3
Updated by Oliver Hader over 13 years ago
- Target version changed from 4.5.3 to 4.5.3
Updated by Tolleiv Nietsch over 13 years ago
- Target version changed from 4.5.3 to 4.5.4
- TYPO3 Version set to 4.5
Updated by Tolleiv Nietsch almost 13 years ago
- Status changed from Under Review to Needs Feedback
This is still pending right?
Updated by Michael Stucki almost 11 years ago
- Category changed from Bugs to Workspaces
Updated by Michael Stucki almost 11 years ago
- Project changed from 624 to TYPO3 Core
- Category changed from Workspaces to Workspaces
- Target version deleted (
4.5.4)
Updated by Alexander Opitz over 10 years ago
- Is Regression set to No
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.1.7)?
Updated by Alexander Opitz over 10 years ago
- Status changed from Needs Feedback to Closed
- Assignee deleted (
Tolleiv Nietsch)
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.