RE: [xwiki-users] $xwiki.copyDocument, objects, and cache

-----Original Message----- From: THOMAS, BRIAN M (SBCSI) Sent: Wednesday, May 31, 2006 9:29 AM To: xwiki-users(a)objectweb.org Subject: RE: [xwiki-users] $xwiki.copyDocument, objects, and cache Thanks again, Ludovic, for a quick reply. I apologize for neglecting to give you the version; I'm using 0.9.840, and calling copyDocument from a Velocity script on a wiki page. And no, I'm not getting any error messages, either on the page or in the logs, with one exception: my attempts to delete the incorrectly-copied document evoked an error message, which I didn't interpret as having to do with the objects but complained of an inconsistency in item counts (e.g. expected 1, found 0) or something similar; sorry I don't have the message now. After flushing, however, the deletion succeeded. Your suspicions sound consistent with what I've seen here. There's an update to this: I edited the original document's page permissions to add "admin, programming" to the "levels" field of the corrupted rights object, which was for XWiki.XWikiAdminGroup, and the objects survived the flush. Apparently the bogus fieldname (or, more likely, the lack of the correct one) is in some way the culprit - such as causing the transaction to abort when an object with an incorrect schema was saved. Why the document and its content (an #includeForm directive) survived the aborted transaction is a mystery in that case. So, conjecturally, (apart from the incorrect DB data) the bug, if any, is that a) no error message ensued from an aborted transaction (I'm pretty sure, though not absolutely, that the logs were silent) and b) the cache was not cleared. I am adding an $xwiki.flushCache() call to the end of my copy script, at any rate, to be sure that I'm not fooled again by objects that aren't really there. At a minimum, the database dump needs to be fixed ASAP... brain[sic] ----------------------------------------------------------------------