Hey folks, I love what you’ve done with the CSS plugin — super clean!
We have our own “builder” plugin that I’d love to showcase so-css with, but we’re running into an issue where it’s not picking up on ID’s to edit. It works with classes, which is great, but that means it makes a global change to our builder widgets — where I’m looking to make it to just single widgets based on ID.
Is that anywhere on the roadmap or do you know of a workaround?
so-css question
This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.
Hi Matt
The plugin already allows you to select by ID. If you open the visual inspector and click on an element with an ID the code window below lists the element that are included in the selection, including ID tags. You can click on any of these and then use the tools to the left to affect changes.
Hope this helps
Magus
Hi Magus,
Thanks for the quick reply!
Here’s a screenshot: https://www.evernote.com/l/AAkaQ5Gq0FhNTp9Wak9HzXnVI8diadU2l0Q
We can’t seem to click to the ID with your inspector, as shown in the browser inspector. We think it’s selecting the right element based on the classes your css editor shows. I’m wondering if it’s because there’s not enough padding around the element?
Hi Matt
Would you mind telling me what version of the plugin you are using and what browser your screenshot is from.
Thanks
Magus
That’s version 1.0.1 of the plugin and that screenshot was Safari.
I did try in Chrome with the same result.
Hi Matt Medeiros
You should be seeing scroll bars on the lower inspector windows.
http://gyazo.com/bf3eea49f1a1bee94ea0ebaeb3a0239a
I’ve logged this as a potential bug in our issue tracker. We’ll investigate this as soon as possible and try come up with a fix.
Magus
Hi Magus
Just wanted to check in on this. Perhaps it’s our plugin? Do you track the bugs on github or somewhere else so I can follow?
Hi Matt
We track bugs on another site unfortunately but I can link you to the github page
https://github.com/siteorigin/so-css
Magus
Okay, thanks.
We’ve been recommending our customers use so-css, but they can’t target our individual widgets for whatever reason.
Hi Matt
It is possible it is something in the way your plugin handles CSS and ID’s. Could you check for any javascript errors when using the live editor
https://codex.wordpress.org/Using_Your_Browser_to_Diagnose_JavaScript_Errors#Step_3:_Diagnosis
Magus
No console warnings. I’m wondering if there’s a max in ID/Class names it can pick up on?
https://www.evernote.com/shard/s9/sh/10a1ca13-55e1-4609-8911-f513a59a09a6/f19f0698440ca882
Hi Matt
Not as far as I know. Ill pass this along to Greg, if he has time, maybe he can shed some light on it.
Magus
That would be great. We’re going to dig deeper too on our end.
Hi Matt
It’s awesome that you’re recommending SiteOrigin CSS to your customers. Very happy about that. I’d love to try make the plugin better for them.
Would it be possible for you to send me a copy of Conductor to test out what’s going on? Right Now SiteOrigin CSS just scans all CSS on the page and adds any present selectors to the inspector. If some aren’t showing up, then that’s a potential issue. I’ll try figure out why.
If you don’t mind sending a copy to [email protected], along with some very basic setup steps, I’ll start digging.