Quick Localisation allows site admins to patch WordPress translations of any theme and any plugin without leaving the control panel
The bigger the database, the more parsing the plugin has to perform, the higher the load. The relationship is exponential. Though we tested it with thousand words and the extra load was minimal.
WordPress activates plugins alphabetically or in the order provided by the file system. Having said this, if one of these earlier plugins localises its strings directly on the initialisation, Quick Localisation won't be able to catch those.
A known way around it is as follows:
<?php include_once ABSPATH . "wp-content/plugins/quick-localization/index.php"; ?>
Requires: 3.0.0 or higher
Compatible up to: 3.3.2
Last Updated: 2014-8-2
Active Installs: 2,000+
0 of 2 support threads in the last two months have been resolved.
Got something to say? Need help?