Package creates new/duplicate notification type in "Notifications" dialog
Hi,
I'm seeing this issue with both 4.7.1.1 and 4.7.1 (latest tested compatable version) of Umbraco. After installing the Media Protect package the notifications dialog displays two "Public access" check boxes:
The umbraco client is finding the iAction within the "MediaProtect.Actions.MediaProtectAction" namespace. I've tested this iwth a clean install of 4.7.1 and 4.7.1.1 (installed umbraco -> installed MediaProtect).
Is there a fix for this? I'd prefer not to create a seperate umbraco fork to resolve this issue because I'd need to apply the fix with each Umbraco release.
This was the case in previous versions also. This is because I left the notifications option into the action. Doesn't work anyway since it's not content. I've created a hotfix for you. You can find it here http://hotfix.soetemansoftware.nl/MediaProtect/ .Copy assemblies to your bin folder then it should work.
Package creates new/duplicate notification type in "Notifications" dialog
Hi,
I'm seeing this issue with both 4.7.1.1 and 4.7.1 (latest tested compatable version) of Umbraco. After installing the Media Protect package the notifications dialog displays two "Public access" check boxes:
The umbraco client is finding the iAction within the "MediaProtect.Actions.MediaProtectAction" namespace. I've tested this iwth a clean install of 4.7.1 and 4.7.1.1 (installed umbraco -> installed MediaProtect).
Is there a fix for this? I'd prefer not to create a seperate umbraco fork to resolve this issue because I'd need to apply the fix with each Umbraco release.
Thanks
Hi james,
This was the case in previous versions also. This is because I left the notifications option into the action. Doesn't work anyway since it's not content. I've created a hotfix for you. You can find it here http://hotfix.soetemansoftware.nl/MediaProtect/ .Copy assemblies to your bin folder then it should work.
Please let me know if this solved your issue.
Thanks,
Richard
Hi Richard,
Thanks for the quick reply, the hot fix resolved the issue.
Regards,
James
is working on a reply...