I have been alerted to an exploit within the spoiler tag, and this update addresses these issue.
v1.2.2 also includes a phrased "Show Spoiler" and "Hide Spoiler" for use within the Spoiler Tag.
Can you check if the latest version 1.2.2 fixed it?If you can't wait for the next release, here is a quick patch I'm using on my test forum. (Just need to replace the KingK/BbCodeManager/BbCode_Formatter/Base.php file).
I have no new features/enhancements in v1.2.2. I've already written and implemented a cache system for v1.3.Can you check if the latest version 1.2.2 fixed it?
Thanks
Does that mean that there won't be any queries anymore for spoiler bbcode? Are you going to address the no-javascript issue?I have no new features/enhancements in v1.2.2. I've already written and implemented a cache system for v1.3.
The answer is in the message your are quoting...Does that mean that there won't be any queries anymore for spoiler bbcode? Are you going to address the no-javascript issue?
So the answer is yes. Again, if you need a patch now, just look at the previous page.I've already written and implemented a cache system for v1.3.
No it's not. Read my reply to King Kovifor to know why.The answer is in the message your are quoting...
So the answer is yes. Again, if you need a patch now, just look at the previous page.
When a forum software hides content such like spoiler content from users with javascript disabled, it's cleary an issue, that needs to be addressed. This is called graceful degradation.See this post: http://xenforo.com/community/thread...-looking-spoiler-tag.17083/page-2#post-290111What you're calling a "no-javascript issue" is not an issue. XenForo is made to be used with javascript. And most of "spoiler bbcodes" all use javascript. If you don't want to use javascript, you can still do your own bbcode with a text that has the same colour than its background.
There will be a single query for BBCodes. It's impossible to get around. The query isn't intensive, it isn't going to destroy anything.
That's all enhancements. Meaning they'll be addressed in future versions.
[float=left][/float]
[float=left][/float]
[float=left][/float]
[float=left][/float]
[float=left][/float]
[float=left][/float]
[float=left][/float]
[float=left][/float]
[float=left][/float]
[float=left][/float]
[spoiler]This is a spoiler][/spoiler]
[spoiler]This is a spoiler][/spoiler]
[spoiler]This is a spoiler][/spoiler]
[spoiler]This is a spoiler][/spoiler]
[spoiler]This is a spoiler][/spoiler]
[spoiler]This is a spoiler][/spoiler]
[spoiler]This is a spoiler][/spoiler]
[spoiler]This is a spoiler][/spoiler]
[spoiler]This is a spoiler][/spoiler]
[spoiler]This is a spoiler][/spoiler]
v1.3 will have a cache system that will execute 1 query per session for user. The reason you have multiple queries executing for spoiler is beyond me, because none of the BBCode rendering actually utilizes queries except for the user ID and that's only to look up information.No it's not. Read my reply to King Kovifor to know why.
When a forum software hides content such like spoiler content from users with javascript disabled, it's cleary an issue, that needs to be addressed. This is called graceful degradation.See this post: http://xenforo.com/community/thread...-looking-spoiler-tag.17083/page-2#post-290111
Perhaps you didn't understand what I was saying. I am aware that a query is needed for the BB Code Manager to function, but again, the spoiler bbcode would slow down threads with spoiler bbcodes used if it produces additional queries spoiler by spoiler. Let me give you an example:
A post contains 10 float bb codes:
Code:[float=left][/float] [float=left][/float] [float=left][/float] [float=left][/float] [float=left][/float] [float=left][/float] [float=left][/float] [float=left][/float] [float=left][/float] [float=left][/float]
This would produce only 1 query, right?
Now imagine a post has 10 spoilers:
Code:[spoiler]This is a spoiler][/spoiler] [spoiler]This is a spoiler][/spoiler] [spoiler]This is a spoiler][/spoiler] [spoiler]This is a spoiler][/spoiler] [spoiler]This is a spoiler][/spoiler] [spoiler]This is a spoiler][/spoiler] [spoiler]This is a spoiler][/spoiler] [spoiler]This is a spoiler][/spoiler] [spoiler]This is a spoiler][/spoiler] [spoiler]This is a spoiler][/spoiler]
Ideally this would produce only 1 query as well, but it doesn't. It would produce 10 queries. One query for each spoiler. This needs to be fixed. I am using a similar spoiler bbcode for MyBB and it actually doesn't produce any queries. So the coding of your BB Code Manager needs to be optimized![]()
I read it and I insist. The reply is in your quoting text. And again, if you need a patch now, just find one of my previous post.No it's not. Read my reply to King Kovifor to know why.
If you find a way to make a toggle function only with CSS, I pay you a bottle of champagne ^^ If you need a none javascript spoiler tag, see my last post answer.When a forum software hides content such like spoiler content from users with javascript disabled, it's cleary an issue, that needs to be addressed. This is called graceful degradation.
To solve this, see my first answer of that post otherwise just be patient ^^Perhaps you didn't understand what I was saying. I am aware that a query is needed for the BB Code Manager to function, but again, the spoiler bbcode would slow down threads with spoiler bbcodes used if it produces additional queries spoiler by spoiler. Let me give you an example:
Oh I misunderstood it thenI'm caching the codes not the content. Spoiler shouldn't be executing multiple queries.
BBCode Title: TABLE WIDTH
BBCode Tag: TABLEWIDTH
Example: [TABLEWIDTH=400][TR][TD]This makes a 400px wide table[/TD][/TR][/TABLEWIDTH]
Activate BB Code : check
Require Option : check
Replacement start : <table width="%s" border=0 style="font-size: 0.8em">
Replacement end : </table>
I'll look into it as soon as I possibly can.i upgraded to 1.22 & no change. as you can see, all my table tags work fine EXCEPT tablewidth. i can go into the bbcode manager, click edit tablewidth, not change 1 thing & click save bbcode, & I get the error. any other tag and it just saves.
We use essential cookies to make this site work, and optional cookies to enhance your experience.