CSS error: .dpsp-network-icon-inner >svg{fill:#1e73be}

Hey @a4jpcom,

Thanks so much for bringing this to our attention! I was able to replicate a similar experience on my end. I went ahead and forwarded this over to our plugin engineers to have them look at correcting this in a future release of Grow Social.

Can you please tell me which folder and file the error is in so I can directly fix it? Can you also give the plugin a matching folder name to make it easier to find? There isn’t a folder named grow-social or mediavine in the plugins folder.

Hey @a4jpcom,

It’s possible that the error is in social-pug/inc/class-custom-color.php however our engineers are still investigating so I cannot say for certain what might be wrong as of yet. This particular style is something that’s dynamically added to the internal styles based upon the style of buttons chosen.

As far as the name of the main plugin folder, you should see it as social-pug. This is something that cannot be changed and was the original name of the plugin before Mediavine took over development.

• This reply was modified 3 years, 1 month ago by mediavine.

It looks like they edited a file using text software and it converted > to &gt ; (minus the extra space) which is needed. A super simple thing but as you have so many files I didn’t want to go through and find it. I tried but as you had a super strange folder name for the plugin folder I have to download everything from a client’s server and find it. Then when I saw the amount of files in the folder I just gave up on finding the bug. Please change the folder name so it matches your plugin name. It makes it difficult for everyone if you use a name that doesn’t match the plugin name.

• This reply was modified 3 years, 1 month ago by a4jp.

I don’t think the problem is in that file (social-pug\inc\class-custom-color.php). Just do a search for dpsp-network-icon-inner and you should be able to see all those lines of code are perfect. Is that the only place you have dpsp-network-icon-inner?

Hey @a4jpcom

Thanks for giving that a try. Our engineers took a deeper look into it and it looks like this is occurring because of some escaped output coming from WordPress’ linting requirements. The escaping causes the child selectors here to be converted from ‘>’ over to ‘>’ which breaks the CSS selector.

It looks like we are planning to get this fixed in a future release but we don’t have an ETA on this or further information to share quite yet.

As for changing the main folder, that’s not something we’re able to do as I mentioned above as this was the original name of the plugin. It could be possible in the future to change that but as of now with WordPress it’s something we cannot change. There’s some information about that you can find here if you’re interested!