can't edit object assigned to root node (2)

Next topic

Author	Message
Andrew Kelly	Tuesday 05 June 2007 7:29:25 am Hi all, I've just upgraded from 3.8.6 to 3.8.8 and suddenly I cannot edit the object at my root node (object ID 1, Node ID 2). It keeps chucking a fatal error with transaction ID in the browser, and the error logs tell me Error: error executing query: DELETE FROM eznode_assignment WHERE id='' ERROR: invalid input syntax for integer: "" I've tracked this to the purge function in kernel/classes/eznodeassignment.php (which incidentally is unchanged compared to the previous version). Anybody seen something like this before? Andy
Andrew Kelly	Tuesday 07 August 2007 6:08:47 am Still baffled by this one, folks, and looking for any help out there. There's an additional problem, very likely related. If I'm embedding an object and choose to select an existion object, I get an error if I try to "go upstream" of node 2. Basically this call: /layout/set/dialog/content/browse/1 returns an error, "The requested object is not available...." What is causing all this? Anybody? Andy
Kristof Coomans	Friday 10 August 2007 12:34:48 am Hello Andrew Looks like you have some serious troubles. Did you run all database update scripts? The issue didn't occur on 3.8.6, did it? independent eZ Publish developer and service provider \| http://blog.coomanskristof.be \| http://ezpedia.org
Andrew Kelly	Friday 10 August 2007 6:31:06 am Hi Kristof, long time no read ;-) You know, I can't really answer that question for you right now, not with any real accuracy anyway. I do know that I first encountered this error condition after the upgrade to 3.8.8. And I do know that this condtion did not exist immediately after the upgrade to 3.8.6. But I cannot say if the condition appeared immediately following the upgrade to 3.8.8 or if it was already present at that time. Editing the root node isn't something we really need to do much, you see. To more tightly localise when this might have first appeared, I'm going to have to play in some backups and check things out. Sadly, though, the disks I need are off-site in a vault and everybody who has access is currently away on vacation and will be for a while yet. (How's that for great planning at the boss-level ;-) ). My guts are telling me that the problem has something to do with a node-assignment record disappearing, or something of that nature. It's definitely in the db, at any rate. For what it's worth, I upgraded to 3.9.2 two days ago, and the condition persists. Out of curiosity, how the heck is node 1 maintained in the DB. I can't find a direct assignment in any table anywhere. The closest I can come is finding it listed (correctly) as parent node of several others. Andy
Andrew Kelly	Wednesday 19 September 2007 3:35:43 am Just a follow up, in case anybody ever bumps into this as well. I've been able to verify that the upgrade from 3.8.6 to 3.8.8 did not have any involvement. The "breakage" occurred prior to and independantely of the upgrade. It's impossible for me to reconstruct HOW it happened, but WHAT happened was pretty much what I had suspected. In table 'ezcontentobject_tree', the record for contentobject_id=1 had gone missing. A reconstruction of this record solved this, and several other related problems. Andy