Ismail:

Not tried but at a guess something like:

Page page = HttpContext.Current.Handler as Page;

if (page != null)
{
     Page.Controls.Header.Add(new LiteralControl("javascript in here"));
}

Though I'm not sure at what point in the page lifecycle the event handler is called.

Let me know how you get on.

This would be an interesting one.

If you have problems then there is an event that is raised everytime a page in the GUI is rendered.

You could set a flag on the event and tap into that maybe.

Hi Ismail,

I would propose something like:

    public class OnSaveEventSample : ApplicationBase
    {
        public OnSaveEventSample() {
            Document.AfterSave += new Document.SaveEventHandler(Document_AfterSave);
        }

        void Document_AfterSave(Document sender, global::umbraco.cms.businesslogic.SaveEventArgs e)
        {
            Page.ClientScript.RegisterClientScriptBlock(this.GetType(), "popup", "<script>\ntop.openModal(yourpopup.aspx?nodeid="+ sender.Id +", 'OnSave Pop Up', 540, 620);</script>");
        }
    }

- Morten

Actually looks as though you should just be able to do:

Page page = HttpContext.Current.Handler as BasePage;

page.ClientTools.OpenModalWindow(.....)

Ups .. and I wrote AfterSave.

Try it out with Document.BeforeSave += new Document.SaveEventHandler(Document_BeforeSave); instead

Looking at how the Save-method is setup it would appear that you have access to the same properties as with AfterSave:

        public override void Save()
        {
            SaveEventArgs e = new SaveEventArgs();
            FireBeforeSave(e);

            if (!e.Cancel) {
                base.Save();
                Index(true);
                FireAfterSave(e);
            }
        }

- Morten

Guys,

Many thanks will try both ways when i get a moment.

Regards

Ismail

Hello,

I have this working however when the pop up comes up the page continues to save take it i would before showing popup cancel the event and after doing by bit re fire the event though not sure how i would stop it from looping?

Regards

Ismail

I guess you'd need to set a session variable.

Check if session["cancelPublish"] exists if not then cancel the event and set it.

If it does exist then null it and continue with the event.

That way, when your modal re-raises the event it should work.

HI Ismail,

The properties are saved anyway when you hit the save button. So why not take a different approach. Why not create a custom datatypestore it on the generic properties tab so normal users wouldn't see it  and let that capture the data whenm submitting the form?

Cheers,

Richard

is working on a reply...