Title: Using NextGen with CodeStyling Localization
Last modified: August 21, 2016

---

# Using NextGen with CodeStyling Localization

 *  [nexenbe](https://wordpress.org/support/users/nexenbe/)
 * (@nexenbe)
 * [12 years, 3 months ago](https://wordpress.org/support/topic/using-nextgen-with-codestyling-localization/)
 * Dear Miss, Sir,
 * I’m using the CodeStyling Localization translation plugin and the plugin detects
   faults concerning the NextGen gallery.
 * Is this something that can be fixed in future versions?
 * Malfunction at 3rd party Plugin detected!
    Name: NextGEN Gallery by Photocrati
   | Author: Photocrati Media Below listed scripts has been automatically stripped
   because of injection:
 *  [http://domain.com/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/ajax/static/ajax.js](http://domain.com/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/ajax/static/ajax.js)
   
   [http://domain.com/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/frame_communication/static/frame_event_publisher.js](http://domain.com/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/frame_communication/static/frame_event_publisher.js)
   [http://domain.com/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/nextgen_admin/static/gritter/gritter.min.js](http://domain.com/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/nextgen_admin/static/gritter/gritter.min.js)
   [http://domain.com/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/nextgen_admin/static/ngg_progressbar.js](http://domain.com/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/nextgen_admin/static/ngg_progressbar.js)
 * More information:
 * Scripting Guard – hardening against plugin/theme based malformed script injections
 * Some authors of plugins and themes does not care about how they attach javascripts
   into WordPress backend pages. They pollute pages from other plugins with their
   own script code and damage the proper function of those plugins.
 * The plugin Codestyling Localization introduced a high sophisticated inject detection
   and will show error messages, if themes or plugins try to inject their own scripts
   into this plugin pages. Furthermore all embedded scripts will be safe guarded
   and traced in case they will raise runtime exceptions. Doing so this plugin protects
   itself of malfunction caused by 3rd party plugin/theme authors. This will ensure
   the correct behavoir for this page, but expect at other backend pages malfunctioning
   code, because this is a global issue.
 * CDN – Javascripts loaded using Content Delivery Networks instead of WordPress
   provide files
 * Some Blog owner decide to replace the location where the Javascripts will be 
   loaded from by using a Plugin. In normal cases this should work proper but sometimes
   WordPress includes versions of Scripts not yet hosted at CDN provider. The Guard
   will threat CDN usage as warning and checks if all files can be load from CDN.
   If not possible to load at least one file, additionally an error message will
   be issued to show, that this page will not work as expected.
 * What can I do, if I get this protection message alert?
 * If your Installation has this kind of problems, please contact the author of 
   theme or plugin(s) which inject their script code either accidentally or intentionally(
   click message details). He/she must repair the affected theme/plugin to play 
   nicely with other plugins at WordPress backend and/or restrict its scripts to
   the 3rd party theme/plugin pages only.
 * Theme & Plugin Authors – exclusion from Guard for developers
 * You may have written a Plugin or Theme that requires scripts at all pages but
   play nicely at backend pages. In those cases please send me an email with your
   repository link. I will check this Plugin or Theme and exclude it from trace,
   if the test will show, that it is working well.
 * Plugins currently supported by Scripting Guard:
 *  WP Native Dashboard (by codestyling)
    Debug Bar (by wordpressdotorg) Debug Bar
   Console (by koopersmith) WP-Piwik (by braekling)
 * Cheers!
    Kevin
 * [https://wordpress.org/plugins/nextgen-gallery/](https://wordpress.org/plugins/nextgen-gallery/)

Viewing 1 replies (of 1 total)

 *  [tizz](https://wordpress.org/support/users/tizz/)
 * (@tizz)
 * [12 years, 3 months ago](https://wordpress.org/support/topic/using-nextgen-with-codestyling-localization/#post-4579270)
 * [@nexenbe](https://wordpress.org/support/users/nexenbe/) if you’re trying to 
   translate the legacy NGG’s .po file, then you can do it anyway (despite that 
   message), but that translation doesn’t work in the current NGG version.

Viewing 1 replies (of 1 total)

The topic ‘Using NextGen with CodeStyling Localization’ is closed to new replies.

 * ![](https://ps.w.org/nextgen-gallery/assets/icon-256x256.png?rev=2083961)
 * [Photo Gallery, Sliders, Proofing and Themes - NextGEN Gallery](https://wordpress.org/plugins/nextgen-gallery/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/nextgen-gallery/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/nextgen-gallery/)
 * [Active Topics](https://wordpress.org/support/plugin/nextgen-gallery/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/nextgen-gallery/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/nextgen-gallery/reviews/)

## Tags

 * [nextgen](https://wordpress.org/support/topic-tag/nextgen/)
 * [Scripting Guard](https://wordpress.org/support/topic-tag/scripting-guard/)

 * 1 reply
 * 2 participants
 * Last reply from: [tizz](https://wordpress.org/support/users/tizz/)
 * Last activity: [12 years, 3 months ago](https://wordpress.org/support/topic/using-nextgen-with-codestyling-localization/#post-4579270)
 * Status: not resolved