Page 1 of 1
Favicon in LUWS Calendar
Posted: Thu May 10, 2007 7:47 pm
I get the old Netscape icon rather than the usual Christus in my browser as the favicon. Is this intentional?
Posted: Thu May 10, 2007 8:04 pm
I've seen that happen for those who are admins. Are you currently a stake or ward administrator?
Not Just Admin
Posted: Thu May 10, 2007 8:15 pm
Yes I am a Bishop, so I've given myself admin authority. However, I am not on the administrator page.
I had my wife try to login also (she is not an admin) and noticed that the Netscape favicon is ever-present on the LUWS session, not just in the calendar..
This should be an easy fix.
Posted: Fri May 11, 2007 7:47 am
This probably doesn't have anything to do with what role you have in LUWS, unless the developers who work on this have modified this specifically.
I know that all of lds.org isn't on the new servers which occurred when the new lds.org site launched recently. There aren't many indications of which pages are on which servers because the developers have been slowly modifying the old pages to have the new look to them, but this is one of the most obvious indicators. (I still see some of the old page formats from time to time) There is so much on the old servers that it will be some time before everything is moved over.
Servers or Code
Posted: Fri May 11, 2007 7:51 am
I'm not sure this would be a deployment issue regarding which server the code is on.
This type of error, in my experience is simply the JSPs are pointing to the wrong favicon. file.
Is the same code running on new servers showing a different favicon?
Posted: Fri May 11, 2007 8:03 am
Apparently the pages on the old servers haven't been modified to point to the new icon file.
LUWS on old servers
Posted: Fri May 11, 2007 8:37 am
100% of the Stake and Ward Web Sites (LUWS) section of lds.org is on the old servers. It will not be slated for redesign for some time. I can check into getting the Christus favicon working for it though. It has not been deemed a high priority, but you are right: It should be an easy fix.
On old secure servers
Posted: Fri May 11, 2007 9:21 am
It would appear that this only happens when on a secure url (e.g. https://secure.lds.org....)