How does "Link to Document" turn into "#" on every page?
I've seen this issue posted before where the Link to Document field becomes a # and the solution is to republish the sites. Does anyone know why this happens? Republishing did fix the issue, but I'm trying to find a cause. I find it hard to believe it all hinges on the umbraco.config, I have thoroughly added garbage characters and deleted pieces but it still works. Another question is where are these links stored?
Any insight on where or how the links are stored and what could wipe out all of them simultaneously is welcome. It could very well be a hardware problem, I'm just trying to figure out how to narrow the possibilities of causes.
I'm guessing that you're using Umbraco 4.7? Not sure what is causing the issue except that it's a bug that seems to have been fixed in releases from v4.8+ and forward since I have not seen the error since.
Sometimes I've seen it happen if a illegal characters has been added as a document type alias for instance.
If I'm right in my assumption about, which Umbraco version you're using is it then perhaps possible to do an upgrade to a newer version?
Yes, you are correct in the assumption, my apologies for forgetting to add it. And thank you for the welcome!
Upgrading is in the works, hopefully that does fix the bug. Do you know what the illegal characters are? Nothing was changed, it just happened one day, on every single page. I heard the Umbraco.config in app_data could be the culprit, but I added every possible illegal character I could think of and had no affect on the website.
At this point I'm trying to satisfy my curiousity of how Umbraco stores these links and what the workflow looks like. I'm seeing some slowness, but it looks like a sql timeout, unrelated to Umbraco.
Well I have not been able to reproduce the error consitently. But in my case I suspect that sometimes danish characters æ,ø and å have been what messed it up since sometimes we add a name on a document type containing those characters and then somehow the autocompleting of the alias is messed up even though the character seems to have been removed.
But I think there are more ways to provoke it and of course there are more characters that could do it like " and ' etc.
A bad character can mess the underlying code up pretty badly if it's not being handled correct indeed. Ehm...but you could perhaps try searching the /app_data/umbraco.config to see if there are some weird characters in there that are not being handled correctly.
I've tried every character I can imagine in /app_data/umbraco.config without reproducing the error. It seems to be very resilient. It's a very odd bug, if I find anything else out I'll be sure to post it.
I've tried every character imaginable in umbraco.config with no luck, it seems to be very resilient. It's definitely an odd bug, but we're upgrading, so I suppose it doesn't matter anymore. If I find something else out I'll be sure to post it.
Ok - Sorry I forgot to mention that you should be able to fix it by simply publishing the nodes again by hittig "Save and publish" or simply bulk publish by right clicking the root node for instance.
How does "Link to Document" turn into "#" on every page?
I've seen this issue posted before where the Link to Document field becomes a # and the solution is to republish the sites. Does anyone know why this happens? Republishing did fix the issue, but I'm trying to find a cause. I find it hard to believe it all hinges on the umbraco.config, I have thoroughly added garbage characters and deleted pieces but it still works. Another question is where are these links stored?
Any insight on where or how the links are stored and what could wipe out all of them simultaneously is welcome. It could very well be a hardware problem, I'm just trying to figure out how to narrow the possibilities of causes.
Thanks.
Hi Peter and welcome to our :)
I'm guessing that you're using Umbraco 4.7? Not sure what is causing the issue except that it's a bug that seems to have been fixed in releases from v4.8+ and forward since I have not seen the error since.
Sometimes I've seen it happen if a illegal characters has been added as a document type alias for instance.
If I'm right in my assumption about, which Umbraco version you're using is it then perhaps possible to do an upgrade to a newer version?
/Jan
Hi Jan,
Yes, you are correct in the assumption, my apologies for forgetting to add it. And thank you for the welcome!
Upgrading is in the works, hopefully that does fix the bug. Do you know what the illegal characters are? Nothing was changed, it just happened one day, on every single page. I heard the Umbraco.config in app_data could be the culprit, but I added every possible illegal character I could think of and had no affect on the website.
At this point I'm trying to satisfy my curiousity of how Umbraco stores these links and what the workflow looks like. I'm seeing some slowness, but it looks like a sql timeout, unrelated to Umbraco.
Thanks!
Hi Peter
Well I have not been able to reproduce the error consitently. But in my case I suspect that sometimes danish characters æ,ø and å have been what messed it up since sometimes we add a name on a document type containing those characters and then somehow the autocompleting of the alias is messed up even though the character seems to have been removed.
But I think there are more ways to provoke it and of course there are more characters that could do it like " and ' etc.
A bad character can mess the underlying code up pretty badly if it's not being handled correct indeed. Ehm...but you could perhaps try searching the /app_data/umbraco.config to see if there are some weird characters in there that are not being handled correctly.
Hope this helps.
/Jan
Hi Jan,
I've tried every character I can imagine in /app_data/umbraco.config without reproducing the error. It seems to be very resilient. It's a very odd bug, if I find anything else out I'll be sure to post it.
Thanks for your help!
Hi Jan,
I've tried every character imaginable in umbraco.config with no luck, it seems to be very resilient. It's definitely an odd bug, but we're upgrading, so I suppose it doesn't matter anymore. If I find something else out I'll be sure to post it.
Thanks for your help!
Hi Peter
Ok - Sorry I forgot to mention that you should be able to fix it by simply publishing the nodes again by hittig "Save and publish" or simply bulk publish by right clicking the root node for instance.
Hope this helps.
/Jan
is working on a reply...