Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Articulate Error: A route named 'articulate_metaweblog_1148' is already in the route collection. Route names must be unique. Parameter name: name #326

Open
biapar opened this issue Dec 3, 2019 · 4 comments
Labels

Comments

@biapar
Copy link

biapar commented Dec 3, 2019

Hi,
After some years of running, today I’ve this error : A route named 'articulate_metaweblog_1148' is already in the route collection. Route names must be unique.
Parameter name: name
Umbraco 7.7.6 and Articulate 3.0.1
All site is down.

Stack trace:

[ArgumentException: A route named 'articulate_metaweblog_1148' is already in the route collection. Route names must be unique. Parameter name: name] System.Web.Routing.RouteCollection.Add(String name, RouteBase item) +4254616 Articulate.ArticulateRoutes.MapMetaWeblogRoute(RouteCollection routes, String nodeRoutePath, IPublishedContent node) in C:\Users\Shannon\Documents_Projects\Articulate\Articulate.Project\src\Articulate\ArticulateRoutes.cs:208 Articulate.ArticulateRoutes.MapRoutes(RouteCollection routes, ContextualPublishedCache umbracoCache, UrlProvider umbracoUrlProvider) in C:\Users\Shannon\Documents_Projects\Articulate\Articulate.Project\src\Articulate\ArticulateRoutes.cs:67 Articulate.UmbracoEventHandler.ApplicationStarted(UmbracoApplicationBase umbracoApplication, ApplicationContext applicationContext) in C:\Users\Shannon\Documents_Projects\Articulate\Articulate.Project\src\Articulate\UmbracoEventHandler.cs:53 Umbraco.Core.ApplicationEventHandler.OnApplicationStarted(UmbracoApplicationBase umbracoApplication, ApplicationContext applicationContext) +50 Umbraco.Core.CoreBootManager.b__38_0(IApplicationEventHandler x) +379 Umbraco.Core.EnumerableExtensions.ForEach(IEnumerable1 items, Action1 action) +167 Umbraco.Core.CoreBootManager.Complete(Action1 afterComplete) +416 Umbraco.Web.WebBootManager.Complete(Action1 afterComplete) +177 Umbraco.Core.UmbracoApplicationBase.StartApplication(Object sender, EventArgs e) +381 [HttpException (0x80004005): A route named 'articulate_metaweblog_1148' is already in the route collection. Route names must be unique. Parameter name: name] System.Web.HttpApplicationFactory.EnsureAppStartCalledForIntegratedMode(HttpContext context, HttpApplication app) +520 System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +176 System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +165 System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +267 System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +341 [HttpException (0x80004005): A route named 'articulate_metaweblog_1148' is already in the route collection. Route names must be unique. Parameter name: name] System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +523 System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +107 System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +688

@biapar
Copy link
Author

biapar commented Dec 3, 2019

I cleaned the cache and ported the "blog" node under main site node because I don't want to assign an hostname to blog node.

@Shazwazza
Copy link
Owner

Do you have any steps to replicate the issue? Have you tried using the latest 3.x version?

@biapar
Copy link
Author

biapar commented Dec 5, 2019

The issue happened after republish the entire blog. The blog has a lot of article. The blog node was at the same level with the "home" content node. Any main nodes has "hostname". So I solved:

  • delete umbraco xml file anche cache files
  • I assigned an hostname to main content node
  • I assigned an hostname to blog node, but for customer rule, I moved it under "home" node.

MAIN ISSUE: I lost tags and categories but the articles have them into backoffice.

@biapar
Copy link
Author

biapar commented Jan 12, 2020

Update: this happened after the customer move blog node.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants