[personal profile] swaldman
Hi Styles people :-)

I've just finished working on Bug 1723 and, pending reviews etc, it will probably appear in a code push soon. It makes a couple of changes to how things in the TagDetails class behave, so I thought I should do a post here and warn you.

Firstly: The use_count variable currently gives the total number of posts on which a tag is used. This will change to the number of posts visible to the current user on which the tag is used. This fixes a privacy issue, whereby somebody without access could see how often the journal owner wrote about that tag in locked posts. Note that for performance reasons, the new value will sometimes be an approximation. It may be accurate or it may underestimate. It should never overestimate.

Secondly: There is a data structure called security_counts, which is not used by any of the DW official styles, and which I suspect nobody actually used because half of it didn't work. Here's how it will work in future:
  • security_counts{"public"} will give the number of public posts on which the tag is used.

  • security_counts{"protected"} will give the number of friends-locked (members-only for comms) posts on which the tag is used, if the current user has access to those posts. If not, it will be undefined.

  • security_counts{"private"} will give the number of private (admin-only for comms) posts on which the tag is used, if the current user has access to those posts. If not, it will be undefined.

  • EDIT TO ADD: security_counts{"group"} will give the number of posts on which the tag is used that are locked to access groups (also called access filters). This will only be visible to the journal owner (admin for comms). If the current user is no the journal owner, it will be undefined.

Note that security_counts{"group"}, which used to exist but frequently gave the wrong value, is deprecated. There is no way to provide this info for access filter groups without thrashing the database.

Also, security_counts{"friends"} is deprecated because it never worked anyway! It has been replaced by security_counts{"protected"}.

I hope that all makes sense; please ask questions if you have them.

EDIT: I realised that we can do security_counts{"group"} properly for journal owners, because we can assume that they can see all groups. There's still no way to work it out for other users without database-thrashing. Unlike before, for those who can see it it will now give the right number ;-)

foxfirefey: Dreamwidth: social content with dimension. (dreamwidth)
[personal profile] foxfirefey
We have a brand new layout going out with the latest code push: Five AM by [personal profile] winterfish! Check it out. Theme makers will be sure to be making more themes for it soon!

The code push also brought out 73 other new themes, besides Five AM's Early Edition. They're all in the featured area of the Journal Selection Area.

I've also updated my prototype style browser to have all the layouts and themes--and it has a stats page, if you're curious.
foxfirefey: Dreamwidth: social content with dimension. (dreamwidth)
[personal profile] foxfirefey

There are a couple of important style happenings that could affect people who make their own custom styles; remember that if you end up having problems with your style, you are always free to ask for help here or in [community profile] style_system. We are more than happy to assist you!

External Stylesheets

So, we've flipped the property to make style sheets load externally by default (external_stylesheet). This is actually going to be great for styles--it means that instead of putting the CSS in the HTML page on every single page load, increasing load times, browsers will be able to cache the externally linked CSS! It does mean, though, that if you have manually overwritten the print_default_stylesheet function, you might end up with some problems--to solve them, take away any <style> tags you may be printing out, as the system will add any necessary ones inline.

Comment titles now use heading elements

Comment titles now use heading elements--this allows people with screenreaders to jump by a certain element level, which increases accessibility. We've updated the CSS for official styles for this (let us know if anyone finds anything amiss), but you might have to add extra CSS for any custom styles.

And now, on to the fun stuff!

There are a LOT of new themes, thanks to [personal profile] timeasmymeasure, [personal profile] dancing_serpent, [personal profile] busaikko, and [personal profile] sarken. Layouts with new color themes include: Drifting, Bases, Negatives, Skittlish Dreams, Nouveau Oleanders, Modular, Blanket, and Brittle. Other fun changes include:

  • Sunday morning now has one column and two-columns right layouts. ([personal profile] ninetydegrees)
  • Transmogrified now has a two-columns-left layout. ([personal profile] ninetydegrees)
  • More official styles support the placement of icons to the right or left side of entries now. ([personal profile] ninetydegrees)
  • More official styles also support placing metadata at the top or bottom of the entry. ([personal profile] ninetydegrees)
  • There's a new journal search module! If you're a paid user (or can search the journal you are viewing), and are viewing a style that includes the search module, you can use it to search the journal! ([personal profile] foxfirefey, [personal profile] ninetydegrees, [personal profile] fu)
  • You can now use community icons instead of the poster's icon on your reading page for community posts ([personal profile] kareila and [personal profile] fu)
Other changes and fixes )

This was a huge update, so if I missed anything or missed giving credit, please let me know!


Dreamwidth Styles

Resources for creating layouts

August 2014

17 181920212223


RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Oct. 18th, 2017 12:47 pm
Powered by Dreamwidth Studios