WordPress.org

Support

Support » Plugins and Hacks » 2 bugs easy to solve (3.3.13)

2 bugs easy to solve (3.3.13)

  • Hello

    There is two minor bugs :

    The custom CSS is asking for h6, but the code delivers h5

    Also, the custom CSS is showing before the css file, so I have to use !important for some css, and I don’t want to

    By the way, I think upPrev menu should be in settings.

    And 2 feature request…
    – Having a way to add a custom title, if we don’t display the header
    – Having the possibility to customize the div template. At least, possibility to have the h5 before the image, so the title could be the box width long

    Thx, this is a great plugin !

    http://wordpress.org/extend/plugins/upprev/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Marcin Pietrzak
    Participant

    @iworks

    The custom CSS is asking for h6, but the code delivers h5

    h6 is used for displaing tags/category.

    Also, the custom CSS is showing before the css file, so I have to use !important for some css, and I don’t want to

    Your theme have a little bug. Function wp_header must by the last before </head> tag. In Your theme is before theme style.css. Check it please.

    Having a way to add a custom title, if we don’t display the header

    You can use iworks_upprev_box_before action to put anything what You want to put.

    Having the possibility to customize the div template. At least, possibility to have the h5 before the image, so the title could be the box width long

    At last You can use iworks_upprev_box_item filter to change anything in each upPrev item.

    1 : Ok, so h5 should be from my style.css

    2 : I checked before, and my header is correct :
    <head>
    <title>…</title>
    <link rel=”stylesheet” href=”<?php bloginfo(‘stylesheet_url’); ?>” type=”text/css” media=”screen”/>
    … (other meta and header stuff) …
    <?php wp_head(); ?>
    </head>

    3 : Ok, will try

    4 : ok, will try this also

    thx

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘2 bugs easy to solve (3.3.13)’ is closed to new replies.