Merge branch 'bugfix/move-topic-url' into develop

There has been a long-standing bug in the OnTopic Editor where the URLs of topics in the tree view are broken after being moved. That's because while ExtJS moves the nodes within the tree, it doesn't make any updates to their `path` or `webPath` properties. As such, if they are clicked on, they will still go to their old location, thus yielding a 404 Not Found. This issue is compounded if the user is currently on the topic that was moved, or is a descendant of that topic. In that case, if the user performs an action such as save, it will return a 404 Not Found since it will attempt to post back to the original URL.

These issues are resolved by reloading the tree view after a topic is moved. And if the topic that was moved in the current topic or an ascendant, then the user will be redirected to the new URL, thus ensuring the form and its actions are refreshed.

In many cases, these never caused problems as the user would click to another page after performing a move. But for the scenarios where the above conditions were met, the behavior was unintuitive and frustrating.

Author: JeremyCaney

OnTopic.Editor.AspNetCore/Areas/Editor/Views/Shared/_TreeViewScript.cshtml

@@ -97,6 +97,20 @@
             url: "/OnTopic/Move",
             data: { topicId: node.attributes.id, targetTopicId: newParent.attributes.id, siblingId }
           })
+          .done(function() {
+
+            //If current or ascendent topic, redirect to new location since the current URL is no longer valid
+            if (currentTopic.startsWith(node.attributes.path)) {
+              location.href = location.href.replace(oldParent.attributes.webPath, newParent.attributes.webPath);
+            }
+
+            //Otherwise, refresh the tree to ensure the new webPaths are reflected
+            else {
+              currentPosition = currentTopic.indexOf(':', 5);
+              tree.getRootNode().reload();
+            }
+
+          });
 
         }
       }