Update: New sCode Processor
Filter
Show Official Posts OnlyReplies
At first glance, you are missing a lot of semicolons in your CSS. Try fixing the semicolons first, and let me know if you still have issues after that and I'll take a closer look :)
🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights
Well, my original code wasn't missing those. That's what the code looked like after I ran it through a "beautifier" for CSS. Doesn't make a difference on my profile either way. Changed it back to the "ugly" original code now and it still looks like this: X
And here's the original code: X
Can you share the contents of your About section? (The "blank" widget on the profile where you have your About text) I think there's an unclosed HTML tag or something there.
🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights
Sure, although the only thing that I could see was a div-tag that might be unclosed. Closing it did not affect the look of my profile though. Here's the content of the About section: X
Is there a reason you have all the table tags that are built-in to the profile itself repeated here? Like this line:
This element is just supposed to have a picture and text in it right?
Try just this: https://pastebin.com/a44CEmxT [edit] If you still have issues after that, please make a post in this section of the forums as it seems to be an issue with custom code rather than any glitch in the new sCode processor. Thanks. 🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler.
stay in the loop! join and check out the latest admin post highlights
Question. Does figures no longer work with this update? Because I'm using figures to keep my pet buttons organized but it's all f---ed up now.
This is the code I use for that part: X
I want to have them in rows with 5 buttons per row, not the way they look right now: X (under "My darling army!")
And I tried changing the img-tags from being in [] to <> but that just made all the buttons disappear. No changes were made that should affect what HTML tags are allowed. But I'm not sure why you're using a figure tag there instead of a normal div. As for the images, change them to HTTPS if you're using the img tag (the https requirement is not new) 🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler.
stay in the loop! join and check out the latest admin post highlights Question: how trustworthy is the Preview tool? I find that sometimes what actually appears on the forum/etc is not the same as what the Preview said it would be. Is that related to the new sCode processor? I've been writing a big post in Notepad++, and when I copypaste it over to the forums and hit Preview to check my sCode, then things turn out wonky even though I've quintuple-checked my tags. Using the Li tag breaks Spoilers, for example.
[topic not found] I see that "- bug/butterfly emoji picture thing!" is listed under fixed. Is that the 🦋 that I reported? It isn't showing as fixed for me on either forums or pet profiles (my pet Jailyn has a section overflowing that used to have butterflies as bullet points essentially)
Jailyn
Thanks for the heads up. Going to fix my board now haha. I appreciate you putting the instructions on how to fix the problems in the first post! They're now accurate, and can be trusted. They sometimes mismatched when the rollout was in progress because it was being rolled out gradually. It was fixed but then unfixed cuz the fix broke a LOT of other stuff - sorry! It was a good lesson on not rushing fixes :x A better fix is in the works. 🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler.
stay in the loop! join and check out the latest admin post highlights
One more question - were fonts removed/changed? We were using a specific font on our thread, and it appears it's no longer functioning. No, they should be the same (I think)
What is the sCode you're using? 🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler.
stay in the loop! join and check out the latest admin post highlights
It's the Chelsea Market font - it's just quit working. But googling it...it seems like they've changed how it looks also o_O I know for a fact it didn't look like wonky writing when I had it before.
I can confirm that the sCode for font is still working correctly. I tried and it correctly becomes:
🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler.
stay in the loop! join and check out the latest admin post highlights
It was supported though. That's kind of the thing. It worked fine until the sCode update...that's why I asked. It's not working on either browser I use. As I said, your issue is just that it's a non-standard font and might not be supported by the viewer's computer. In any case it is not a bug. The sCode is correctly being converted into CSS, which is all the sCode processor does. Whether it is a valid or working font is not something we have any control over. 🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler.
stay in the loop! join and check out the latest admin post highlights
Okay. It was valid and working on this exact computer right until the update. That's literally all I'm telling you. Which is why I asked if alternate fonts were just no longer supported on the site then. Because it's the exact same browser version (well, multiple since I checked on more than one) and computer I've been using. And it's not just that font. I can check the tags for multiple boards and see that any non-standard (ie: arial, verdana) fonts no longer work. Obviously, the answer is maybe just that they're not supported anymore at all. But it's not on my end specifically. I'm not trying to be testy or argumentative, but nothing on my end changed, which is the only reason I bothered asking you at all, since the only change has been to the sCode processor. Ooh so I was taking a closer look and I think I see what the issue is: missing quotation marks in the HTML.
And yeah, no worries and no argumentative-ness meant on this end either. I definitely appreciate that you brought it up, and I apologize if I sounded dismissive. I try to give the best answer I can, but I do still look into every report (which is why I eventually noticed the mistake here) so I didn't mean to sound so dismissive. 🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler.
stay in the loop! join and check out the latest admin post highlights
It's totally alright, I understand that sometimes it's tiny little things that kind of wonk it up. I'll go ahead and try it with the quote marks and see if that works! Thank you for looking again ❤️ [edit]
It's still not working =/
And I tried with Garamond (which I know is supported everywhere) and that doesn't work either. So I give up for now haha.and so on.
useful threads
The Giant List of Usability and Random Improvement 2.0
Comprehensive Guide to Battle Opponents (v2)
[topic not found]
I suspect your issue is just that it's a non-standard font and might not be supported by the viewer's computer. In any case it is not a bug.
This should be
God that is subtle x-x