Hello,
Remembering the steps that lead to the error:
I cleaned the trash folder.
Well, restored from a database backup made before the trash cleaning (using the empty trash button).
The error gone.
So, there is something broken at the trash...
Regards. Andre Felipe
---
A Debian user never dies. Issues a last command:
shutdown -h now
Hello,
By selectively removing objects from trash, I isolated 2 articles that did not have main location for publishing. (these tries involved some database restore operations...)
One of them I edited and assigned a location and was able to delete and remove it.
The last object, despite being assigned one mail publish location, did not come to a consistent state.
If I removed it from trash, the cronjob workflow crashed.
So, as a workaround I restored db backup and assigned it an invisible draft folder location. It is still there, but invisible....
Now the cronjob can run without crash.
but the object is broken, inconsistent, and I do not know how to repair it in order to remove it.
How an object could become broken?
Why the system does not dectect it? (at the admin interface, the verify upgrade is ok)
Regards. Andre Felipe
---
A Debian user never dies. Issues a last command:
shutdown -h now
