Arie (arie) wrote in xxcustomization,
Arie
arie
xxcustomization

Standard responses to new *_HEAD changes, feel free to modify.

These are based on the standard response created by rahaeli here. Also please see FAQ124 for a list of what tags are allowed. You can also reference this FAQ should a user ask what is allowed and, as you'll see below, it is useful for giving to users who are asking for help with non-*_HEAD overrides that need to be warned about the change.

As a side note, any cust privs who haven't done so already may wish to stop by lj_support and introduce themselves to the new sysadmin.


Free accounts, already modified their *_HEAD, asking about 'xx'
FAQ Reference: What are the paid account benefits?

There was a change to the override system, implemented recently. Previously, any element was allowed in the *_HEAD overrides. This had the effect of breaking many browsers, and causing your journal to display improperly.

If you attempt to edit your overrides and you have used a tag that is not allowed in the head of the document -- such as <DIV>, <SPAN>, <IMG>, and many other tags -- that tag will be rendered inoperable by adding "xx" to the beginning of the tag at the time of editing your overrides. This is to increase the standards-compliant HTML that LiveJournal outputs but still allow you the ability to see what overrides you were using.

If you want to keep using that effect, you can purchase a paid account and create a custom style, which are not limited by this change. Paid accounts start at as little as $5 USD for two months, and come with a number of additional features. Further information on paid accounts can be found in the above FAQ.

I apologize for the inconvenience.


Free accounts, helping with other overrides, have not modified *_HEAD

Please add this, or a variation on it, to the bottom of an answer for a user whom you notice has an existing *_HEAD override that contains elements that will be stripped. This means that you will need to check the source of all users even if they are only asking for help with comments links.

Also, you should be aware there was a change to the override system, implemented recently. Previously, any element was allowed in the *_HEAD overrides. This had the effect of breaking many browsers, and causing your journal to display improperly.

If you attempt to edit your overrides and you have used a tag that is not allowed in the head of the document -- such as <DIV>, <SPAN>, <IMG>, and many other tags -- that tag will be rendered inoperable by adding "xx" to the beginning of the tag at the time of editing your overrides. This is to increase the standards-compliant HTML that LiveJournal outputs but still allow you the ability to see what overrides you were using.

You will still be able to modify and edit your other overrides without noticing this change but if you attempt to edit or change your current *_HEAD override you will see this change. You can find more information on what tags are permitted here: http://www.livejournal.com/support/faqbrowse.bml?faqid=124 .


Paid Accounts, were using overrides, asking about xx, don't have a custom style

The given FAQ reference is useful even if they are currently using a custom style because it provides instructions on creating a new one if they want instead of adding to their existing one.

FAQ Reference: How do I make a custom style?

There was a change to the override system, implemented recently. Previously, any element was allowed in the *_HEAD overrides. This had the effect of breaking many browsers, and causing your journal to display improperly.

If you attempt to edit your overrides and you have used a tag that is not allowed in the head of the document -- such as <DIV>, <SPAN>, <IMG>, and many other tags -- that tag will be rendered inoperable by adding "xx" to the beginning of the tag at the time of editing your overrides. This is to increase the standards-compliant HTML that LiveJournal outputs but still allow you the ability to see what overrides you were using.

If you want to keep using that effect, you can create a custom style and move the tags to the proper part of the *_PAGE section.

{insert specific instructions for what needs to be moved where}

Here its best to give them instructions for moving the entire override into their custom style. This does several things, not the least of which is demonstrating exactly how much easier life is when using a custom style. Especially if they are using an override to rewrite the navigation banner or the like. I would recommend actually cutting out the sections of code and then saying this section will need to go foo, this section will need to go bar and so forth, with a brief description of what line of the *_PAGE section to look for to put the code before or after or between at your preference.

Paid accounts, helping with other overrides or questions, have not modified *_HEAD

This is a combination of the free accounts standard response for when you are working on something else and the paid accounts response, but this asks them to open a new request since the move might involve extensive explanation. Basically we can't tell if they already have a custom style or not somewhere so we have to assume they don't if they are currently using one of the system styles. If you want to check the styles browser to see if they have any public custom styles they just aren't using that's fine, but I don't see any need to do that as the response below simply asks them to open a new request if they need help with moving their overrides. Please add this, or a variation on it, to the bottom of an answer for a user whom you notice has an existing *_HEAD override that contains elements that will be stripped. This means that you will need to check the source of all users even if they are only asking for help with comments links.

Also, you should be aware there was a change to the override system, implemented recently. Previously, any element was allowed in the *_HEAD overrides. This had the effect of breaking many browsers, and causing your journal to display improperly.

If you attempt to edit your overrides and you have used a tag that is not allowed in the head of the document -- such as <DIV>, <SPAN>, <IMG>, and many other tags -- that tag will be rendered inoperable by adding "xx" to the beginning of the tag at the time of editing your overrides. This is to increase the standards-compliant HTML that LiveJournal outputs but still allow you the ability to see what overrides you were using so they can be moved into a custom style.

You will still be able to modify and edit your other overrides without noticing this change but if you attempt to edit or change your current *_HEAD override you will see this change. You can find more information on what tags are permitted here: http://www.livejournal.com/support/faqbrowse.bml?faqid=124 . If --after you have made the changes described in this request-- you would like help with moving your current overrides into a custom style, please open a new request stating your desire to do so and support volunteers will be able to assist you.


The four above responses will give everyone a jumping off point for handling most of the situations that will come up. Just keep in mind, we like this. Right? Right?? ;)

You guys are the best!
Subscribe
  • Post a new comment

    Error

    default userpic

    Your IP address will be recorded 

    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.
  • 10 comments