JKL Unit Converter

As a general rule, it is always best to keep your WordPress installation and all Themes and Plugins fully updated in order to avoid problems with this or any other Themees or Plugins. I regularly update my site and test my Plugins and Themes with the latest version of WordPress.

Each element within the conversion_form contains its own unique CSS identifier, allowing you to hook into those in your own Custom CSS stylesheet. To easily find out which classes control which elements, simply open your site in a modern browser (Google Chrome, Firefox, Opera, or Internet Explorer 9 or later) and right-click on the element you wish to style. Then find Inspect in the pop-up contextual menu.

The unit lists are dynamically controlled by JavaScript (which loads at the end of the page load). So, if your site has large images or other things that cause the page to load more slowly than usual, this will also cause the script to load later and delay the appearance of unit options in the select dropdowns.

Simple: it's best to not allow TWO separate instances of the Unit Converter to run on the same page. It's overkill. You only need one per page. The same is true for multiple shortcodes on one page. Only ONE instance of the Unit Converter should be used on any one Page.

There is currently no AJAX functionality implemented by this plugin to maintain the state of the Page and dynamically calculate and show the answer without a reload. This is a planned feature for an upcoming release.

Currently, the plugin doesn't remember your page position when you submit the conversion form, so because the form completely reloads the page, it thinks this is the first time you're loading, so it will load to the top of the page. Remembering page position is a planned upcoming feature, but it will be unnecessary if/when I implement dynamic calculations with AJAX.

For the most part, it depends on how your Theme styles those elements. I did my best to style the form very simply and plainly, but some elements may appear out of place in your installation due to your Theme's default styles. In order to fix this, add some Custom CSS (preferrably using Jetpack's Custom CSS feature, or another that doesn't require modifying the Theme or Plugin files). See the first question above for more info on how to do create Custom CSS for the plugin.

Sure, I'm always open to suggestions. Let me know what you're looking for. Feel free to open a GitHub Issue on the plugin repository to let me know the specific features or problems you're having.