inherit
97216
0
Nov 26, 2024 13:53:14 GMT -8
Bennett 🚀
Formerly iPokemon.
3,622
January 2007
catattack
iPokemon's Mini-Profile
|
Post by Bennett 🚀 on Jan 22, 2019 17:07:40 GMT -8
If you remove theheight:150px;
from the div above "FIRSTNAME LASTNAME" it seems to fix the overlapping issue.
However, I'm not sure what you mean by tabbed sections in that post? Is it not supposed to scroll?
|
|
inherit
97216
0
Nov 26, 2024 13:53:14 GMT -8
Bennett 🚀
Formerly iPokemon.
3,622
January 2007
catattack
iPokemon's Mini-Profile
|
Post by Bennett 🚀 on Jan 14, 2019 18:24:08 GMT -8
If you're looking for some kind of automation to prune some of your spaces: www.freeformatter.com/html-formatter.htmlI would go for their tab delimiter (which would be 1 less character than 2 spaces as you were suggesting). |
|
inherit
97216
0
Nov 26, 2024 13:53:14 GMT -8
Bennett 🚀
Formerly iPokemon.
3,622
January 2007
catattack
iPokemon's Mini-Profile
|
Post by Bennett 🚀 on Jan 14, 2019 18:17:57 GMT -8
The template goes in your Board List area. Board > Board List.
|
|
inherit
97216
0
Nov 26, 2024 13:53:14 GMT -8
Bennett 🚀
Formerly iPokemon.
3,622
January 2007
catattack
iPokemon's Mini-Profile
|
Post by Bennett 🚀 on Jun 13, 2018 14:35:32 GMT -8
Presuming I found a bug in Style Tags, how would I go about reporting it? It's not a minor annoyance, and there's a possibility it is an exploit vector, though I'm uncertain of that part, hence my unwillingness to just put it in this post. (Yes pure CSS can be exploited). You can send me a PM if you so desire. There are a lot of ways CSS can be exploited for malicious purposes that cannot be filtered out by simple means that Javascript provides, but I would be curious as to what you consider an "exploit vector". |
|
inherit
97216
0
Nov 26, 2024 13:53:14 GMT -8
Bennett 🚀
Formerly iPokemon.
3,622
January 2007
catattack
iPokemon's Mini-Profile
|
Post by Bennett 🚀 on May 14, 2018 8:31:12 GMT -8
As long as the style tags are before that plug-in it shouldn't be a problem. The only other thing I would say to make sure you're doing is not using the visual editor when posting, but rather use the text editor solely. Bennett 🚀 Seems like the issue stems from the VDice Replacer plugin. Could it be because of the type of tags it uses? This has me scratching my head. Should I contact that plugin's author to see how we could find what's causing the issue? |
|
inherit
97216
0
Nov 26, 2024 13:53:14 GMT -8
Bennett 🚀
Formerly iPokemon.
3,622
January 2007
catattack
iPokemon's Mini-Profile
|
Post by Bennett 🚀 on May 13, 2018 7:14:34 GMT -8
My only suggestion would be to put Style Tags as high up in your plugin list as possible and try turning one plugin on/off at a time while keeping Style tags on and see if there is something interfering. I'm not sure if it's a plugin issue, or something in my css, but for some reason this post is not taking the attribute, break or no spaces tags. The same happens for this template in any part of the site...
The reason I'm not sure if it's the plugin is that it seems to work on the application template I have on the site.
Maybe someone's seeing something I'm not?Definitely a CSS issue. I'll fish around to see what it could be. Sorry for the trouble! I love this plugin. Thaks so much for sharing it! Edit again: so after reverting to an old css I had stored, and testing on another forum, it all works on the other forum, but not this one. Now I'm thinking it could be some other plugin affecting this one? I'm not sure now... I'll keep fishing around to see what I can find. |
|
inherit
97216
0
Nov 26, 2024 13:53:14 GMT -8
Bennett 🚀
Formerly iPokemon.
3,622
January 2007
catattack
iPokemon's Mini-Profile
|
Post by Bennett 🚀 on Apr 28, 2018 11:39:10 GMT -8
Hey Bennett, sorry if this has been asked before! I'm having some trouble with :before and :after pseudo-elements. Are these supported or nah? Unfortunately, those selectors are not allowed. Way back when it was a contingency that needed to be addressed in order for the plug-in to be allowed in the plug-in database because of potential security issues. |
|
inherit
97216
0
Nov 26, 2024 13:53:14 GMT -8
Bennett 🚀
Formerly iPokemon.
3,622
January 2007
catattack
iPokemon's Mini-Profile
|
Post by Bennett 🚀 on Apr 17, 2018 14:53:26 GMT -8
Bennett 🚀 - I'm not sure if your still doing work on this but is there any chance that this could be altered to at least strip out the style tag items for custom pages? fireinyourveins.boards.net/page/faq < Here's a link so you can see what currently happens Plugins cannot be run on custom pages, so that's unfortunately out of my control. |
|
inherit
97216
0
Nov 26, 2024 13:53:14 GMT -8
Bennett 🚀
Formerly iPokemon.
3,622
January 2007
catattack
iPokemon's Mini-Profile
|
Post by Bennett 🚀 on Mar 18, 2018 13:48:22 GMT -8
If you were to go back to that version of style tags (v2.1.0 I think), then it would work. You could maybe ask that forum for their Style Tag plugin. (even though the latest and greatest is 150% faster than the old version  ) Ooooh, hopefully that would work! The faster speed would be nice, but loading times weren't usually enough of a problem that I think people would be too broken up about it. That begs the question, though: H...how exactly would I go about getting a previous version of the plugin? :'D I have it installed on some past forums, but how to go about getting it from THERE to THIS site is a complete mystery to me. ;u; From version 2.1.0 on, the plugin was editable. So you should be able to go into the "Build" part of the plugin area in the admin panel and do an "export to computer" or whatever. And then take that and upload it on your current site. EDIT: You can get the old link here |
|
inherit
97216
0
Nov 26, 2024 13:53:14 GMT -8
Bennett 🚀
Formerly iPokemon.
3,622
January 2007
catattack
iPokemon's Mini-Profile
|
Post by Bennett 🚀 on Mar 18, 2018 13:31:03 GMT -8
If you were to go back to that version of style tags (v2.1.0 I think), then it would work. You could maybe ask that forum for their Style Tag plugin. (even though the latest and greatest is 150% faster than the old version ) Ooooh, hopefully that would work! The faster speed would be nice, but loading times weren't usually enough of a problem that I think people would be too broken up about it. That begs the question, though: H...how exactly would I go about getting a previous version of the plugin? :'D I have it installed on some past forums, but how to go about getting it from THERE to THIS site is a complete mystery to me. ;u; From version 2.1.0 on, the plugin was editable. So you should be able to go into the "Build" part of the plugin area in the admin panel and do an "export to computer" or whatever. And then take that and upload it on your current site. |
|
inherit
97216
0
Nov 26, 2024 13:53:14 GMT -8
Bennett 🚀
Formerly iPokemon.
3,622
January 2007
catattack
iPokemon's Mini-Profile
|
Post by Bennett 🚀 on Mar 16, 2018 18:08:37 GMT -8
I'm not sure what help I can be other than to suggest putting the style tag plugin below the Tabbed Sections plugin. The newest version of style tags goes from the inner most elements to the outermost, so if the tabbed sections are not there before style tags is executed, it'll go to the closest element and put its magic to work there instead of the html that the tabbed sections plugin puts in for its tags. Already tried this, unfortunately, and with no such luck. c': I've probably moved these plugins around in every possible combination of 'em, but the problem persists. c':
Aaaaah, sorry for bothering you with a problem that's probably not in your power to fix. Thank you for the quick response, anyway, and for getting back to me at all! <3 If you were to go back to that version of style tags (v2.1.0 I think), then it would work. You could maybe ask that forum for their Style Tag plugin. (even though the latest and greatest is 150% faster than the old version ) |
|
inherit
97216
0
Nov 26, 2024 13:53:14 GMT -8
Bennett 🚀
Formerly iPokemon.
3,622
January 2007
catattack
iPokemon's Mini-Profile
|
Post by Bennett 🚀 on Mar 15, 2018 10:29:50 GMT -8
Hello! This query of mine may be a little... off, and I apologize in advance if this isn't the place to make it. In truth, I'm having an issue with a different plugin than the Style Tags, but my friends' and I's best guess at the source of the problem actually lies here, instead. I've already left a message in the other plugin's support thread with this same issue, but I figured I'd take the extra step and bring it here, as well. At best, the issue lies here and we can get the problem solved. At worst – well, that's one possible source of issue to cross off the list!
I've been having issues with the Tabbed Sections in Posts plugin, which you can see here (in contrast to what it should look like, as seen in its code-identical counterpart); this is one of many, by which I mean every template I've posted on this board that: a) uses the Tabbed Sections in Posts plugin, and b) uses a class, more specially the [attr] tag within the [Ptab] tag. If no [attr] is present, the plugin works as it should. Since [attr] is used to denote classes via this pluggin, and this version of the Style Tags is the only one I've had this particular issue with, you can see why we thought to double check with this support thread as well as the Tabbed Sections thread. My friend – who I don't think has a Support account, so I can't tag her – has apparently had similar issues of non-functionality on her own recent board. There's a possibility this latest update has done something to make these two plugins non-compatible.
There's always a chance, of course, that the problem lies elsewhere, and I'm just an idiot for not having caught it yet! I've double checked my code in the template itself, taken out and re-added potentially conflicting scripts, and done a fair bit of plugin re-arranging, which I know has caused not identical, both other problems in the past – but none of these potential fixes have had any results. If you can think of anything else that I could try that may help, let me know! If you need more information, let me know! If this was completely the wrong place to post this and you'd like me to remove myself from this thread... l-let me know, and I'm very sorry! 8'D Thanks in advance! I'm not sure what help I can be other than to suggest putting the style tag plugin below the Tabbed Sections plugin. The newest version of style tags goes from the inner most elements to the outermost, so if the tabbed sections are not there before style tags is executed, it'll go to the closest element and put its magic to work there instead of the html that the tabbed sections plugin puts in for its tags. |
|
inherit
97216
0
Nov 26, 2024 13:53:14 GMT -8
Bennett 🚀
Formerly iPokemon.
3,622
January 2007
catattack
iPokemon's Mini-Profile
|
Post by Bennett 🚀 on Dec 12, 2017 11:06:45 GMT -8
Ack ok, yeah that works. Good to know. The PDF was a little hard to read at some points due to misalignment so I ended up creating myself a thread of your guide and linked it back to here. If you do happen to check it out and see something I got wrong please let me know. Thanks again! Yeah I just saw that now too.. I'll have to re-type it up. The old version of my document was on an older version of Word than what I use now, so that was probably what happened. |
|
inherit
97216
0
Nov 26, 2024 13:53:14 GMT -8
Bennett 🚀
Formerly iPokemon.
3,622
January 2007
catattack
iPokemon's Mini-Profile
|
Post by Bennett 🚀 on Dec 12, 2017 7:21:07 GMT -8
Hi again. I just wanted to say thank-you for fixing the link to your guide and maybe point something out. I'm pretty much a noob to CSS and whatnot so maybe I'm wrong but... In your guide you say "You may omit quotation marks if you prefer". The word "may" suggests to me that you can either use or not use the quotation marks. That it wouldn't matter because the code would work either way. When I got to the [var] tag section I tested your example and it wouldn't work. So I removed all the quotation marks and everything worked afterwards. Needless to say I won't be using quotation marks anymore. Using this exactly? [div]
[attr="class","my-class"]
This is my post!
[/div]
[var name="primary" value="black"]
[var name="secondary" value="blue"]
[newclass=".my-class"]background-color: [var="primary"]; color:[var="secondary"];[/newclass]It works for me! The problem you might be getting is copying from a PDF, quotes are replaced with the curly quotation marks, which do not parse in HTML. So those need to be replaced with plain ol' quotes ("). Otherwise, yes, you do not need quotations for any of the elements, but is suggested to keep things clean and correctly parsed when values get long. |
|
inherit
97216
0
Nov 26, 2024 13:53:14 GMT -8
Bennett 🚀
Formerly iPokemon.
3,622
January 2007
catattack
iPokemon's Mini-Profile
|
Post by Bennett 🚀 on Dec 11, 2017 20:04:24 GMT -8
Once disabled you can then edit the post and try to fix the problem. The post itself cannot be quoted by guests so I cannot really see the BBCODE that was used but the section in that post that starts with "0 Moons:" contains 21 DIVs and 17 of those are nested (meaning one DIV inside of another DIV inside that inner DIV and so on with that going 17 levels deep). It is generally nestings that goes too many levels deep that causes that plugin to choke, since it uses the memory expensive recursion technique to walk the DOM tree so at some point the stack runs out of memory. Usually when you see nestings like that it is because the post author opened a div ( [) but neglected to close them with a corresponding div closer ( [) so the browser automatically closes it for them all at the end of the post resulting in multiple levels of nested DIVs. Instead of:
[div] This is DIV #1[/div]
[div] This is DIV #2[/div]
[div] This is DIV #3[/div]
This is DIV #1 This is DIV #2 This is DIV #3 You get (when [
[div] This is DIV #1
[div] This is DIV #2
[div] This is DIV #3
This is DIV #1 This is DIV #2 This is DIV #3
the javascript engine saves the entire execution context unto the stack each time another recursion function is called and the stack eventually runs out of memory space once it gets too deep. My advice to Bennett 🚀 some time ago was to process the node list from the tail end thus taking advantage of the fact that nodes are returned in document order and you would be working from inner to outer which is obviously the intent of using that recursion but without the expensive memory consumption. I do not ever recall getting this suggestion, but did just do a rewrite of the plugin because I was bored and procrastinating other things. Benchmarks of the new plugin are in the 4-6 ms processing time for each post using style tags, rather than something like a total of 1-2s for all posts on the page with the old plugin. So Fern , look for the updated Style Tag plugin to be available in the plugin library later this week when the PB staff approves the new v2.2.0. EDIT: I posted the downloadable plugin file on the support page. |
|
)
