• Resolved martin9870

    (@martin9870)


    After updating to 3,4 “Read more” text has wrong format and after click it gets dark background so it is unreadable. It looks very bad. Something wrong is in CSS so I was forced to downgrade! I hope there will be a new version soon.

    • This topic was modified 1 month ago by martin9870.
Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author George Gkouvousis

    (@gkouvousisg)

    Hello Martin.

    While this sounds more like a CSS conflict with the theme or other plugins, I was wondering if you can use the latest version of the code and report back if that solved it? V4.0.0 is introduced.

    Thread Starter martin9870

    (@martin9870)

    Hi, unfortunately it didn’t help. I have installed 4.0.0 version and text is still badly formated. You can check it live here: https://www.femdom365.net

    Thank you for help

    Plugin Author George Gkouvousis

    (@gkouvousisg)

    Please dont publicly share links or warn about NSFW ones.

    The background color (black) that messes your appearance is not coming from the plugin – its rendered through litespeed cache: https://dl.dropboxusercontent.com/scl/fi/hpabskp3cpxoicc2omt6k/chrome_k4rhDGtJqY.png?rlkey=3zeeejz3hcmqe49yyiqk2hshy&dl=0

    Thread Starter martin9870

    (@martin9870)

    Hi, but how I can solve it? It worked fine until latest updates – so this problem was caused by your plugin somehow. Do you think that I am only one who use Litespeed cache? I’m sure this problem affects many users. BTW, problem is also with the red text itself – it is very bold and you can see thar “R” letter is VERY small. It looks like it uses some uncomaptible text font..

    Plugin Author George Gkouvousis

    (@gkouvousisg)

    Hi Martin,

    I never mentioned that you are the only person on the planet using LiteSpeed Cache, so the rhetorical question is unnecessary. What is necessary is technical evidence before concluding that “this problem was caused by your plugin somehow”.

    To be clear and factual:

    1. There have been no CSS changes in the plugin that would introduce the behavior you describe. You are free to diff previous and current versions and verify this yourself.
    2. The black background you are seeing is not rendered by the plugin, it is injected at runtime by LiteSpeed Cache, as already demonstrated.
    3. A font being bold or a glyph like the “R” appearing smaller is a classic sign of theme or font override, not a plugin that does not define fonts at all.

    At this point, blaming the plugin without any reproducible evidence is speculation, not debugging. I have already spent time inspecting your site, despite the plugin being free and support limited in actions that do not include personalized debugging.

    To move forward pragmatically instead of guessing, please do the following:

    • Switch temporarily to a default WordPress theme.
    • Clear all cache layers, including litespeed cache.
    • Confirm whether the issue persists.

    This will conclusively determine whether the problem is related to the plugin or to your theme or cache stack. Until this basic isolation step is done, there is no technical basis to claim the plugin is the cause.

    I am happy to continue helping, but only on the basis of facts, not assumptions. Debugging works best that way, magic rarely helps.

    Looking forward to your findings.

    Thread Starter martin9870

    (@martin9870)

    Hmm, thank you for reply. I am not technician or programmer. But it is easy logic – version 3.3 worked perfectly with my current theme, other plugins etc. BUT after upgrading to a new version it caused this graphic bug. So it is for sure that there is something problematic in a new version of the plugin that caused this problem. BTW in plugin directory (4.4) is CSS directory (with admin.css file) and it wasn’t in older version. I wouldn’t be surprised if this file was the cause of this problem šŸ™‚ I am going to downgrade to older version and wait for new and upgraded version of the plugin.

    After downgrade it works fine – you can check it. Have a nice day.

    • This reply was modified 1 month ago by martin9870.
    Plugin Author George Gkouvousis

    (@gkouvousisg)

    Hi Martin,

    Just to clarify something very basic, because there seems to be confusion.

    The file you are referring to, admin.css, is loaded exclusively in the WordPress admin area (backend). It is not enqueued on the frontend, not conditionally, not accidentally, not magically. So it cannot affect what visitors see on your website.

    Reporting a frontend visual issue and attributing it to an admin-only stylesheet is technically impossible.

    Additionally:

    • The plugin does not define fonts.
    • The plugin does not force font weights.
    • The plugin does not apply background colors to frontend content.

    Bold text, broken glyphs like the “R”, and dark backgrounds are all classic results of theme CSS, font-face overrides, or cache/minification layers, not this plugin.

    At this point, continuing to insist that “it must be the plugin somehow” without isolating the variables is not troubleshooting, it is guessing.

    If you are not interested in following the simple and standard debugging steps I shared in my previous reply, thats ok, however, a future version wont solve any issue related to a factor other than our plugin.

    Have a great weekend ahead.

    Thread Starter martin9870

    (@martin9870)

    Dou you have knowledge of what plugin directory contains? There is another NEW file in JS directory named “frontend.js”. This file also has nothing to do with the frontend? THIS is cause of this problem in my opinion….

Viewing 8 replies - 1 through 8 (of 8 total)

You must be logged in to reply to this topic.