Moving an Event doesn't quite work as expected .. redirect doesn't happen

Since there is no OOTB way to move an Event (and it isn't on the roadmap), we have endeavoured to code this up ourselves. It's pretty much working.. I can move an Event from one calendar to another...

The event is there in the Calendar I moved it to, and is available on the new URL. 

There's one problem; if I go to the old URL it doesn't redirect to the new one as I'd expect. That's in spite of there being a row in the te_UrlRedirects table which looks correct to me...

I can actually go to the old URL & the event still displays (with no redirect).. making it look like it's in the old group/calendar, even when it isn't!

When I delete the redirect from te_UrlRedirects, it doesn't make any difference.

If I do this with another content type, like a Wiki doc then I can see the browser redirect from the old URL to the new one. I'd assumed that was to do with the entry in te_UrlRedirects, but interestingly, it continues to redirect even when I delete that row from the database (and restart the site). It therefore feels like I'm missing a piece of the puzzle, and that piece might help solve why Event moving isn't working 100% as expected.

Any help would be appreciated.

Thanks!

Parents
  • Former Member
    0 Former Member

    The redirect code only runs if the original Url fails to find an valid calendar event at that Url.  So the problem lies in the code that still thinks the old Url is valid.  I have filed a bug to address the issue.  Note, there should be no security issue in being able to open a calendar event in a different group from where it exists, you still need access to the event to see it.  But this should be corrected so an event is only be viewable from the correct url in the correct group.  Once that is corrected, the redirect will begin to work.

    TE-17455

Reply
  • Former Member
    0 Former Member

    The redirect code only runs if the original Url fails to find an valid calendar event at that Url.  So the problem lies in the code that still thinks the old Url is valid.  I have filed a bug to address the issue.  Note, there should be no security issue in being able to open a calendar event in a different group from where it exists, you still need access to the event to see it.  But this should be corrected so an event is only be viewable from the correct url in the correct group.  Once that is corrected, the redirect will begin to work.

    TE-17455

Children