I have implemented a Sitecore saveUI processor for moving news items to a specific location inside a year/month hierarchical structure. It does the job well, except for the fact that when used inside the Page Editor (navigating to an item's page and then trying to save, and implicitly move, the item) I am redirected to our 404 page, since Sitecore expects the original item's url to still be valid after the operation.
Is there any way to tell Sitecore that the item has been moved? I'm thinking at some property in SaveArgs, but any solution would do, as long as it's somewhat maintainable (for example, I'd prefer a server-side solution, not a client-side JavaScript-based one, if possible).
相关问题
- How to pass “[Sitecore Mobile SDK] Data from the i
- How can I remove duplicated page events in Sitecor
- Spoof an IP address to test GEOIP lookups with Sit
- How to get a Multilist with Search field to not di
- Page.Header.Controls.Add(control) is adding contro
相关文章
- Sitecore set/change default language from 'en&
- Sitecore OMS - achieving a goal on a form submissi
- Get number of components in placeholder, Sitecore
- Sitecore text search in PDF or Word documents
- sending data from one sublayout to another in site
- The model item passed into the dictionary is of ty
- How to implement Solr into Sitecore
- Sitecore enables accessing child node around paren
Off the top of my head, make sure your processor the last one in the pipeline and add the following code to the end of the process method:
Have you tried using the Sitecore Newsmover Module? This works seamlessly and could be the way to go instead of creating custom movers. We have used this plenty of times and it does seem to work well in all conditions.
Sample config for this: