|
Thursday 16 February 2006 8:22:12 am
I have similar problems. I have experienced your problem (random objects not getting published) but it disappeared after I tinkered for a while (I'm sorry to say I didn't record what I did). The problem that remains is that users that register show up directly in the content-object tree, bypassing approval. I have isolated the bug to the case where ezapprove is set to section Users. If "all sections" is set, the approval process runs normally. If I run the approval workflow it via the multiplexer, I get similar results: filtering by class or section makes the publishing process bypass approval, while deactivating filtering makes it work. I get only two error messages running the workflow-cronjob script manually with debug: Undefined index: no-cache-adviced in /home/helsekom/public_html/lib/ezi18n/classes/eztstranslator.php on line 64
and Warning(): User not found, returning anonymous
. I suspect something within ezapprove breaks during filtering. I will continue to investigate this problem, but am grasping at straws. I am unsure whether this problem is related to the one you, Marienborg, are experiencing. How do you filter in your workflow? I cannot answer your question about the collaboration table properly, but suspect that its contents are used for the "collaboration/view/summary" view under "My account".
Leif Arne Storset
|
