Adding multiple Articulate root nodes crashes my site...
Hi,
I was under the impression that multiple Articulate root nodes worked fine. However, I added 2 root nodes to my site, and when I restarted the app pool I get this error:
A route named 'articulate_search_656226678' is already in the route collection. Route names must be unique.
Removing the second root node fixes the problem.
Am I trying to do something that isn't allowed, or is there a bug that's causing this error?
In my test project I have 3 articulate roots so not sure how you've set your site up to get this error. If you can create an issue at the link above with full details on how to replicate I'll have a look.
I have added a new issue for this (#50). Having created a new blog node under my home node, I can no longer get into my back office or get the website to work. I get
"The route URL separator character '/' cannot appear consecutively. It must be separated by either a parameter or a literal value"
I am using Umbraco 7.2 and Articulate 1.05, which I installed in teh back office.
Sadly, I have not backed up the database for two weeks (my bad) and have no wlost a lot of work unless someone can tell me how to remove the offending blog nodes from the database or some other cure. I would be grateful for any help!
As mentioned in my replies there, the more details the better. It's only now after reading this post do i actually know what the title of that bug report means.
You can't just go deleting rows from cmsDocument, a node is stored in all sorts of tables.
Try just removing the articulate DLLs from your /bin and delete your App_Config/umbraco.config file too and see what happens.
Adding multiple Articulate root nodes crashes my site...
Hi,
I was under the impression that multiple Articulate root nodes worked fine. However, I added 2 root nodes to my site, and when I restarted the app pool I get this error:
A route named 'articulate_search_656226678' is already in the route collection. Route names must be unique.
Removing the second root node fixes the problem.
Am I trying to do something that isn't allowed, or is there a bug that's causing this error?
Thanks,
Maff
That would be a bug, can you please log an issue here: https://github.com/Shandem/articulate/issues
In my test project I have 3 articulate roots so not sure how you've set your site up to get this error. If you can create an issue at the link above with full details on how to replicate I'll have a look.
Doh! never mind, i can replicate now. I'll create the issue and log the bug.
https://github.com/Shandem/Articulate/issues/36
Great - thanks Shannon.
Is there a work-around for this that I can use in the mean time?
Nope sorry, you'll have to either get the articulate source with the issue fixed or wait until next release (couple weeks)
or assign hostnames to your other articulate roots
Cool thanks Shannon - I'll try the hostnames route and see if that fixes it in the meantime.
I have added a new issue for this (#50). Having created a new blog node under my home node, I can no longer get into my back office or get the website to work. I get
"The route URL separator character '/' cannot appear consecutively. It must be separated by either a parameter or a literal value"
I am using Umbraco 7.2 and Articulate 1.05, which I installed in teh back office.
Sadly, I have not backed up the database for two weeks (my bad) and have no wlost a lot of work unless someone can tell me how to remove the offending blog nodes from the database or some other cure. I would be grateful for any help!
The issue mentioned is here:
https://github.com/Shazwazza/Articulate/issues/50
As mentioned in my replies there, the more details the better. It's only now after reading this post do i actually know what the title of that bug report means.
You can't just go deleting rows from cmsDocument, a node is stored in all sorts of tables.
Try just removing the articulate DLLs from your /bin and delete your App_Config/umbraco.config file too and see what happens.
I am sorry, I was under the impression I hjad given the fullest details in my bug report. I am replying there.
is working on a reply...