|
[
Permlink
| « Hide
]
Toni Birrer added a comment - 18/Oct/07 03:14 AM - edited
We have exactly this problem. Is there a workaround or hot fix available for this?
We also have this problem. It is really annopying.
The same error can occur when the {content-by-user} macro is used.
Could this problem affect versions prior to 2.6 as well?
We're using 2.5.6 and for some reason we aren't getting the notifications generated every day either... oddly enough now that I check, we also seem to be missing log files on the days that notifications aren't being generated?? That may just be a freakish coincidence though... at any rate, it means I can't check the logs for a similar event... David, this specific problem cannot occur in versions prior to 2.6. Drafts weren't content objects with permissions in 2.5.x, so they couldn't exhibit this failure.
Could you please raise a support case at https://support.atlassian.com Replicated, copied code from trunk, tested - AOK.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||