ldevore849

Thanks for responding at last. In the meantime, I tried creating another Social Profile and was able to change that person to Administrator and my own profile to User. It worked, but there was NO documentation to suggest trying that, which would have solved the problem immediately. It was not an intuitive or obvious solution. You might consider adding something like that in the Initial Setup instructions.

Thank you for the response. Unfortunately that is a Premium extension, and my budget is already over limit.

May I please have a reply?

Yes, the Console script result was whatever I typed into the bar. So if I typed Muh, the result of  carbon_get_theme_option('oacs_spl_like_text'); was "Muh" . If I typed Like, the result was "Like" . 

I assume that means the value does exist in the database, correct?

I can see that as well, but I obviously can’t go into each page’s html and add the text. What do you propose as a solution? A custom CSS fix?

Even though I marked this resolved on your part, I found out something from my theme designer that you should know. In researching why their theme had a conflict with your plugin, they discovered the following:

The plugin authors have made a small mistake when they apply their “icomoon” font to their icon elements. Instead of targeting their specifics icons, they target all icon classes on the website. This will conflict with any other plugins or themes that are modifying general icons as well. This is not the correct implementation for a plugin with its own icons.

Additionally, they are targeting the parent element instead of the ::before element that contains the icon.

“The plugin authors of Solid Post Likes should consider updating their CSS to properly target only their own icon elements, and correctly target the ::before element that contains the icon.

For example, by updating their icon selects to include their plugin class prefix:

.oacs-spl-icon[class^=”icon-“]::before, .oacs-spl-icon[class*=” icon-“]::before {
font-family: “icomoon” !important;
}

This will prevent conflicts with any other theme or plugin that modify general icon classes.

That’s the end of their message to me. When I added that code to my site’s custom CSS, the heart symbol immediately displayed, so I guess their advice worked. I wanted you to know.

• This reply was modified 1 year, 8 months ago by ldevore849.

You said above:

Something on your site is commenting out the icomoon font that is required to display the icons: https://share.zight.com/9ZuJBQk8
I think this is disabling the icon display.

I found the path to that file but I don’t see anything in it that would disable the icon. As far as I can tell, it’s your php file, isn’t it? I do have 3 warnings in it from my file editor that may or may not matter:

Line 10: font-display: block is an unknown property
Line 13: [class^="icon-"], [class*=" icon-"]
Attribute selectors with ^= are known to be real slow!
Attribute selectors with *= are known to be real slow!
Unqualified attribute selectors are known to be slow.
Line 16: speak: never
Expected (normal | none | spell-out | inherit) but found ‘never’.

Is there anything specific in that file that I am missing? Please help me solve this problem. Otherwise, I’ll have to use another, less attractive plugin. Thank you.