Ok,

Unfortunately, I do not know how to set the answer back to unsolved.

However, the answer may still be found in one of the log files (in ~/App_Data/Logs).

Is there anything special in the log file at the time of publishing your renamed item?

Any suspicious logs created during upgrade ?

The database (the local connection string is pointing to) has a table umbracoRedirectUrl and that table is completely empty?

Ok,

Unfortunately, I do not know how to set the answer back to unsolved.

• no problem..just some free karma for you :-)

However, the answer may still be found in one of the log files (in ~/App_Data/Logs). Is there anything special in the log file at the time of publishing your renamed item?

• nothing in the logs

Any suspicious logs created during upgrade ?

• nope

The database (the local connection string is pointing to) has a table umbracoRedirectUrl and that table is completely empty?

Table is there. Just not getting populated

... thanks for the karma ;-)

The only valid reason I can think of right now why an umbracoRedirectUrl table would be empty after having renamed a published node, is when you delete the renamed node afterwards and then clear the recycle bin.

In your case, where it has not been added to the table in the first place, something else must be going on ... hopefully someone can help you further!

Do you happen to have any of these installed?

                "InfoCaster.Umbraco.UrlTracker",
                "SEOChecker",
                "Simple301",
                "Terabyte.Umbraco.Modules.PermanentRedirect",
                "CMUmbracoTools",
                "PWUrlRedirect"

We disable redirect tracking if these dlls are found to avoid rewrite conflicts and infinite redirects. See: https://github.com/umbraco/Umbraco-CMS/blob/5397f2c53acbdeb0805e1fe39fda938f571d295a/src/Umbraco.Web/Routing/RedirectTrackingEventHandler.cs#L43

That said, it should also show up as the being disabled in Umbraco if you have any of them installed.

I actually think I know what the issue is.

We have a shared db between developers. And my instance wasn't master at the moment.

Because here in the code from the link you posted i see this :

private void PageCacheRefresher_CacheUpdated(PageCacheRefresher sender, CacheRefresherEventArgs cacheRefresherEventArgs)
        {
            // only on master / single, not on slaves!
            if (IsSlaveServer) return;

            // simply getting OldRoutes will register it in the request cache,
            // so whatever we do with it, try/finally it to ensure it's cleared

            try
            {
                foreach (var oldRoute in OldRoutes)
                {
                    // assuming we cannot have 'CacheUpdated' for only part of the infos else we'd need
                    // to set a flag in 'Published' to indicate which entities have been refreshed ok
                    CreateRedirect(oldRoute.Key, oldRoute.Value.Item1, oldRoute.Value.Item2);
                }
            }
            finally
            {
                OldRoutes.Clear();
                RequestCache.ClearCacheItem(ContextKey3);
            }
        }

Dave

is working on a reply...