FYI: FAQ 177 (custom S2 style FAQ) has been overhauled to take into account the types of layers and stuff. Notably:

* it now mentions theme layers, not just layout layers
* it can therefore be used in cases where people should create theme layers (not just in cases where they want to create layout layers)
* there is a warning on user layers and overwriting
* I like asterisks
* ...also chocolate.

Okay, so the last two aren't in the FAQ. But, anyway.

Just so y'all know (especially those of you that don't watch lj_userdoc):

FAQ 140, "o noes my overrides don't work *flail*", has just been rewritten to hopefully be a bit clearer. Some of it was just reorganization and putting in headers; but, uh, yeah. The content isn't a whole lot different in a general sense, but you might want to look it over.

Also, because there are section headers, the "using a *_WEBSITE override without a website" type requests just got easier to answer, since the information has it's own section, rather than being hidden towards the end of the FAQ! So you can just point them to the section of the FAQ for an answer.

As a lot of you will have seen, the terminology for the Journal Display area has been standardised within the FAQs. To keep things consistent and to avoid as much confusion as possible, your answers should also use the same terminology.

The biggest note to make is that we're no longer using the term "customization wizard". Instead, you should be using "Journal Display area" and pointing to whichever tab and section the user needs to go to.

Using "customization wizard" is still approvable, but we want everyone to move away from using that term. SHs, don't pass over anyone simply because they use "customization wizard", but please encourage the usage of the new terminology in reviews and the like.

Please let me know if you've got any questions.

Known Issues and Status

S2

*Selecting "Edit Customizations" in several reported styles (variable flow, component, unearthed, and one unknown), the customizations options that come up are for the style they had previously selected. Users have noted that clearing the cache isn't helping. Duplicated by selecting a different layout layer and clicking "Edit Customizations", options for the previous layer display. Reported to developers

*Generator Issues
-User layers that do not exist, yet only options are to "Edit Customizations" and "Remove Customizations" clicking on either simply refreshes the page and still doesn't allow for customizations - only reported when using S2 Generator. Most reports also note that they can't select a different theme layer.

-S2 Generator layout layer with Clean and Simple theme layer - has same problem as above and can't select a new theme.
-Paid users are reporting that if they attempt to switch to a paid only style, it switches them to S2 Generator. Fix not live yet

*Component not respecting "set_color_forms" for customizable forms zilla Reported to developers

*Unearthed "Link List On Recent Entries Page Only" unexpected results zilla Reported to developers

*Consider new screen-reader friendly style for addition to system styles Jesse is working on this

*Variable Flow preview image (http://www.livejournal.com/customize/preview.bml) shows Friends page rather than recent events Reported to developers

*Japanese translation layer causing incorrect tallies in comment links zilla Reported to developers

*Add confirmation of child layer deletion to S2 area (message to say deleting layout layer will delete related theme, lang, and user layers) Reported to developers


S1

*S1 custom styles that are uneditable and undeletedable fixed
(http://www.livejournal.com/community/changelog/1802365.html) - however, these still pop up, so mark with with [a] and leave for admin. Have to be fixed manually by developer.

*Error message when you attempt to create a new style that has the same name as an existing style (erinn-lastn-new) the error message just says "Error". Doesn't actually tell you what's wrong. Reported to developers



I probably missed one or twelve, but this can be edited and I think it contains the most common known issues. Everyone hug a developer today.

This is a basic guide to answering the most frequently asked types of questions in Styles. Note that every request is different, so this guide may not always apply. You should use it to help you become familiar with the category and know what is required. If you have any questions regarding this guide, please email the category admins at stylesreviews@livejournal.com.

( Guide Here )