I really like the way Bitt's ROT13 spoiler works, so I am going to implement it on the board. One piece I need though is PHP 4 code to do the following:

Take the string $Body, and ROT13 text between [rot13] this text [/rot13].

I'm horrible with string manipulation code, so I'm hoping someone here well versed in PHP can make the one line needed to do this.

Could be done in one line, but for clarity, three:

preg_match("!\[rot13\]([^[]+)\[/rot13\]!i", $body, $match);
$text = $match[1];
$rot13 = str_rot13($text);

Another test of the [spoiler] [/spoiler] tags

Spoiler:
Jbbg! Tbg Vg

There is one limitation though, only one spoiler per post.

And a test to see what happens with multiple spoilers in the same thread.

Spoiler:
Grfgvat, 1 gjb guerr

Ok, looks like it might need a bit of work, no idea why it is going bezerk there...

FYI, the board censor should be off.

It looks like it's also rot13'ing the the HTML codes in some weird way.

It looks like Jim was trying to do the "exple[i][/i]tive" trick, which at some point the board turned into "exple<i></i>tive", which for some reason got turned into "exple&gt;i&lt;&gt;/i&lt;tive", which the new code turned into the crud that appears there. I don't know why it multiplies itself, though.

If I understood what was changing it into the "&gt;"-style character entities, I might have a better idea how to avoid it. Maybe it's holding it that way in the database where they get changed back to "<"s when written out. The obvious thing to do would be to avoid changing HTML character entities, but I don't see a really efficient way to do that at the moment. You can't do it with your matching code very easily, and you can't do it with the javascript very easily, not that I think that's the place where it matters anyway.

I think you'll somehow have to match all the stuff inside the spoiler tags that isn't an HTML character entity, but you'll have to do that in a loop, and, it would seem, some sort of recursive addressible regex. I'll leave that up to someone more familiar with PHP.

That colored-text thing is looking more attractive all the time, huh?

Spoiler:
Ebpxa, I wish more boards would use this.

It probably has to do with where I put the spoiler code in the file. It goes through and searches for the UBB code to then replace with HTML, one item at a time. Bumping it up higher should fix it. I'll tinker with it more tomorrow.

To ensure it gets displayed properly every time, the ROT13 code is what is actually being stored in the database. For some reason with your javascript only code, it was decoding it initially from time to time if multiple ones were on the page.

As far as the color thing, that would make us like so many other boards. Kinda cool to have something unique here for the obscuring code.

Now don't y'all go overboard with this, kids.. it may also impact the ability of our already feeble search engine to locate such info with a Search later!

Cool, though!

Hmm... will it? The post is still in plain text, but the browser is just interpreting it differently.

test: Spoiler:
ebg13frnepu

Ooh, you're right.....

Didn't even think of the search aspect. Though I do have to agree, this does need to be used on a limited basis.

I may go in later and try to find a way to encrypt it during the HTML generation, and not the database phase where it is now.

As far as the search in general, I'll be trying to expand the Google search I just added. They have a site map thing that I need to make to try and ensure their results are up to date. They already spider the site quite frequently.

What can you do with Google that you can't do with the builtin search? The builtin one allows AND, OR, and NOT searches on words and phrases (though not complex combinations of them, not that Google allows that, either, AFAIK). It can, in combination, restrict to poster, time, and forum. Seems to me that it's more powerful than Google.

Spoiler:
Dhbgvat fcbvyref fubhyqa'g or oebxra nsgre guvf. Gur byq barf jvyy erznva hadhbgnoyr, ohg arj barf fubhyq or

As far as the PRE tag, it causes more problems then it solves, as a long spoiler won't be word wrapped properly, and manually word wrapping caused even weirder issues. For now, just hover over the beginning of a spoiler.

Spoiler:
Zr purpxvat gb frr ubj vg jbexf.

a-ok, works fine for one without much privlege.