Icons

This nice plugin is sadly becoming a real mess. Let’s hope that Canadian https://www.sujinc.com will hear us and take some time to launch a second life for this plugin.

Here is a piece of code I added for an inhanced interface – even if I wasn’t able to remove the vertical useless lines. If someone can show me the right selector..

/*** PLUGIN MANAGER > UI fix + custom ***/

.plugins .plugin-title .dashicons:before {
padding: 4px;
background-color: #e4e9f6;
border-radius: 4px;
font-size: 20px;
color: #b4b7e9;
}
.plugin-title .dashicons {
width: 30px!important;
height: 30px!important;
margin-top: 10px !important;
}

I’ve finally gotten back to this. The vertical lines (pipes) are in the HTML, though I couldn’t actually find them to remove them. No matter, I’ve managed to mostly restore this to the way I remember it being. This version places the icons between the pipes, so it does the trick for me:

.activate, .deactivate {
	float: left;
	margin-left: 0;
}

.delete {
	float: left;
	margin-left: 2px;
	margin-right: 3px;
}

.group, .lock, .hide {
	float: left;
	margin-left: 4px;
	margin-right: 0;
}

.plugins .plugin-title .dashicons:before {
	padding: 4px;
	background-color: #e4e9f6;
	border-radius: 4px;
	font-size: 17px;
	color: #b4b7e9;
}

.plugin-title .dashicons {
	width: 20px !important;
	height: 20px !important;
	margin-top: 0 !important;
	padding-right: 10px !important;
}

• This reply was modified 6 years, 10 months ago by dycweb.

The only time it doesn’t work is for plugins that add extra functions aside from activate and deactivate. I have a few that add functions like custom menu, settings, and other specific function names. In those cases, the classes for the extra functions tend to be generically named 0 and 1. When I try to add styles for them similar to activate, deactivate or delete, it scrambles everything. I don’t have much time to mess with this so, for now, I’m happy with all but 2 or 3 plugins appearing the way they should.

• This reply was modified 6 years, 10 months ago by dycweb.
• This reply was modified 6 years, 10 months ago by dycweb. Reason: clarity

It is fixed on the version 6.0.2. Sorry for late ??