In types.cfc setLock()
uses bAfterSave="false"
when it calls setData()
so that shouldn’t be it…
We might need some more info about your environment / project;
- Does this happen on versioned or non-versioned objects, or both?
- Does it happen on unmodified core content types or custom content types, or both?
- Does it happen for all content types in the system or just some?
- How have you confirmed that
afterSave
is running when “Edit” is clicked? Have you put logging inside afterSave()
?
- Are you calling
setData()
from inside afterSave()
? If so are you including bAfterSave="false"
?
I’ve done the following test on a custom content type that extends types
by adding a basic afterSave
handler;
<cffunction name="afterSave">
<cflog file="bug-aftersave" text="inside afterSave">
<cfreturn super.afterSave(argumentCollection=arguments)>
</cffunction>
With this code, there is no log entry written when clicking “Edit” on the objectadmin grid, and after I click “Complete” to save the object there is a single entry in the log. The same thing happens when I click “Edit” from the object overview dialog.
Do you have any code you can share or a .cfc that can reproduce the issue?