TYPO3 Core

If a user changes the pagecontent in the Popup-Window via frontend-editing, the page ("the opener") should get a refresh signal, so the saved data gets visible right away.

It would be cool, if the page gets only refreshed, if data actually changed (saves server performance).

Hi,
I currently don't have any time to investigate this, but a patch would be very welcome to fix this a bit annoying issue.
Greets, Sebastian

Very annoying issue and still there in Typo3 4.0beta1 ...

Hi Sebastian,
Any news on this issue?
regards,
Martin

On save-and-close this JS code must be executed:

window.opener.location.reload(true);

For close a way has to be found, if any changes have occured since the opening of the window. But where to track? A save will re-load the form page.

added "window.opener.location.reload(true);" to file typo3/close.html which is called from alt_doc.php if you press the "close" or "save_and_close" button:

----- typo3/close.php -----
<script type="text/javascript">
/*<![CDATA[*/
self.close();
window.opener.location.reload(true);
/*]]>*/
</script>
-----

The reloading of the frontend page has to be done in close.html, to be sure that the database update has been finished!

Hi Martin,

Do you think, it would be a big problem if the frontend page gets reloaded after closing the edit window even if there was no change since opening the edit window?
In my opinion this little performance penalty is much less annoying than no reload at all after changing the content in FEedit.

update:
"self.close()" has to be called before "window.opener.location.reload(true)" else there might be problems like nonclosing edit windows in backend.

(see: close-1.html)

Now i have created a bugfix for this problem. (close-1.html)
(i think a unified diff won't be necessary in this case , but i will create one if needed)
Could you please have a look at it. It would be very nice if this "gremlin" could be fixed in Typo3 v4.0

thanks in advance

fixed in CVS.