If I'm not mistaken you can just add node data jsExecutedAfterSaving = timeoutOrWthateverElse(); opener.document.location.reload(); to your dialog and the problem should be solved
HTH, Jan On Jun 21, 2011, at 3:18 PM, Ronald Ten Berge wrote: > > Hi, > > We have implemented a custom front-end for Magnolia using XML exports, and > these exports are being run using the observation module. > > If a user saves content using a dialog, the mgnlDialogReloadOpener() function > in /.resources/admin-js/dialogs/dialogs.js will be executed. But sometimes > this page reload is faster than our exporter. This means that the data is not > updated after the reload, or that the browser shows a broken XML file (not > completely exported). A solution to this problem would be adding a delay to > the mgnlDialogReloadOpener() function using setTimeout(), but we can't find a > way to override this function. > > We tried adding an admin-js folder to our module under mgnl-resources, but > this doesn't work. We could implement a SaveHandler, but then the content > would be exported twice and we would have the same problem with the broken > XML files. > > Does anybody know a solution? > > Kind regards, > > Ronald > > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- - Best regards, Jan Haderka, PhD. Magnolia International Ltd. http://www.magnolia-cms.com Magnolia CMS is a Red Herring Europe 100 winner: http://tinyurl.com/redherringE100 -------------------------------------- Magnolia® - Simple Open-Source Content Management ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
