Spoiler Tag

Title: Spoiler
Tag: spoiler
Replacement:

 <div class="fieldset">
<table class="tborder" cellpadding="5" cellspacing="0" border="0" width="100%" align="center">
<tr>
   <td class="tcat" colspan="3"><a style="float:right" href="#top" onclick="return toggle_collapse('spoiler_{option}')"><input type="button" value="Show/Hide" /></a>Spoilers!</td>
</tr>
<tbody id="collapseobj_spoiler_{option}" style="">
<td class="alt1" align="$stylevar[left]" valign="top">{param}</td>
</tbody>
</table>
</div>

Example: [spoiler=example]This is Hidden![/spoiler]
Use Option: Yes
Image: Leave Blank

Q. Why do I have to "use option"?
A. This will solve a bug when not using it. In the first coding it wasn't used, but it would only collapse the first usage of "[spoiler][/spoiler]" in the thread. Using option in the code allowed to to specify which usage of the tags to collapse.

Bugs: It's open by default! I'm working on getting it closed by default.

[King Kovifor]

Originally Posted by SirAdrian

The unique identifier should be generated by PHP (hash, microtime, etc).

Then you could do [spoiler]HE DIES IN THE END![/spoiler] or if you want ... [spoiler=WARNING]HE DIES IN THE END[/spoiler] which would replace the default caption.

Just an idea to simplify the use.

How could I do that within the BBCode Manager?

[daboogas94e]

i can't seem to get the spoiler tags working at all

[King Kovifor]

Originally Posted by daboogas94e

i can't seem to get the spoiler tags working at all

What do you have in the BBCode Manager?

[smokey]

Originally Posted by Disasterpiece

is it possible to use php code in the code field? when yes, could you give me the php code for creating a random number? would be great

Here's a quick fix.

Create a plugin, for the hook location choose postbit_display_complete and paste the following php code in the box:

PHP Code:

$this->post['message'] = preg_replace('/\{rand_string\}/i',rand(0,32768),$this->post['message']); 


The above code will change {rand_string} in a post to a random number (making it unique).

In the spoiler bbcode you created, find both:

spoiler_{option}

Replace both with:

spoiler_{rand_string}

Also I replaced "Spoiler!" in the header to "Spoiler for {option}". Just a suggestion to all.

Thanks for the bbcode btw, it was a great idea!

[TheoMessinis]

Thank you! Great spoiler!

[mikkitine]

Originally Posted by Disasterpiece

Yeah, im kind of a noob in php, i can only html ^^

so, this is my modified code:

<div class="fieldset">
<table cellpadding="5" cellspacing="0" border="0" align="center">
<tr>
   <td colspan="3" align="center"><a href="#top" onclick="return toggle_collapse('spoiler_{option}')"><input type="button" value="{option}" /></a></td>
</tr>
<tbody id="collapseobj_spoiler_{option}" style="display:none;">
<td align="$stylevar[left]" valign="top">{param}</td>
</tbody>
</table>
</div>

i used the option param for the button's value AND the spoiler id. works in 80%; when users use different values for the buttons, but i wanted to use it in the signature. So there would be many buttons with the same id.

is it possible to use php code in the code field? when yes, could you give me the php code for creating a random number? would be great

Originally Posted by smokey

Here's a quick fix.

Create a plugin, for the hook location choose postbit_display_complete and paste the following php code in the box:

PHP Code:

$this->post['message'] = preg_replace('/\{rand_string\}/i',rand(0,32768),$this->post['message']); 


The above code will change {rand_string} in a post to a random number (making it unique).

In the spoiler bbcode you created, find both:

spoiler_{option}

Replace both with:

spoiler_{rand_string}

Also I replaced "Spoiler!" in the header to "Spoiler for {option}". Just a suggestion to all.

Thanks for the bbcode btw, it was a great idea!

I combined both of your suggestions and the result was still unchanged. Spoiler tags with the same option only open the first spoiler. In fact, spoiler tags with a different option still only open the first spoiler.

[scottevtv]

The tag begins as "Spoiler about...", and then if the user clicks and cicks again the "Spoiler about" text is gone. This was a bit confusing.