Plugin Author
pepe
(@pputzer)
Which version of wp-Typography have you been using? The underlying reason for the problem is explained in the FAQ (“This plugin breaks post title links. What gives?”). Basically, some other plugin incorrectly assumes that the_title
does not contain any HMTL, instead of using the_title_attribute
or stripping the tags themselves.
While the proper solution is to fix those plugins, you can alleviate the problem by disabling adding CSS Hooks in the settings of wp-Typography (the “Wrap XY with <span class=...>
” checkboxes).
Thread Starter
Li-An
(@li-an)
OK, thanks for quick answer. I will take a look at the theme for the title problem and the eventual CSS problem in WP Plugin Info Card.
Plugin Author
pepe
(@pputzer)
@li-an, what exactly was the problem with WP Plugin Info Card?
Thread Starter
Li-An
(@li-an)
Plugin Author
pepe
(@pputzer)
The styles are not specific enough. .wp-pic .wp-pic-bar a, .wp-pic .wp-pic-bar span
should be changed to .wp-pic .wp-pic-bar > a, .wp-pic .wp-pic-bar > span
(and also the same selectors with pseudo-elements like :before
) for additional specificity.
Thread Starter
Li-An
(@li-an)
So if I change the styles.css, would it work ? I found the problem in a widget too
See https://framapic.org/pPQXe1c51FZP/yOpD2lOVXSVA.png (footer widget)
Plugin Author
pepe
(@pputzer)
@li-an: For WP Plugin Info Card, yes. The widget is a case of the problem discussed earlier (using the_title
instead of the_title_attribute
when the title is expected to not contain any HTML). These are separate issues.
Thread Starter
Li-An
(@li-an)
OK. It seems to be the old blogroll widget and I may have to find another solution.
-
This reply was modified 6 years, 5 months ago by Li-An.
Plugin Author
pepe
(@pputzer)
Alternatively, you can disable the wrapping of acronyms.
Thread Starter
Li-An
(@li-an)
Howdy, another conflict with another plugin! https://wordpress.org/plugins/code-snippets/.
It breaks the rendering of the code lines. Well, I have to accept your plugin is not compatible with my use of WP 🙂
Plugin Author
pepe
(@pputzer)
@li-an, maybe I’m misreading this, but have you even looked at the FAQ and the available settings? wp-Typography is very customizable and there are ways to disable features that don’t work for your setup (like adding CSS classes to acronyms, numbers etc.) and to avoid processing certain elements, identified either by ID, class or tag name.
There may be situations where two plugins are simply incompatible without the cause being a bug in either of the plugins, but in my experience that is pretty rare. I’m willing to help your resolve apparent incompatibilities by determining the root cause (and fix it if it’s a bug in wp-Typography), but I need detailed description of the expected and actual behavior (with screenshots or access to a live site to look at HTML code and styles). Also, it would be best if we could talk about each separate issue in thread of its own.
Thread Starter
Li-An
(@li-an)
You are right. Sorry for the confusion and the time I stole to you for help. But I have no time right now to work on this. It’s just easier not to use your plugin on this site 🙂
Plugin Author
pepe
(@pputzer)
I am sorry to hear that, @li-an. Disabling the CSS Hooks injection via the settings would not take more than a few seconds, though, and fix most of the problems you described above. (Not sure about the Code Snippets plugin, since you did not tell us any symptoms for that.)
-
This reply was modified 6 years, 5 months ago by pepe.
Thread Starter
Li-An
(@li-an)
Plugin Author
pepe
(@pputzer)
Is that a full view of the “Code Snippet” custom post type?