SimplePoTranslate

সলনি-পঞ্জী

1.0.6

• New readme FAQ on translating the plugin’s interface — points users to the official translate.wordpress.org project for community translations and shows how to use the plugin’s own Auto Translate flow on its POT file as a fallback while their locale is still being translated.
• Suppressed a Cannot modify header information PHP warning that could appear in debug.log on sites running with WP_DEBUG enabled. The plugin’s admin pages now check headers_sent() before emitting the LiteSpeed cache-bypass header, so the header is sent when possible and quietly skipped when output has already begun (no functional impact either way).

1.0.5

• Fixed a silent-failure case where a translation job that completed on the API side never had its .po/.mo written into the plugin uploads directory — e.g. after a PHP timeout, memory-limit exhaustion during ZIP extraction, or the browser tab being closed mid-import. Previously the affected job became an invisible “zombie” (status marked completed but no file on disk, hidden from the Translations page). v1.0.5 keeps the download URL on the row until the write is confirmed, wraps the entire import pipeline in try/catch so any fatal surfaces as a Failed row with an error message, and uses a transient lock to prevent duplicate imports.
• New Retry Import action in the Translations page for any job whose file did not make it into the uploads directory (including jobs stuck by earlier versions). One click refetches a fresh download URL from the API and re-runs the import.
• The Active Jobs panel now stays visible for at least 1.5 seconds even when the API responds instantly, so users always see that their translation was submitted.
• Every step of the import pipeline (download, extract, resolve, write, recompile, DB update) is logged to wp-content/debug.log with a [SimplePoTranslate import] prefix, making failure diagnosis straightforward.
• Scan Files and Translations pages now correctly group uploaded translation files under the parent plugin (not under a generic “plugins” header) and show a proper Uploads location badge.
• String Editor now saves fuzzy entries whose suggested translation the user left unchanged (previously the save silently skipped them because the text hadn’t been edited).
• Manually-edited translations now show a delete icon on the Translations page (previously only API-imported files were deletable).
• Translations page auto-runs a fresh scan when the cache is empty instead of showing a blank table.
• Compatibility shim for plugins that bypass WordPress’ translation API with their own custom MO loader (currently Smart Slider 3 Free and Pro, which use the Nextend framework’s private Localization::$l10n cache and an {locale}.mo filename convention). The plugin does not write outside the uploads directory to support them; instead, after the third-party plugin has finished booting, we read our own uploads .mo and replace their in-memory translation cache via PHP reflection so our translations take effect on the frontend. The shim is scoped to one class, wrapped in try/catch, and a silent no-op on sites without Smart Slider 3 installed.

1.0.4

• Removed every direct reference to the discouraged WordPress path constants (WP_PLUGIN_DIR, WP_CONTENT_DIR, WP_LANG_DIR, and WPINC). All filesystem paths are now derived from plugin_dir_path( __FILE__ ) and the public wp_upload_dir() / get_theme_root() APIs, which work correctly under relocated wp-content layouts, symlinked plugins, and Bedrock-style installs.
• Translation API compatibility: fixed a backend provider issue that previously caused translation jobs to fail with “API reported status=failed” in some locales.

1.0.3

• String Editor now supports editing .po files from any scanned location. When you edit a file stored in a plugin/theme bundle directory or in the v1.0.1 legacy system directory (wp-content/languages/), the plugin automatically copies it into the plugin uploads working area on first edit — your edits live there, the original file is never modified.
• The Translations page now shows the underlying reason when a translation job fails (instead of just a “Failed” badge with no detail).
• Import failures now update the job’s DB row with a clear error message, making it possible to diagnose failed jobs without enabling WP_DEBUG.
• Every step of the import pipeline now writes a structured [SimplePoTranslate import] log line to WordPress’s error log, so the cause of any future import failure can be inspected with a single grep.
• Dashboard surfaces a warning when the plugin cannot write to the uploads directory at activation (previously silent).

1.0.2

• All generated .pot, .po, and .mo files are now written exclusively to wp-content/uploads/simplepo-translator/ (per WordPress.org plugin team guidance). The plugin no longer writes to wp-content/languages/ or any plugin/theme bundle directory during normal operation.
• Translations activate transparently while the plugin is active: the built-in translation loader redirects WordPress’s load_textdomain_mofile and pre_load_textdomain filters to the uploads location, so plugins with custom translation loaders (e.g. Smart Slider 3) continue to work.
• New — Copy translations to WordPress system directory (Settings → Preserve translations): a one-click action that copies the contents of the plugin’s uploads directory into wp-content/languages/plugins/ and wp-content/languages/themes/. Click this before deactivating or removing the plugin if you want your translations to keep loading afterwards. This is the only code path that writes outside the uploads area, and it runs only when the administrator explicitly triggers it.
• Previous “bundle copy” compatibility feature removed; superseded by the translation loader redirect above.
• Backup files now live in wp-content/uploads/simplepo-translator/backups/ (rotated per-file, 5 most recent kept).
• Path-handling consolidated into a single internal helper (SimplePOTranslator\Paths); direct WP_PLUGIN_DIR / WP_CONTENT_DIR references reduced to 3 security/enumeration call sites with inline justifications.
• String Editor now restricts in-place edits to files inside the uploads directory. v1.0.1 translations at wp-content/languages/plugins/ remain loadable but are read-only in the editor — re-import them to move into the new location.
• Full Reset (Danger Zone) and uninstall now remove the uploads directory only; legacy wp-content/languages/ files are preserved in case WordPress core / GlotPress language packs share the directory.
• Deactivation notice on the Plugins page now warns that translations in the uploads directory stop loading once the plugin is inactive and points the user to the new Copy-to-system action.

1.0.1

• Disclosure: added External services and Privacy sections to the readme documenting the optional SimplePoTranslate API (what data is sent, when, and links to Terms and Privacy Policy).
• Generated .pot files are now written to the WordPress system translations directory (wp-content/languages/plugins/ or wp-content/languages/themes/) so they survive plugin and theme updates.
• Imported .po/.mo files from the Auto Translate API are always routed to the WordPress system translations directory; removed a fallback that could write to a plugin’s bundle folder when a locale could not be derived.
• Tightened the inline string editor’s file path validation: edits are now restricted to files inside wp-content/languages/ or files discovered by a prior scan.

1.0.0

• Initial release.
• One-click file scanning for PO/POT files.
• API-powered automatic translation for 39 languages.
• Manual translation workflow with upload support.
• Inline string editor for fuzzy and untranslated entries.
• POT file generation from plugin/theme source code.
• Multi-language simultaneous translation.
• Automatic backup before import operations.
• Safe uninstall — preserves all translation files.