PHPackages benjaminmedia/wp-polylang-theme-strings - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Templating & Views](/categories/templating) 4. / 5. benjaminmedia/wp-polylang-theme-strings ActiveWordpress-plugin[Templating & Views](/categories/templating) benjaminmedia/wp-polylang-theme-strings ======================================= Polylang Theme Strings with support for Blade syntax v1.0.3(8y ago)159.9k↓16.7%10[1 issues](https://github.com/BenjaminMedia/wp-polylang-theme-strings/issues)[1 PRs](https://github.com/BenjaminMedia/wp-polylang-theme-strings/pulls)proprietaryPHP Since Jun 6Pushed 3y ago11 watchersCompare [ Source](https://github.com/BenjaminMedia/wp-polylang-theme-strings)[ Packagist](https://packagist.org/packages/benjaminmedia/wp-polylang-theme-strings)[ RSS](/packages/benjaminmedia-wp-polylang-theme-strings/feed)WikiDiscussions master Synced 1mo ago READMEChangelog (4)Dependencies (1)Versions (5)Used By (0) ``` This is a fork of the following plugin: === Polylang Theme Strings === Contributors: modeewine Donate link: http://modeewine.com/en-donation Tags: extension, polylang, multilingual, translate, translation, language, multilanguage, international, localization Requires at least: 3.8 Tested up to: 4.7 Stable tag: 3.4 License: GPL2 Automatic scanning of strings translation in the theme and registration of them in Polylang plugin. Extension for Polylang plugin. == Description == = What is «Polylang Theme Strings» and what for is it? = This plugin gives additional features to the plugin Polylang. It automatically scans all templates files and scripts of the active WP theme for available strings that can be translated. For example: * `pll__('...');` * `pll_e('...');` and adds them to the Polylang registery, after what you can manage the translation of finded strings using the administration panel. It will make your life easier for the development of multilanguage’s projects, because you will not need to enter the needed strings to translate manually – the plugin will do all the work for you. Don’t forget that in the example are described the PHP-function calls, that is why they have to be inside of PHP-tags. = How works «Polylang Theme Strings»? = You have to install the plugins «Polylang» and «Polylang Theme Strings» on your multilanguage WordPress CMS project and they must be both active. When you are in the settings of plugin (Polylang) in the tab «Strings translation» the «Polylang Theme Strings» scans automatically the active theme of your project, find all the code strings that needed to be translated, adds them to the register, displays them on that page and gives to user the ability to translate these strings. Like you can see, the «Polylang Theme Strings» is perfectly integrate with the «Polylang» plugin and works in automatically mode – it is comfortable, simple, and useful! Learn more in . == Installation == 1. Make sure you are using WordPress 3.8 or later and that your server is running PHP 5.0 or later. 1. Install multilingual plugin «Polylang». 1. Install the plugin «Polylang Theme Strings». 1. Activate both plugins via the 'Plugins' menu in WordPress administration panel. 1. Go to the languages (Polylang) settings page. 1. When you are in «Strings translation» tab of plugin settings (Polylang) – «Polylang Theme Strings» starts scan the active theme of your project automatically, it finds all the code strings that needed to be translated, adds them to the register, displays them on that page and gives to user the ability to translate these strings. 1. Learn more in . == Screenshots == 1. Screen of «Polylang» strings translate page settings and when «Polylang Theme Strings» in action. == Changelog == = 3.4 (2017-05-17) = * Fixed small bug in the search-engine of strings-translation. * Added file size limit in the theme-files search-system. = 3.3.2 (2017-01-25) = * Added compatibility with Polylang 2.1 (Thanks to Mike Ambukadze for the report). = 3.3.1 (2017-01-24) = * Fixed small bug in the theme-files search-system (Thanks to einicher). = 3.3 (2017-01-20) = * Added compatibility for strings with special characters. * Tested and optimized compatibility with WordPress 4.7. * Tested and optimized compatibility with Polylang 2. = 3.2.1 (2016-07-21) = * Fixed small bug (Thanks to Peter Bowyer). = 3.2 (2016-06-28) = * Improved search-engine of strings-translation. = 3.1 (2016-06-01) = * Improved code. * Tested and optimized compatibility with PHP 7. = 3.0 (2016-03-23) = * Added new info area in strings-translations page (Polylang settings). * Improved code and scanning strings engine. * Tested and optimized compatibility with WordPress 4.5. = 2.2.1 (2016-03-09) = * Fixed small bug in search strings-translation. = 2.2 (2016-01-25) = * Optimized compatibility with Polylang 1.8. * Improved code. = 2.1.1 (2015-12-17) = * Tested and optimized compatibility with WordPress 4.4. = 2.1 (2015-09-01) = * Absolute compatibility with WordPress 4.3. * Partially improved code. = 2.0 (2015-06-21) = * Completely remade the search strings-translations logic in the themes. * In the languages (Polylang) settings page: the search is performed on all themes in your project. * Optimized initialization strings-translations for the active theme. * Improved code. = 1.1 (2015-06-12) = * Fixed bug when removing the plugin from the admin panel. * Improved code. = 1.0 (2015-05-29) = * First release. ``` ### Health Score 37 — LowBetter than 83% of packages Maintenance19 Infrequent updates — may be unmaintained Popularity34 Limited adoption so far Community16 Small or concentrated contributor base Maturity66 Established project with proven stability Bus Factor1 Top contributor holds 50% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~81 days Total 4 Last Release 3024d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/a652ae71c3dbb5561c66c620c07b46301f1a06ac938200727a00a9bf21797731?d=identicon)[Interactives](/maintainers/Interactives) --- Top Contributors [![sulfo](https://avatars.githubusercontent.com/u/830016?v=4)](https://github.com/sulfo "sulfo (8 commits)")[![Xayer](https://avatars.githubusercontent.com/u/1837767?v=4)](https://github.com/Xayer "Xayer (8 commits)") --- Tags wordpresspluginwordpressblade ### Embed Badge ![Health badge](/badges/benjaminmedia-wp-polylang-theme-strings/health.svg) ``` [![Health](https://phpackages.com/badges/benjaminmedia-wp-polylang-theme-strings/health.svg)](https://phpackages.com/packages/benjaminmedia-wp-polylang-theme-strings) ``` ### Alternatives [log1x/sage-directives A set of Blade directives for use with Roots Sage. 297709.3k5](/packages/log1x-sage-directives)[log1x/blade-svg-sage Composer package to add support for Blade SVG by Adam Wathan to Roots Sage. 7577.3k](/packages/log1x-blade-svg-sage)[tomatophp/tomato-admin Tomato Admin Dashboard Build With FilamentPHP Theme for Laravel Splade 578.6k60](/packages/tomatophp-tomato-admin)[hexbit/sage-woocommerce Woocommerce support for sage 10 257.0k](/packages/hexbit-sage-woocommerce)[roots/wp-blade-check Simple Composer package that checks and displays an admin notice if your uncompiled Blade templates are publicly accessible. 161.1k](/packages/roots-wp-blade-check) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)