How to change bullet in widget to ref #

Hi believerinsight,

That sounds like a theme CSS issue. I’m guessing your theme’s stylesheet includes some variation of the following rule:

ol {
    list-style-type: disc;
}

What theme are you using? I might be able to point you to a more specific fix if it is a publicly available theme (or if you can link to your site).

HI Setzer,

I’m using Theme twenty ten and the site is:

https://believerinsight.com/

Even in the settings preview screen it shows the bullets.

Thank you for being so quick to reply.

believerinsight,

That’s strange. In that case, it must not be theme-related. No idea why the note numeral would display as a bullet even in the settings preview field. Do <ol> HTML tags (ordered lists) always show up like this for you, or just with Side Matter?

Think this is an IE-specific issue with the li type attribute. This will be fixed in the next plugin release.

Thank you for the update. Some small issues; using number format when double digit the first part of the number is missing – this happens both in Firefox and IE, other issue is the order start over at 13 but shows the correct number or letter on the article – only occurs in IE. Thank you again for the update.

https://believerinsight.com/acts-1717-out-of-control/

believerinsight,

This is a CSS issue and can be fixed. The sidenote list needs a wider left margin in order to display the full double-digit numerals. Try adding the following custom CSS rule to your site:

ol.side-matter-list {
    margin-left: 3em;
}

If you’re not sure how to add that to your site, I suggest installing a custom user CSS plugin (like the Custom CSS module included with Jetpack) and pasting the above code into the custom CSS field.

Thank you, I thought it was something with CSS.

Any ideas with the numbering in the widget?

Again thank you for the help love the plugin.

I believe these are the same issue. On the page you linked, the notes appear to reset after 13 because the first digit of 14, 15, etc. is getting cut off. The CSS above should fix this as well.