Userpic Links {bullet points solved}

[jhumor]

In one of my communities, I'm using a slightly modded Abstractia.

I'd like to be able to change the userpic so that it will ALWAYS display Keyword order|View All.
Mostly I'm kind of tired on waiting for DW to do anything about this for all style sheets and I'm wondering if there's a way to code it using Custom CSS.

After searching through this comm, I came across some code that looked like it worked for CSS2, but probably won't work for Abstractia?

Anyway, so I tried changing it to this (and several derivatives of it). So, I'm just guessing this isn't the way to go about it. (I wish I understood the different CSS better.)

.entry .userpic { url:("http://$e.poster.username""" + """.dreamwidth.org/icons?sortorder=keyword&view=all”) }

Any help you could grant would be great, because I have this comm and several journals that I'd like to update to forcing the keyword order and view all options.

ETA: perhaps easier? Is there a way to change the bullet point image? I know I can do it by finding a URL and doing 'background img', but I'd rather do it natively via text. (IE: currently on the style they are squares (■) I want them to be one of my choice.)

SOLUTION: Use this code:
BODY { ul { list-style: XXX; } ul ul { list-style: XXX; } }

Where XXX are options from a CSS List Style website.


Thanks in advanced.

Comments

[marahmarie]

That's s2 in CSS syntax. You'd have to go to our compiler and try your code there, but I'm not sure what your code should include besides what you have so far.

On the bullet points, are you saying you want them as part of your inline text? On DW we're kinda limited on what we can do with that to, if I recall correctly, UTF-8 characters. I'm not even sure what exactly that allows you to use, but that would work only on your entry lists. The sidebar bullet points (assuming your style contains any) are hard-coded, so you'd have to use CSS or s2 (or even a combination of both; however you most prefer to approach it) to change those.

Also, I need to come with a disclaimer when I jump in on questions like yours (an icon, perhaps?) that warns people I don't know how to write s2. I can occasionally toy with it depending on what it does or what I wish it would do, but as far as coding what you want, I can't do that. I do wish it was as easy as using a set = command, as those involve almost no coding - something like:

set text_module_customtext_content = "<a href="";

...which is code I once used in an old version of my s2, but I'm not sure if any version of that (or what exact version) would work to change your icon page to display the keyword order view as the default.

[marahmarie]

I'm sorry I wasn't more clear. I meant what you put in the textarea is in CSS syntax, but the code between the brackets is actually written in s2 syntax, so that's why it won't compile! s2 inserted into a CSS command won't be recognized by our compiler. You'd have to write an actual function (I believe that's what it's called) to pull off what you're after.

We have an s2 Cookbook to help those curious about s2 to get started. Some people can just look at the examples found there and figure out how to write the s2 they want. I've never been quite that good at it, but I've seen plenty of people who seem to be.

The bullet point issue seems to be a limitation of CSS (only certain bullets are pre-coded).

Yes, they're hardcoded via more s2, so without re-writing DW's code for that it's hard to work around. We can't just insert bullet point text into the Wizard since it has no function to allow that.

As far as changing bullet points go, you can change both list bullets in your entries and the ones in say, your sidebar, via CSS (the former would require using inline HTML in your entry lists to target with CSS; the latter, just targeting the existing sidebar module-list HTML via CSS).

I'm glad you found something you can live with right now as far as the bullet points go. I get into similar places myself, where I have sort of what I want but not quite, which is why I rewrite my CSS so much, because eventually I find a better solution, so I'm always kind of upgrading as I go along. :)