liddweaver

The best way to remove the word ‘amortized’ from the text strings would be to add a filter on rmc_localization to make the modifications on the script localization.

Barring writing any code, you can edit the strings directly in includes > function-rmc-localization.php lines 56 through 83 – keeping in mind that you will lose these changes if you update the plugin.

There is currently no way to append text to the results. For this, you will need to hack the JavaScript file js > lidd-mc.js. At about line 382, just before // Add the summary to the page, you can concatenate your HTML to the results text:

summary += '<p>Your text string</p>';

• This reply was modified 8 years, 6 months ago by liddweaver.

I have added this as a feature request, although I am not currently working on new features. If this is a must have for you, you can create it with the pro version.

At present, this is beyond the limitations of the plugin. However, you can hack the jQuery file lidd-ms.js to put the results wherever you want.

There are two methods for translating the time period strings, like yearly, monthly, weekly, etc.

1. There is a Spanish translation file included with the plugin. Setting your site’s language to Spanish should automatically use the Spanish translation file. Failing that, you can create your own .mo file for the language you want based on the included .po file.

2. Add a filter callback function to run on the rmc_localization filter. This will allow you to modify all the remaining strings to your liking. Here’s some example code to get you started – copy and paste into your theme’s functions.php.

function custom_rmc_localization( $strings ) {

    // Modify strings in the array
    $strings['yearly'] = 'anual';
    $strings['monthly'] = 'mensual';

    return $strings;
}
add_filter('rmc_localization', 'custom_rmc_localization');

You’re theme is probably providing default styling for the select box. Try adjusting the CSS options via the plugin settings page: Settings > Resp Mortgage Calculator.

Fixed in v2.3.3

I will be maintaining compatability with new WP releases for the foreseeable future. You can log issues here and usually get a response within a few days.