Support » Plugin: Kontrol Developer Kit » in css conflict with wp?

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Kontrolwp

    (@kontrolwp)

    Hey Zebrastribe,

    Good pick up mate, didn’t notice that. Looks like it was caused by mooRainbow (colour picker css) overwriting the label font with monotype. I’ve pushed a silent update to the WordPress repository, so if you download the plugin again and overwrite your current version, that should fix it and also fix it for any future downloads. I’ll rollout this change to anyone who’s already downloaded Kontrol in the next minor version update which shouldn’t be far off.

    Thanks!
    Dave.

    Hey Dave
    Cool. Now it is fixed, thanks for a great plugin.

    An other question I have is why can the user double click on the field name inside custom post a get a dialog message “custom key field” where a value can be type in but not saved…
    see here

    Plugin Author Kontrolwp

    (@kontrolwp)

    This was a developer shortcut that I added in 1.0.3 to allow developers a quick way to access a custom fields key. When developing the front end and using the get_cf() command to retrieve a custom fields value, it provides a quick way for the developer to find and copy a fields key, rather than opening Kontrol back up, going to the custom fields section and finding the group that contains the field key you need.

    It should be hidden to most regular users as I can’t imagine many would double click the title for a custom field 🙂

    Hope that explains it!
    Dave.

    Okay. Thanks for the information. Do you have I wishlist or a roadmap for the next versions? and can I hide admin menu items based on “Roles”?

    Plugin Author Kontrolwp

    (@kontrolwp)

    Hey zebrastribe,

    At the moment I you can restrict access to menu items by setting their permissions, but I don’t believe you can hide the item. I’ll look at this possibility.

    As for the wishlist/roadmap. Since 1.0.3 has introduced internationalisation support for the whole plugin, I’d like to see it get fully translated to as many languages as possible. It now has partial support for over 20 languages, but I’d really like to see it get translated for a lot more people who don’t use English as a native language. Danish and Portuguese full translations shouldn’t be to far off!

    Other than that, I’m always receiving requests for new features and I generally keep a list of the viable ones. One of the next modules I’d like to introduce is a Form Manager, I feel the current ones for WordPress can be improved a lot, so I’d like to add a complete module for creating/storing/exporting forms. Not sure if it will make the next major release though.

    Cheers,
    Dave.

    Sounds good with a form Manager. I am using “gravity forms” but some functionality could be really nice f.ex.: better integration with custom posts/fields, prepopulated and repeatetive fields. They have a good nofication setup included merge tags…

    Keep up the good work!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘in css conflict with wp?’ is closed to new replies.