3 ms·
"I can advised [sic] you that the work needed to put the favicon live was complicated by an old environment (which has since been updated) that caused issues an
by corin_ 16y ago
"I can advised [sic] you that the work needed to put the favicon live was complicated by an old environment (which has since been updated) that caused issues and extended the time taken to carry out the work."
What?
- astrodust 16y agoMaybe this is a euphemism for "bunch of old people who don't know how the internet works but were put on the web site steering committee anyway and made a bunch of of absurd requests that had to be fulfilled in order to get approval".
- bad_user 16y agoYou missed the clarification: I can confirm that that the old website development environment was upgraded from one server to two.
- corin_ 16y agoHow does that have any impact on the cost of a favicon? Unless they were charged per FTP transfer...
- bad_user 16y agoWell yes, that and the original maintenance cost doubled. PS: if you pay attention, right now I am laughing really, really loud, so you might hear me.
- Groxx 16y agoI wonder if they were the ones who set the favicon up so it worked on their server. If that's the case, diving around someone else's code for £585 is pretty cheap.
- bad_user 16y agoBehold, the magic of Apache (or pretty much any web server) ... Alias favicon.ico /path/to/your/physical/location/favicon.ico Now please give £300 for selling you this tip.
- Groxx 16y agoHere's £150, because you only told me how to do it on one server :P Curiosity: does that work for subdomains with different favicons?
- bad_user 16y agoQuick and dirty solution, for each favicon you'll have a different virtual host inside Apache. And I fail to grasp the situation where you've got multiple subdomains setup inside the same virtual host config (through ServerAlias), but still having different favicons. But even for this case you can probably come up with something based on mod_rewrite.