You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No exceptions should occur when accepting VersionAddedNotification via PowerShell in Sitecore.
Actual Behavior
NullReferenceException occurs when trying to accept VersionAddedNotification via PowerShell in Sitecore.
It happens for cloned items after creating a new numbered version for its master item.
Steps to Reproduce the Problem
Steps to reproduce:
Create a master item - /sitecore/content/Home/Sample Item
Debugging the source code, we detected the exception occurs in VersionAddedNotification.Accept method
when trying to invoke this.SendMessage - see attached pictures
1_VersionAddedNotification.Accept.jpg
2_VersionAddedNotification.SendMessage.jpg
3_ClientPage.jpg
The reason for the issue is HttpContext.Current is null.
It is reproduced not steadily - after several attempts, it could be successfully accepted.
But, each failed attempt adds a new version for the cloned item.
The text was updated successfully, but these errors were encountered:
This one should be fixed but I have a feeling it's a lost cause... I don't think the notification for Field approval is going to be so easy to handle. unless we start taking over some of the "Accept" code. in some of the notifications.
Expected Behavior
No exceptions should occur when accepting VersionAddedNotification via PowerShell in Sitecore.
Actual Behavior
NullReferenceException occurs when trying to accept VersionAddedNotification via PowerShell in Sitecore.
It happens for cloned items after creating a new numbered version for its master item.
Steps to Reproduce the Problem
Steps to reproduce:
Debugging the source code, we detected the exception occurs in VersionAddedNotification.Accept method
when trying to invoke this.SendMessage - see attached pictures
The reason for the issue is
HttpContext.Current
is null.It is reproduced not steadily - after several attempts, it could be successfully accepted.
But, each failed attempt adds a new version for the cloned item.
The text was updated successfully, but these errors were encountered: