• When updating to 4.0.1 I got a ton or errors, uninstalled then fresh installed 4.0.1.

    Plugin is working as expected, however the MediaTagger options are throwing up a number of bugs, for instance when changing the “Search format -> Default search display mode” options I can only get the Tag form to display if I select both Tag cloud and Search field, no combination of those options will display only the tag form, very strange.

    Changing the “Search Format -> Visitors can switch between available search formats” option has no effect, it will display the switching options no matter what you do.

    This was previously a 5 star plugin even though it had a rough admin interface, since the update the interface is much improved, however there a number of bugs that I am still uncovering.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter ChicksAsses

    (@chicksasses)

    And what’s with all the in-line styles, the elements do not even have unique classes of ID’s, very hard to style.

    Option “Output format -> Default result display mode” also has no effect.

    Plugin Author phd38

    (@phd38)

    I fixed the search format.

    Concerning the output format, please make sure to run a new search, not just refreshing the search page – otherwise the FORM elements will be used and the default setup overwritten.

    It works fine on my side, I tested it in many different cases.

    Can you please confirm your issue and, if relevant, describe all the steps you are taking ?

    Plugin Author phd38

    (@phd38)

    Also fixed the default mode switchable for both search and result.

    Plugin Author phd38

    (@phd38)

    BTW – I am a developper, not an expert in CSS. Any help to rationalize the style coding… I take.
    I did as much as I could but focused my effort on providing a reliable code.

    Thread Starter ChicksAsses

    (@chicksasses)

    Hi Author, sorry I was a bit flustered yesterday. It really is a great plugin and everything seems to be working fine now.

    With regard to the CSS, all I would suggest is that you include class names for the objects, users would then be able to target those objects and override the default attributes.

    Seeing as your objects now have class names; you could then pull out the in-line styles and plonk them in your own css file.

    Further to that; if you then have a separate css file you could have an option in the admin to exclude the css file completely for those who wish to implement their own styles or to better allow the plugin to inherit the styles of the theme being implemented 🙂

    Again, great work!

    Plugin Author phd38

    (@phd38)

    Thanks, I will put the CSS in the list.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Bugs (FIXED, back to 5 star!)’ is closed to new replies.