Welcome to the MacNN Forums.

Is that new? I don't remember seeing it before. And what is it? Looks a bit metallic, yet sexual.

Just sayin'.

It used to have one (originally brought up in this thread), although the recent look - that silver/embossed mix - is new.

Are we talking about the vBulletin logo icon? It's kinda bland...

I like the favicon that came with effgee's design.

Hmmm... I forget what that looked like.

Edit: I don't wonder if this favicon wasn't automatically added when they upgraded vbulletin.

Me too, why was it changed? Only last week or so we had effgee's design

vBulletin was just upgraded and that's usually the reason the favicon breaks anyway.

I don't mean to sound like a jerk or a bitch, but I don't understand why you guys don't have a test environment for testing these forum upgrades? Virtually every time you upgrade the forum, something is left behind - be it the image resizer, favicon, etc.. If you really want to upgrade the live, production system this way, I would at least look into a better way to account for all of your code changes and/or customizations. I don't understand why you guys keep on repeating the same mistakes.

Maybe because there are not enough anal mods to find all the problems ?

Average Joe'NN is just so good at it...

-t

I'm not too into the new silver favicon. I don't think it goes too well with the forum itself. But I'm new to design though.

applejacks: it's the vBulletin logo, not something that somebody at MacNN designed.

We TRY to test everything. But every vBulletin upgrade breaks something DIFFERENT. Some of them break their own code tag function (most of the updates seem to do this). Others tweak something else that breaks the image sizer (our own coding on top of vBulletin). It's not us messing around and breaking stuff because we HAVE used an independent system for live testing. It's vBulletin's updates that keep breaking things.

vBulletin is a HUGELY complex system-I doubt anyone really understands it thoroughly. So when we install an update, while we know something is going to need attention, we don't always know what. That's one of the uses of this forum. "Hey guys! The dohickey is frabbled. Again! Fix it please!" That sort of thing. And as turtle so delicately puts it, the staff is generally busy busting shoe spammers and tossing buckets of water on flame wars, so meticulously testing each feature, function, button and so on, being kind of time-intensive, is not something we can manage.

Why not come up with a simple checklist of things that are inclined to break between each release and test these, not putting the upgrade into production until everything checks out?

In the case of your favicon, this is simply a case of this file being present in your document root, so there is nothing to test there, this was simply an oversight.

One way to track your code changes is to insert a comment into your code wherever you make a change that includes the string "MacNN", and then before each upgrade:

grep -rl "MacNN" *

to get a listing of all of your files with this comment. Upgrading to a newer version of vBulletin is not hard, these problems are not inevitable, it just needs better procedures.

I'm not the code guy-I can handle HTML and a bit of C and Java, but that's it. This monster is built on PHP and I don't know what else. The thing is that it seems that the breaks are never in the same place-and sometimes it appears at first that something works but later doesn't. Too many layers interacting I think.

I'd like to have our own favicon, but I'm kind of up to my eyeballs in school and thus completely out of imagination.

I wonder if there'd be much interest in designing a MacNN favicon, or at least one for the forums...

Let's use the one we had a few days ago.

^ ja ja. much better

We have had a favicon for at least a year now. You don't have to design anything. It's the same as the macnn.com main site uses..