Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Contributor Maeve Lander

    (@enigmaweb)

    It’s just a margin-bottom on <p>. Its currently set to 40px, but sounds like you might want to adjust that. You’d do it with css like this:

    #kbe_content .kbe_leftcol p {
    margin-bottom: 10px;
    }
    Thread Starter dreamware

    (@dreamware)

    Thank you for the reply, it works perfectly. Much appreciated.

    Hello. Thank you for your work! I’ve been looking for a decent Knowledgebase plugin and it seems this is it! However, this fix is not working for me… and I have another issue I will post on another thread.

    Using Ver. 1.02

    on kbe_style.css, changed

    #kbe_content .kbe_leftcol p {
        font-size: 14px;
        font-weight: normal;
        line-height: 26px;
        color: #333333;
        margin-bottom: 40px;

    to

    #kbe_content .kbe_leftcol p {
        font-size: 14px;
        font-weight: normal;
        line-height: 20px;  /*26px;*/
        color: #333333;
        margin-bottom: 16px;  /*40px;*/

    Commented the values I didn’t want and still looks the same.

    Here’s a link to a page:
    http://www.abcinfotech.com/?kbe_knowledgebase=como-borrar-estimados-en-mitchell-estimating

    This is a SPANISH website, but everything you have on your plugin is in english, too.

    Thanks!

    Plugin Contributor Maeve Lander

    (@enigmaweb)

    Instead of commenting the values, try using !important attribute instead so that it is sure to override the styles coming from the plugin

    This is a SPANISH website, but everything you have on your plugin is in english, too.

    Can you explain this statement more? I don’t understand

    Sorry for that poorly constructed sentence, it’s horrid!

    What I meant to say was, the website itself is in spanish but words like “knowledgebase” will not get translated, but I see why now. You still don’t have a spanish translator.

    Maybe I can help 🙂

    oh, and also, I am not seeing any difference using the !important attribute.

    Hi, sorry to be a pest. Nothing on this yet. !important tag on CSS won’t work.

    Plugin Contributor Maeve Lander

    (@enigmaweb)

    @h.Silva please feel free to email me privately regarding translation. I will send you the translation instructions. maeve[at]enigmaplugins.com

    Regarding the CSS issues… I can see in my element inspector that the style for line-height is coming from your theme stylesheet, line 377. I can see it is set to 26px and does not use the !important attribute. If I adjust that in my element inspector it changes the line height perfectly, so there is no reason why it should not work if you adjust it in your theme.

    I apologize for the continued harassment! I saw what the problem was, in my particular case.

    There was another kbe_style.css on the root of my theme’s directory (/public_html/wp-content/themes/attitude) along with other kbe-related files. Don’t know what they’re doing there as I installed the plugin from the WordPress installer. The spacing issue, for me, was resolved when I edited that css file.

    Removing or editing your kbe_style.css file inside your plugin directory (/public_html/wp-content/plugins/wp-knowledgebase/template) did nothing to fix the spacing issue, nor did it alter the way the content looked.

    I guess this is now resolved for me.

    Thanks.

    Plugin Contributor Maeve Lander

    (@enigmaweb)

    No worries, glad you figured it out for yourself.

    Yeah, actually the way this plugin works is that on install, it copies over these files to your theme, then the styling is controlled from there. It has to be this way due to the way it inherits styling from the active theme. So that’s how the files ended up there, and it’s why the active styles on the site are coming from those files, not the plugin. It is so that you can customise them inside the theme, and they are not overwritten on update of the plugin.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Fix Spacing Between Paragraphs In Content?’ is closed to new replies.