As you know, some coding was affected by site updates. There have been troubleshooting tips and fixes for common problems in a few topics here, so I've compiled them into this post. If there's anything not here that you think should be added, please let me know.

---

How to fix it (Click to open)

This is the easiest way to restore your code:

1. Select all of your code and COPY it.
2. Go to an online "html entities decoder", for instance this one (warning: link is offsite)
3. PASTE your code into the text box and click "Decode" to get your result.
4. Replace your profile code with the decoded text.

If you don't want to use a free online tool, you can use Find & Replace in any text editor: -- Replace > with > -- Replace < with < -- Replace " with " In most cases, doing these three find-and-replace commands will suffice to fix it.

---

The good news is it is usually not as bad as it looks. You don't need to rewrite your entire profile. Usually the required fix is just 1-2 lines of code; the tricky part is figuring out what fix is required.

1. This one fixes most profiles, so definitely give this a try. Add this to the beginning of your CSS. html,body,,-content,{position:static!important;} .container-fluid {position:absolute;top:0;left:0;right:0;bottom:0;}If this fixes your profile, but the entire thing is now shifted to the left or right, simply tweak the values for left and right in the second line. For example: left:176px;

2. If your profile is mostly fine, but has extra scrollbars, try the following. {height:auto!important;} 3. Pages now have an extra container, with the CSS id "main-content". In some cases, the code can be fixed by looking for CSS rules on containers and adding this. For example, if you see a CSS rule that begins with this - html,body,,Try adding the main-content, so it looks like this - html,body,,,-content

---

The new sCode processor is a lot stricter about enforcing the rules of both sCode and HTML. Please see this topic to read more about the sCode update itself: Update: New sCode Processor And check out the updated sCode reference as well.

Spoiler titles

When using the spoiler= sCode, you can no longer include sCode within the title; it must be plaintext. If you need a fancier title, you can use this workaround for now: [spoilertitle]

Fancy title

[/spoilertitle][spoilercontent]Hello world![/spoilercontent] Which will look like this: [spoilertitle]

Fancy title

[/spoilertitle][spoilercontent]Hello world![/spoilercontent]

If you are targeting spoilers with CSS, use the classes .spoiler-click for the title and .spoiler-text for the content.

Style tag and quotes

When including CSS in a profile, make sure your style tag is opened by one of the following: (Preferred) <style type="text/css"> <style> Examples of things that won't work: <style type=text/css>

<style type='text/css'>

Order of closed tags

Make sure that nested tags are closed in the correct order. For example: Hellowill result in an error. The correct order would be: Hello

Extra line breaks due to br tag

In some places, if you use both a br tag AND a line break (via the enter key), it will interpret each of those as a line break and will give you double line breaks as a result. For example: hello
world Will give you two line breaks. But this will give you just one line break in between the lines: hello world This will also only give you one line break: hello
world

Square brackets inside CSS

If you have something like this inside style tags, it will break: div[style^='width:50%'] { display:none; } This is because of the square brackets within the code. This is unintentional, and will be fixed, but is mentioned here because it could be causing your code to break.

Make sure you check for other HTML syntax errors as well, such as: missing quotation marks, missing closing tags, unclosed divs, etc

---

Still having issues? Feel free to make a topic about your problem. Please paste your code somewhere (we recommend Pastebin.org - link is offsite!) and link both the pastebin AND the profile in question when asking for help.