Bugfix: improved javascipt exception handling within jQuery initializer chains
Bugfix: updated re-introduced js libraries
Version 1.99.28
Bugfix: function missing in very old WordPress versions covered
Bugfix: Scripting Guard now detects broken ready handler of injected javascripts
Bugfix: redirection of prototype/scriptaculous done only, if WP version >= 3.5-alpha
Version 1.99.27
Bugfix: WordPress version 3.5 starts removing prototype.js and scriptaculous but falls back to google CDN include which brokes JSON requests
Bugfix: CDN verification returned an error object and caused a fatal error if external script can't be verified
Bugfix: german translation contains untranslated terms
Bugfix: compatibility improved and checked, still compatible with WordPress >= 2.5
Version 1.99.26
Bugfix: WordPress version 3.5 starts removing prototype.js and scriptaculous but falls back to google CDN include which brokes JSON requests
Bugfix: CDN verification returned an error object and caused a fatal error if external script can't be verified
Bugfix: german translation contains untranslated terms
Bugfix: compatibility improved and checked, still compatible with WordPress >= 2.5
Version 1.99.25
Bugfix: trim of string sometimes broken like: 'Result: \'text\''
Bugfix: 'Domain Path' of plugins will be accepted if set and existing
Bugfix: uppercase letters used at folders or filenames did break the file handling
Bugfix: SSL fully supported, all scripts stripped accidentally
Bugfix: multisite support accidentally sometime broken
Bugfix: accidentally markup polution
Bugfix: theme detection for WP >= 3.3 was broken
Bugfix: statements of memory limits with 0MB indicates mostly misused translation functions at themes/plugins, handled now (e.g. target theme, single.php).
Bugfix: pofile sometimes created with wrong pluralization
Bugfix: mofile didn't got the correct pofile header and loads afterwards the wrong pluralization function
Feature: misused translation functions mapped into artificial textdomain '{bug-detected}' and excluded from mo file generation
Feature: Scripting Guard supports now 'debug-bar', 'debug-bar-console', 'wp-native-dashboard'
Feature: Scripting Guard now monitors PHP script errors provoked by other plugins/themes during page generation
Version 1.99.24
Bugfix: at Multisite installations the global var $domain was accidentally overwritten by dealing with "same origin policy" and did break new blog creation
Bugfix: Scripting Guard now separates external script access from CDN mapped scripts and threat them as "dubious" an warnings
Bugfix: external script validation failed, if scripts are at SSL locations, verify SSL option ste to false now
Feature: none CDN external scripts will be stripped from page creation now always
Version 1.99.23
Bugfix: injected stylesheets may modifiy the thickbox content and will not have any influence now.
Bugfix: potfile indicator was created without filesystem api
Bugfix: WordPress Language directory creation was done without filesystem api
Feature: Scripting Guard now additionally reports CDN based script redirection as warning hint (e.g. ajax.googleapis.com)
Feature: Child Theme translations will be supported completely
Feature: Language files from Main Theme can be synchronized with existing Child Theme files (see help)
Feature: Plugin Help System has been extended again (upper right corner help)
Languages: added Hindi Translation based on 1.99.23
Version 1.99.22
Bugfix: Scripting Guard message was damaged, only affects the message itself not the function behind, repaired
Bugfix: Thickbox gets damaged by Themes/Plugins injecting wp-admin/js/media-upload.js, has been handled and will be reported too.
Bugfix: FTP filesystem handling changed to more server installations.
Version 1.99.21
Bugfix: missing space char at plugin description added
Bugfix: warning message at profile page handled and removed
Bugfix: active theme detection was not working at WP 3.4
Bugfix: consider last component the editor was launche for and scroll to it, if "back to overview page" was clicked or F5 gets pressed
Bugfix: minor CSS changes for RTL target languages. Editor have to show source box in LTR anyway even if target remains as RTL
Feature: plugin stylesheet removed from code into dedicated CSS file
Feature: using WordPress filesystem if direct modification of files are not permitted at the webspace
Feature: first introducing "Scripting Guard" plugin self protection
Feature: help system again extended for WordPress versions >= 3.3
Compatibility: still backward compatible downto WordPress 2.5 but without the filesystem writing (direct write required)
Version 1.99.20
Bugfix: translating the plugin/theme descriptions accidentally states, that Codestyling Localization uses more than one textdomain
Bugfix: admin ajax url not longer lowercase completely, only "same origin policy" parts will be lowercased to avoid broken ajax calls
Bugfix: false positive XSS vulnerablities handled anyway, all reported vulnerabilities require always an admin login (admin permission) to be executable and are all false positive
Bugfix: last 4 plugin versions damaged the backward compatibility downto WordPress version 2.5 and has been repaired to support also this old versions of WordPress again
Bugfix: writing indicator during long time write operations of large mo files was missing
Bugfix: *.po files writen with refreshed revision date automatically
Bugfix: re-scan process refreshes the Product-Id-Version field of *.po file
Bugfix: minor visibility adjustments
Bugfix: locale nn_NN not longer supported, replaced by nn_NO
Feature: using the WordPress backend help system at WordPress version >= 3.3
Version 1.99.19
Bugfix: pot file indicator writes unstructured content and blocked new language creation
Bugfix: valid specified UTF-8 character breaks JSON response during editor call (LINE SEPARATOR / decimal: 8232)
Bugfix: trailing NUL chars may comming out of a reversed *.mo files and will be skipped now
Bugfix: Chinese Traditional and Simplified can be used with translation API now
Bugfix: disabled (unavailable) API's may hang the editor call
Bugfix: Plugin/Theme Descriptions which are translatable (plugin loaded) shows up translated if possible.
Feature: User Interface has been polished to be closer at WordPress standard backend look and feel.
Feature: Translation API availabilities updated, visualization of which API is able to translate what language
Feature: special workaround only for WooCoomerce none standard German language file handling (temporary solution)
Feature: complete support of WordPress 3.4 changed localization behavior at core files
Feature: special handling for improper context based "Center" text, used at UI and as continent/cities
Feature: complete translation of WordPress within one *.po (merges now first splitted po files) file but separate saving of *.mo files
Feature: qualified support of older and newer versions of WordPress out of the box
Feature: supports Uighur language
Feature: supports Albanian language
Feature: supports Burmese language
Version 1.99.18
Bugfix: compatibility with upcomming WordPress 3.4 and rewritten WordPress Theme Core
Bugfix: skips now protected folder during scan process instead of warning message output
Bugfix: simple plugins (main folder) but translatable now being supported correctly
Bugfix: google translate response leads to hidden exception and idle dialog.
Bugfix: minor changes for RTL language CSS
Feature: per user translation API configuration as second option extends User Profile Settings
Feature: provider mode possible to disable the help screen for API configuration
Feature: supports galego language
Feature: supports mongolian language
Feature: supports georgian language
Version 1.99.17
Bugfix: old Google Translate API v1 removed (obsolete and not longer supported)
Bugfix: WordPress 3.4 changes Theme handling, scan process adapted
Bugfix: additional warnings and errors for textdomain issues and textdomain detection
Bugfix: avoid that NomNom Theme damages the plugins pages by unwanted script injection
Feature: Implementation of Google Translate API v2, requires API Key (paid service)
Feature: Implementation of Microsoft Translate API, requires Access Tokens and Curl (free service for 2M characters / month)
Languages: updated german translation
Version 1.99.16
Bugfix: failed preg_match repaired
Bugfix: compatible with latest WP 3.3 pre-release because of modified ThickBox script.
Version 1.99.15
Bugfix: detection of theme textdomains eighter loaded by variable or defined as constant by variable
Version 1.99.14
Bugfix: bbPress plugin translation show index wrong messages (because of stand alone instead of packaged with BuddyPress)
Bugfix: bbPress uses own _nx_noop translations accidentally mapped to default textdomain
Version 1.99.13
Bugfix: WordPress mu-plugin textdomains partially not detected even if present
Version 1.99.12
Bugfix: blog urls configured with uppercase letters breaking ajax JSON calls because of false positive brower XSS detection
Bugfix: textdomain scanning has problems with textdomain names in vars
Bugfix: WP e-Commerce plugin don't play cooperative and hardly unregisters prototype.js library at all backend pages (worked arround)
Version 1.99.11
Bugfix: IDNA support requires now PHP 5.2.1 or higher, not longer possible at lower PHP versions to support IDN
Bugfix: avoid PHP serialization warnings at low memory mode scanning
Bugfix: avoid warnings for not registered locale abbreviations
Bugfix: if used mbstring.func_overload at php.ini with at least mode 2 containing, the plugin didn't work as expected.
Version 1.99.10
Feature: detection of plugins with code created textdomains, but with warning
Feature: experimental parsing of .phtml files now supported
Bugfix: IDNA support requires now PHP 5.0 or higher, PHP 4.x not longer possible with IDN
Languages: updated german translation
Version 1.99.9
Bugfix: IDN support works different for WebKit based browsers (Chrome / Safari) than all others currently
Version 1.99.8
Bugfix: translation file worked with wrong pluralization for different languages if *.pot files have been read and used as translation base
Bugfix: translation file did not recognize the correct language requested if *.pot file was the base of catalog
Bugfix: if catalog contains no translations, an illegal *.mo file can be produced and shows error at blog pages during load.
Bugfix: wrong handling of plural counts leads to stopped working at translation page
Bugfix: IDN based installations won't work because of JSON same origin problem forced by PunyCode Domain Names
Languages: added polish translation based on 1.99.7
Version 1.99.7
Feature: support of low memory condition option for scanning and editing language files to avoid out of memory messages and aborts
Bugfix: reduced the ammount of memory necessary during processing, worked arround PHP internal bugs
Bugfix: serveral english typo's corrected
Bugfix: loading stylesheet for RTL based languages correctly
Languages: added hebrew translation based on 1.99.7
Languages: added dutch translation based on 1.99.7
Version 1.99.6
Feature: detection of trailing spaces at text phrases and visualization
Feature: filter for entries with trailing spaces
Feature: support of translatable plugin header files
Maintenance: language files moved into a subfolder for better handling
Maintenance: screenshots shrinked, updated and extended