More styles for setting button colours

Hi,

Have you checked the following tweaks css-tweaks-for-the-simple-download-monitor-plugin?

Thank you

It does help, but:

.my-button, .sdm_download {
	background: #248ed0;
	color: #fff;
	border: solid 1px;
	border-color: inherit;
	font-size: inherit;
	text-decoration: none;	
}

I would prefer it if I did not have to use !important everywhere. Is this not possible?

I think it would be much better if you add a n option for us to specify the name of our own button class. Then in your plugin you would position it such so that it takes precedence that any other styles. That is how the other plugins that I am using work.

Hi,

I think it would be much better if you add a n option for us to specify the name of our own button class.

I have submitted a message to the developers to investigate further your request.

Thank you

Thank you. ??

Any ETA on updating this at all?

Thanks.

Hi

Please note that I have still not been able to workout a suitable CSS styling to make the button match the buttons on my site:

https://www.publictalksoftware.co.uk/sdm_downloads/msa/

I don’t want to use !important if I can help it. There should be a way of applying CSS without such a forced override to style the buttons.

Thank you.

This is not a trivial change unfortunately. I can’t just go and make a significant change like this which will impact tens of thousands of other installs where the users are perfectly happy.

Ignore this message – double submit. See next reply. Thanks.

• This reply was modified 4 years, 8 months ago by Chuckie.

Hi

Thanks for the reply. Can’t you add a new check box setting (default unchecked):

“Do not colour the button”

? This would not affect other users. It would stop the HTML from including this second class. Or, add Custom to the end of the colour choices where we can specify a custom colour as a # constant.

Either of these don’t affect other users. The latter would probably be more beneficial.

Also, I don’t see why you can’t add a custom class edit box. A user would have to type the class in. If they don’t it carries on like it does now. If they do, it is stitched onto the end of the class list in the HTML and just takes precedence.

None of my suggestions affect any user, yet make your code more flexible. Particularly the custom colour / custom class ideas. They don’t break the current mechanics in any way. They extend them: custom colour, custom class stitched onto end of classes in the HTML.

I would also like this option! In my theme, none of the colors offered work. Also I want no shadows. I’m using white at the moment and I keep getting asked to make it a color that pops by other collaborators.