Hey as some of you know I made an After Action Report for my Barrens campaign. Although the campaign is probably finished now, I noticed after the update that all the posts I have made with Spoiler tags "[Spoiler}" have gone, and the the hidden entries don't reveal themselves by clicking where my post says Spoiler.
Since I Spoiler tagged my entire AAR this means people can't read it anymore (or just that I can't, which would be even stranger). Any mods able to help me?
Full Version: Help Where Did My Aar Go?
Edit the messages with spoilers you want to get at again and you will be able to see your spoilered info. Then either copy/paste stuff into a new reply or erase and put back the spoiler tags. The new spoiler tags dont work like the old ones unfortunately.
QUOTE (Abbandon @ Feb 3 2008, 07:55 PM) 
Edit the messages with spoilers you want to get at again and you will be able to see your spoilered info. Then either copy/paste stuff into a new reply or erase and put back the spoiler tags. The new spoiler tags dont work like the old ones unfortunately.
Ok thanks for the tip. It will be alot of work though, and the new spoiler doesen't look so good with all those black stripes.
I have to admit I miss the old spoilers already... Guess that will have to be a pet project of mine.
Just an FYI, it was not a conscious decision to change how they work.. Its built into the skin and these skins are a pretty complex mess of dynamic html, css, javascript and php.
Just an FYI, it was not a conscious decision to change how they work.. Its built into the skin and these skins are a pretty complex mess of dynamic html, css, javascript and php.
I'm not certain, but it looks like it may just be a matter of including openClose in the new page javascript. It's not present in the new pages, and is the action the spoiler tags formerly performed. Of course, it's probably not that simple, but it's a starting point anyway.
(Copied from an archived page I have hanging around, though you people probably have more than I do)
Edit: also, the header for code blocks is ugly. But you can see that.
~J
CODE
function openClose(id)
{
var obj = "";
// Check browser compatibility
if(document.getElementById)
obj = document.getElementById(id).style;
else if(document.all)
obj = document.all[id];
else if(document.layers)
obj = document.layers[id];
else
return 1;
// Do the magic :)
if(obj.display == "")
obj.display = "none";
else if(obj.display != "none")
obj.display = "none";
else
obj.display = "block";
}
{
var obj = "";
// Check browser compatibility
if(document.getElementById)
obj = document.getElementById(id).style;
else if(document.all)
obj = document.all[id];
else if(document.layers)
obj = document.layers[id];
else
return 1;
// Do the magic :)
if(obj.display == "")
obj.display = "none";
else if(obj.display != "none")
obj.display = "none";
else
obj.display = "block";
}
(Copied from an archived page I have hanging around, though you people probably have more than I do)
Edit: also, the header for code blocks is ugly. But you can see that.
~J
QUOTE (FriendoftheDork @ Feb 3 2008, 08:20 PM)
It will be alot of work though...
Copy text to a text editor... use find and replace to change the start and end tags to the new format globally... copy text back to post.
Bye
Thanee
Is that supposed to somehow not be a lot of work?
~J
~J
QUOTE (Thanee @ Feb 4 2008, 09:22 AM)
Copy text to a text editor... use find and replace to change the start and end tags to the new format globally... copy text back to post.
We're talking about a fair number of spoilers. I am considering doing the same thing for my spoilers in the WttS forum, but it is quite a daunting thought.
QUOTE (Kagetenshi @ Feb 3 2008, 03:32 PM)
I'm not certain, but it looks like it may just be a matter of including openClose in the new page javascript. It's not present in the new pages, and is the action the spoiler tags formerly performed. Of course, it's probably not that simple, but it's a starting point anyway.
(Copied from an archived page I have hanging around, though you people probably have more than I do)
Edit: also, the header for code blocks is ugly. But you can see that.
(Copied from an archived page I have hanging around, though you people probably have more than I do)
Edit: also, the header for code blocks is ugly. But you can see that.
Thanks for the code post. I actually have a complete copy of the old Dumpshock running in my development environment. I will use the openClose function as a starting place. Right now, my head congestion is slowing me down and I have a busy week coming up.. But I will put code in place to deal with the old spoilers...
I also want to add back in the old spoilers as an option in the post form... Ah... Time and money.. Everything always comes down to time and money..
So, for now, should we not go about changing our spoilers, or won't it make a difference, or what? Help me out, because I'm somewhat clueless when it comes to this type of thing.
Unless you need the info right now for a hot topic or an inflight game, leave it. May take me a few weeks to work out the kinks, but as a heavy user of spoilers "In The Shadows"... I will eventually get them working..
Will do, and thanks again for all your work. 
Spoiler Tags
As a stop gap measure, I have hacked it so that you can click on [ Spoiler ] tags and see the text. The back ground css is not in place and its not fancy, nor is editing supported... but you can at least see the hidden text.
As a stop gap measure, I have hacked it so that you can click on [ Spoiler ] tags and see the text. The back ground css is not in place and its not fancy, nor is editing supported... but you can at least see the hidden text.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.