No effective write access to major asset

We have LDAP backend users who are using simple edit, and need to delete assets. There is a trigger set up for this, which works fine. But when I look at the logs, I see the following:

    [2008-10-29 16:02:25][19909:CN=Karen Tempchin [ktempchin],OU=Staff Over the Quota Limit,OU=Staff,DC=puc,DC=edu:Karen Tempchin [ktempchin]][512:mysource warning][R] (/core/include/asset_manager.inc:5322) - Could not delete notice link #66094 - no effective write access to major asset ("Future Linking for "Choral Evensong" [#35479]" #35480) [SYS0319]


It looks like the future linking that gets added on asset create is not getting deleted, because the user doesn't have that permission. Is this cron asset just going to be orphaned when I empty the trash?

The "Future Lineage" cron asset retains the ID of the created asset and will be removed when it comes time to run as the asset could not be found.

The job will then be stored in the Trash. Alternatively, this job can be safely deleted from the Cron Manager before it runs.

[quote]The "Future Lineage" cron asset retains the ID of the created asset and will be removed when it comes time to run as the asset could not be found.
The job will then be stored in the Trash. Alternatively, this job can be safely deleted from the Cron Manager before it runs.[/quote]



Thanks Mark, good to know!