As it is now, the "upload done" hook that fires after the replacement has occurred is not particularly useful as it only sends along the new guid. If, for instance, a user wants to hook in and perform a search/replace against additional tables, they don't have the original guid from which to work.
This simply passes the current guid along with the new guid. It also removes the ternary operator that was checking for the new guid, as the hook is already wrapped in an isset() conditional that should handle that already.
As it is now, the "upload done" hook that fires after the replacement has occurred is not particularly useful as it only sends along the new guid. If, for instance, a user wants to hook in and perform a search/replace against additional tables, they don't have the original guid from which to work.
This simply passes the current guid along with the new guid. It also removes the ternary operator that was checking for the new guid, as the hook is already wrapped in an
isset()conditional that should handle that already.