Check the URL I've given, the sidebar widget photo albums and files both show instances of COM_EASYSOCIAL_GUEST_NAME
I'll explain what caused this below. What do you think the best fix is? I guess when the owner is changed, the new owner should inherit the core albums of the event? Although that's not the whole issue because there's a story post album here which also ended up with the COM_EASYSOCIAL_GUEST_NAME problem... maybe it should show as a non-hyperlinked 'Past Member' or something like that if the user no longer exists?!?!?
In this case, is it possible for you to help me by reassigning the 3 photo albums and the 1 uploaded file to the new event owner.. or would that cause possible more issues?
Here's how it happened...
1) I created an account for a user and create an event on their behalf
2) Then they decided to create their own account
3) I used the 'Change Owner' back-end option on EasySocial Events to give their new account ownership of the event
4) I then deleted the account I'd originally created to add the event in the first place.
5) That's what caused the issue here.
I'll explain what caused this below. What do you think the best fix is? I guess when the owner is changed, the new owner should inherit the core albums of the event? Although that's not the whole issue because there's a story post album here which also ended up with the COM_EASYSOCIAL_GUEST_NAME problem... maybe it should show as a non-hyperlinked 'Past Member' or something like that if the user no longer exists?!?!?
In this case, is it possible for you to help me by reassigning the 3 photo albums and the 1 uploaded file to the new event owner.. or would that cause possible more issues?
Here's how it happened...
1) I created an account for a user and create an event on their behalf
2) Then they decided to create their own account
3) I used the 'Change Owner' back-end option on EasySocial Events to give their new account ownership of the event
4) I then deleted the account I'd originally created to add the event in the first place.
5) That's what caused the issue here.