[CharlesS]

Code:
nuff said.

[shifuimam]

Did the CODE tag ever work?

I've only ever been able to get CODEX to work since I joined 'NN last year.

[Mastrap]

I also don't think [code] ever worked here.

[CODEX]CODEX however does[/CODEX]

[Mastrap]

dp, sorry

[Chuckit]

Originally Posted by Mastrap 

I also don't think [code] ever worked here.

[CODEX]CODEX however does[/CODEX]

CODE worked just fine before the redesign, and I thought it was working at some point afterwards, though I can't say I'm sure.

[besson3c]

It was working until a week or two ago.

What is with all of this bug regression MacNN admins? The image resize bug is another example....

I suggest commenting your vBulletin code patches with something like (sorry I can't wrap this with code tags):

// macnn <username> <date>
// patch description
code
// end <username> macnn

put your code into SVN branches, test each branch in a development environment. Grep for "macnn" in your existing code base when it comes time to upgrading and apply each patch by hand, and don't put the new version into production until all patches are accounted for and working.

Just my two cents...

[Demonhood]

when someone applied the latest VB update, they broke a few things (the code tag, the js resizer, etc.).
oops.

[besson3c]

Is there a sense of urgency in applying some of these vB updates in order to stay ahead of security issues?

[C.A.T.S. CEO]

Originally Posted by Demonhood 

when someone applied the latest VB update, they broke a few things (the code tag, the js resizer, etc.).
oops.

You guys really need a test server, what happened to the one you were using with effegee?

[Chuckit]

I didn't think effgee had a test server, and that's why all the CODEX tags and such wound up going live.

[besson3c]

You don't even need a test server to sort these out, all you need is a test account/install in a separate directory on your production server, and a subversion repository to manage your code base.

However, a test server would be a good in case you accidentally bring the server to its knees with an infinite loop or something, although it could just be a virtual machine.

[reader50]

Another vote for fixing the CODE tag.

[Simon]

Here's another one.

[C.A.T.S. CEO]

Third'd.

[Oisín]

And don’t forget the nice PHP tag

[turtle777]

BUMP.

Can we get it back, pleeeeeeaaaase ?

-t

[brassplayersrock²]

yeah, seriously. it'll be useful to have it again.

[ghporter]

Is the "CODEX" tag not good enough as a workaround? It IS a pain to not be able to use some sort of "code" tag, but I've made do with other tags as needed. I do not think that we have yet tracked down WHY the built in tag no longer works. As to whether or not there's an urgency in applying updates, most of the updates I've looked at were security or usability fixes, not just "here's a cool new feature that three people in the whole world will ever use" things.

[MarkLT1]

Originally Posted by ghporter 

Is the "CODEX" tag not good enough as a workaround? It IS a pain to not be able to use some sort of "code" tag, but I've made do with other tags as needed. I do not think that we have yet tracked down WHY the built in tag no longer works. As to whether or not there's an urgency in applying updates, most of the updates I've looked at were security or usability fixes, not just "here's a cool new feature that three people in the whole world will ever use" things.

I'm not sure how the original [code] tag worked, but CODEX does not provide for whitespace at the beginning of a line. i.e.- here is some spaced/indented code:
[codex]
int main() {
for(int i=0; i<10; i++) {
cout << i << endl;
}
}
[/codex]

now replace the white space at the beginning of the lines, with the - character, and you get what you are supposed to see:

[codex]
int main() {
----for(int i=0; i<10; i++) {
--------cout << i << endl;
----}
}
[/codex]

The second version of the code is much more easily readable.. the first version had the proper whitespace, but the CODEX tag does not replace whitespace with something like an &nbsp; to preserve whitespace at the beginning of a line.

For an example of how unreadable code can be with this codex tag, just take a look at the code I posted in the "accelerate framework" question in the developers forum. Without whitespace, it becomes quite unreadable.

[turtle777]

As a workaround, you can use a hard space (ALT + 255).

1
      2
            3
4

-t

[Oisín]

Alt + 255?

You need to quit that job of yours, turtle. Windows is getting to you.

(Using the Danish keyboard layout in OS X, Alt + Space gives a hard space; not sure if it’s th