When using Visual Web Dev you will get a 404 because it always serves out to the browser that a favico.ico file exists, whether you've said it does or not. IIS handles this differently
Let me be a little more descriptive, it's obvisouly needed since you per default think I'm an idiot =).
I have an phsycial favico.ico file present in the root folder, but when navigating to http://localhost/favico.ico I get the default umbrakko 404 page. I have tried looking for anything related in the /config files to no avail. I thought there might be some configuration requirered since /css and /images-files resolve correctly. So before I jump into Reflector to find the solution, I thought I'd ask here first to see if there were anyone else that had experienced this problem before me.
I have worked 7 years with dev-development/system development, so I now how a favicon is created ;). It's the first time using umbrakko though. And thus far, I have to say, I'm not impressed...but that's another discussion =D.
Thank you very much for any quick and helpful insights in this matter...
yeahright, I don't think you're an idiot, I make no assumptions on your technical background, only trying to help here. :-)
Few things we need to clarify... first, you keep referencing "favico.ico", is that the actual filename? because it should be "favicon.ico".
Which version of IIS are you running? Which version of Umbraco? Do you have the extensionless URLs enabled? (via the "umbracoUseDirectoryUrls" setting in the Web.config)
People as Aaron and Lee are trying to help you as much as possible, but you don't seem to appreciate their efforts in trying to understand and resolve your issue.
If you're not impressed with umbraco so far, could you explain us why, umbraco is completely open source, so you're invited to let us all know your thoughts. I'm sure both core team and community WILL appreciate whatever you have to say.
that said, I currently don't have an answer to your question apart from what's already been said by Aaron and Lee.
Umbraco version: 4.0.3 Tested with the "umbracoUseDirectoryUrls"-setting both enabled and disabled, no luck.
P.S: The "idiot"-part was said with
tongue in cheek. I will try to express my myself in a more "dry" tone =D
And as regard to Umbrao itself. I'm just used to using my own tailor-made systems. I'm now forced by the client/employer to use umbraco, which thus far I think is hindering my flow, compared to what I'm used to. What bugs me the most at the moment is the GUI, it just looks unprofessional. It aslo has some bugs in it, what I have found thus far is that sometimes the left menu doesn't update properly after addning nodes, and you can't remove inserted macros without editing the html-source manually in the RTF-editor. It doesn't feel right to give the client a CMS system with that GUI when they are paying up and over €60k for a system. And a mediocre problem like I'm having now isn't helping either...
/With the most sincere intensions and "happy thoughts" i can give you atm =)
Hmm, you're client is forcing you to use umbraco, well, seems the client likes it then... Agree, sometimes feel the need to completely skin the backend to my needs, but that's just me and not the client talking. Rarely meet clients who have issues with the "unprofessional" look of the backend as they rather focus on functionality. (well, there's a saying that "there's no accounting for tastes")
Ok, but we're getting really off-topic. your issue with left menu not properly updating after adding is a real issue, that should've been resolved in v4.1, which has a vastly improved menu handling.
Can you repro this "I can't remove inserted macr's without editing the html source" as it may sound as a bug and should be reported on Codeplex. TIA.
Hey yeahright, let us know what happens with Morten's suggestion of adding it to the 'umbracoReservedUrls' values.
Was there a typo in the "favicon.ico"?
As for some of your other issues, there are many many ways to use Umbraco that suits you (and your clients) best.
Personally I hate inserting Macros into the RTE, (hate it with a passion)! I use the Macro Picker data-type as an alternative. This will be a default (and improved) data-type in v4.1. (We're all eagerly waiting for v4.1!)
Yeah, that seems to have done the trick for me. Thanks.
To clarify; The clients are not forceing us to use umbraco per se, just any open source system so they have the choice to take the site and move to another company if they wan't to. So in practice it is our technical advisor that is forceing me.
An other negative thing that just came to me is the documentation. It has a
lot to be desired. Since I don't like working with XSLT one bit. I have tried getting my mind oround it many times during these 7 years of dev, but I just think it makes things worse. That said, I'm trying to use the "umbraco.presentation.nodeFactory" part of the API as much as I can. The part I don't like with that is the lack of strongly typed properties. I.e. new Media(mediaId).getProperty("umbracoFile"), the "umbracoFile" part was the hart bit to find out, well not hard but "tricky". I dont know if it is documented somewhere i the documentation, either way I prefer to have entities with strongly typed properties instead...for faster coding. And I find "Summary for [method]/[Class]" entries for comments in many places, not quite up to MSDN standard, I think.
Another thing I noticed on the backend is the JavaScript implementation. If youre are to implement a custom sections there are some JavaScript-property on the module you are supposed to override that says something like "document.top.right.location.href" and that just makes my brain ache since I also work much with the fronted. I always wan't my javascript code seperate from the backend code. But that is just me being picky, I know...
I understand your frustrations completely. The unfortunate thing for you, is that you are starting out with Umbraco about 6 weeks too early... as a LOT of these issues have been resolved in Umbraco v4.1 (because they were bugging a lot of other Umbraco devs too). We're expecting to see an RC in the next 6 weeks.
In the meantime, take a read over Aaron (slace) Powell's blog: http://www.aaron-powell.com/umbraco He wrote LINQ to Umbraco (which will be part of v4.1), he hates XSLT too! :-)
As for the back-office JavaScript, there have been loads of improvements in v4.1 - specifically with the section trees and combination/minification (using the ASP.NET Client Dependency Framework)
favico.ico => 404
Topic says it all.
How do I make /favico.ico not resolve to 404, plz thank you?
Create a favico.ico file.
When using Visual Web Dev you will get a 404 because it always serves out to the browser that a favico.ico file exists, whether you've said it does or not. IIS handles this differently
Well, I'm using IIS...?
Hey yeahright,
As slace says, you need to create a favicon.ico file, and place it in the root of your website.
If you are not familiar with favicon.ico, some background info is on Wikipedia:
http://en.wikipedia.org/wiki/Favicon
If you need help creating a favicon.ico, this tool is pretty good:
http://www.favicon.cc/
Cheers, Lee.
Ok.
Let me be a little more descriptive, it's obvisouly needed since you per default think I'm an idiot =).
I have an phsycial favico.ico file present in the root folder, but when navigating to http://localhost/favico.ico I get the default umbrakko 404 page.
I have tried looking for anything related in the /config files to no avail. I thought there might be some configuration requirered since /css and /images-files resolve correctly.
So before I jump into Reflector to find the solution, I thought I'd ask here first to see if there were anyone else that had experienced this problem before me.
I have worked 7 years with dev-development/system development, so I now how a favicon is created ;). It's the first time using umbrakko though. And thus far, I have to say, I'm not impressed...but that's another discussion =D.
Thank you very much for any quick and helpful insights in this matter...
yeahright, I don't think you're an idiot, I make no assumptions on your technical background, only trying to help here. :-)
Few things we need to clarify... first, you keep referencing "favico.ico", is that the actual filename? because it should be "favicon.ico".
Which version of IIS are you running? Which version of Umbraco? Do you have the extensionless URLs enabled? (via the "umbracoUseDirectoryUrls" setting in the Web.config)
Cheers, Lee.
Hi yeahright,
People as Aaron and Lee are trying to help you as much as possible, but you don't seem to appreciate their efforts in trying to understand and resolve your issue.
If you're not impressed with umbraco so far, could you explain us why, umbraco is completely open source, so you're invited to let us all know your thoughts. I'm sure both core team and community WILL appreciate whatever you have to say.
that said, I currently don't have an answer to your question apart from what's already been said by Aaron and Lee.
Cheers,
/Dirk
Umbraco version: 4.0.3
Tested with the "umbracoUseDirectoryUrls"-setting both enabled and disabled, no luck.
P.S: The "idiot"-part was said with tongue in cheek. I will try to express my myself in a more "dry" tone =D
And as regard to Umbrao itself. I'm just used to using my own tailor-made systems. I'm now forced by the client/employer to use umbraco, which thus far I think is hindering my flow, compared to what I'm used to.
What bugs me the most at the moment is the GUI, it just looks unprofessional. It aslo has some bugs in it, what I have found thus far is that sometimes the left menu doesn't update properly after addning nodes, and you can't remove inserted macros without editing the html-source manually in the RTF-editor.
It doesn't feel right to give the client a CMS system with that GUI when they are paying up and over €60k for a system.
And a mediocre problem like I'm having now isn't helping either...
/With the most sincere intensions and "happy thoughts" i can give you atm =)
In web.config, add it to this key:
That should prevent umbraco from trying to handle the url.
Hmm, you're client is forcing you to use umbraco, well, seems the client likes it then... Agree, sometimes feel the need to completely skin the backend to my needs, but that's just me and not the client talking. Rarely meet clients who have issues with the "unprofessional" look of the backend as they rather focus on functionality. (well, there's a saying that "there's no accounting for tastes")
Ok, but we're getting really off-topic. your issue with left menu not properly updating after adding is a real issue, that should've been resolved in v4.1, which has a vastly improved menu handling.
Can you repro this "I can't remove inserted macr's without editing the html source" as it may sound as a bug and should be reported on Codeplex. TIA.
Already loving the feedback!
Cheers and thanks for your thoughts and feedback.
/Dirk
Hey yeahright, let us know what happens with Morten's suggestion of adding it to the 'umbracoReservedUrls' values.
Was there a typo in the "favicon.ico"?
As for some of your other issues, there are many many ways to use Umbraco that suits you (and your clients) best.
Personally I hate inserting Macros into the RTE, (hate it with a passion)! I use the Macro Picker data-type as an alternative. This will be a default (and improved) data-type in v4.1. (We're all eagerly waiting for v4.1!)
Cheers, Lee.
Yeah, that seems to have done the trick for me. Thanks.
To clarify; The clients are not forceing us to use umbraco per se, just any open source system so they have the choice to take the site and move to another company if they wan't to. So in practice it is our technical advisor that is forceing me.
An other negative thing that just came to me is the documentation. It has a lot to be desired. Since I don't like working with XSLT one bit. I have tried getting my mind oround it many times during these 7 years of dev, but I just think it makes things worse. That said, I'm trying to use the "umbraco.presentation.nodeFactory" part of the API as much as I can. The part I don't like with that is the lack of strongly typed properties. I.e. new Media(mediaId).getProperty("umbracoFile"), the "umbracoFile" part was the hart bit to find out, well not hard but "tricky". I dont know if it is documented somewhere i the documentation, either way I prefer to have entities with strongly typed properties instead...for faster coding.
And I find "Summary for [method]/[Class]" entries for comments in many places, not quite up to MSDN standard, I think.
Another thing I noticed on the backend is the JavaScript implementation. If youre are to implement a custom sections there are some JavaScript-property on the module you are supposed to override that says something like "document.top.right.location.href" and that just makes my brain ache since I also work much with the fronted. I always wan't my javascript code seperate from the backend code. But that is just me being picky, I know...
My 2 cents so far...cheers
I understand your frustrations completely. The unfortunate thing for you, is that you are starting out with Umbraco about 6 weeks too early... as a LOT of these issues have been resolved in Umbraco v4.1 (because they were bugging a lot of other Umbraco devs too). We're expecting to see an RC in the next 6 weeks.
In the meantime, take a read over Aaron (slace) Powell's blog: http://www.aaron-powell.com/umbraco He wrote LINQ to Umbraco (which will be part of v4.1), he hates XSLT too! :-)
As for the back-office JavaScript, there have been loads of improvements in v4.1 - specifically with the section trees and combination/minification (using the ASP.NET Client Dependency Framework)
Yeah, I saw that Linq to Umbraco project. Unfortunatley, the project I'm working on is due to be complete in about 6 weeks. Just my luck I guess.
I'll read up more on 4.1 and see if there are any updates that will comfort my mind =) Thanks
is working on a reply...