Title: Move inline JavaScript into its own JS file
Last modified: September 24, 2017

---

# Move inline JavaScript into its own JS file

 *  Resolved [philiprabbett](https://wordpress.org/support/users/philiprabbett/)
 * (@philiprabbett)
 * [8 years, 8 months ago](https://wordpress.org/support/topic/move-inline-javascript-into-its-own-js-file/)
 * The impressions and clicks JavaScript code added to wp_footer should really be
   enqueued as a separate JS file rather than embedded as an inline script.
 * This functionality is breaking when I move the WordPress jQuery script to the
   footer.
 * Please fix this.

Viewing 1 replies (of 1 total)

 *  Plugin Author [gfazioli](https://wordpress.org/support/users/gfazioli/)
 * (@gfazioli)
 * [8 years, 8 months ago](https://wordpress.org/support/topic/move-inline-javascript-into-its-own-js-file/#post-9589201)
 * [@philiprabbett](https://wordpress.org/support/users/philiprabbett/) Interesting,
   let me investigate. Thanks for reported.

Viewing 1 replies (of 1 total)

The topic ‘Move inline JavaScript into its own JS file’ is closed to new replies.

 * ![](https://ps.w.org/wp-bannerize-pro/assets/icon-256x256.png?rev=3503931)
 * [WP Bannerize Pro](https://wordpress.org/plugins/wp-bannerize-pro/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-bannerize-pro/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-bannerize-pro/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-bannerize-pro/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-bannerize-pro/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-bannerize-pro/reviews/)

## Tags

 * [enqueue](https://wordpress.org/support/topic-tag/enqueue/)
 * [javascript](https://wordpress.org/support/topic-tag/javascript/)
 * [wp_footer](https://wordpress.org/support/topic-tag/wp_footer/)

 * 1 reply
 * 2 participants
 * Last reply from: [gfazioli](https://wordpress.org/support/users/gfazioli/)
 * Last activity: [8 years, 8 months ago](https://wordpress.org/support/topic/move-inline-javascript-into-its-own-js-file/#post-9589201)
 * Status: resolved