XPages Tip: Edit an XPage that won’t open normally in Domino Designer

If playing around with the source of an XPage or Custom Control messes it up so badly that you can’t even edit it anymore, here’s a trick to be able to fix it.

See, I have this, um, friend — yeah, that’s it — and <cough>he</cough> really messed up an XPage by moving things around in the source to try to shove event handlers in places they weren’t meant to be. He told me that it messed up his custom controls so badly that they wouldn’t even open. A tab for the XSP Editor would start to display in DDE, but the control wouldn’t even open — the system would hang until it crashed.

Who (else?) would do something like that?

Fortunately, he told me that he found a way to fix it.

If you mess something up so badly that the XSP Editor can’t even render it without crashing, try opening it with a different editor.

Open the database in the Package Explorer view, locate the element and right-click on it, then select Open With > (XML Editor or Text Editor)


My friend was able to use this to remove the offending tags and restore the controls to a point where they could be edited in DDE.

Thank you for listening. My friend feels better now.


9 responses to “XPages Tip: Edit an XPage that won’t open normally in Domino Designer”

  1. Tim Tripcony (@timtripcony) says :

    Tell your friend not to be embarrassed. A couple years ago I mangled an XSP so badly even the XML editor wouldn’t open it… I had to fix it in the text editor (“I’m too close for missiles, switching to guns”).

  2. Chris Toohey (@christoohey) says :

    I thought you said you wouldn’t say anything about this…

  3. John Jardin (@John_Ukuvuma) says :

    Good tip Brad. This hasn’t happened to me as yet, but very good to know.

  4. V. Watson (@cool_v) says :

    Been there, done that, too!

  5. Henrik says :

    I have a similar problem, but I do not get any errors. My problem is that I just get a blank screen when trying to edit my xpage or custom controls. Even if I create a new database and a new xpage it is still just a blank screen that displays.

    It is like the xsp editor refuses to render properly.

    Any thoughts of what it could be?

    • Brad Balassaitis says :

      It’s hard to know what may have caused an issue. To goal is just to try to restore it. I’d try with several different editors. If not, you may just need to cut bait and restore from a backup. Ideally, if you’re using source control you can either revert to a previous version or at least get the source code of the page and re-apply it. At times, I’ve seen changing the page/custom control design element name allow it to rebuild properly.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: