All - I’m currently unable to save an xpage - originally I had several custom controls, and was bound to data from a separate database: adding a simple submit button with simple action behind it does not seem to do anything. I’m using the action=editdocument&documentId= URL parameters to open a document in edit mode, and the values are showing correctly: however when I edit them and click a submit button (with either save document, save data sources or currentDocument.save() in), the button depresses but nothing seems to be sent back to the server. I’ve now also tried a simple xpage with one edit box (bound to a field in a form the same database which populates correctly from the back-end document), and a submit button, but cannot get it to save a change back to the document.
I’m hopeful that it’s an early senior moment as my 40th approaches - but any hints would be welcome!
Quick Update
This appears to work on local but not on the server - the server was rebooted this morning but the save/submit still doesn’t seem to work.
There are a couple of things I’d suggest checking first of all. One is that the user you’re logged on with has access to create/edit documents (depending on process being performed) in the databases on the servers. Also worth checking maximum internet access on the Advanced tab of the ACL. Though it sounds like a server-level security issue.
Second thing is at design level. By default on the XPage the same page is used for next page after success and failure (on the XPage tab of the XPages’ properties). Changed failure to go to a different page. If it goes to this page, you can confirm that it’s failing, so add a Display Errors control, which may tell you that a specific field is failing.