Inline the custom JavaScript using wp_print_inline_script_tag() #12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request updates the plugin to version 1.1.6 and addresses how custom JavaScript is added to WordPress sites. The main improvements are switching to the recommended WordPress function for inlining JavaScript and moving the script output from the page header to the footer for better performance and compatibility.
JavaScript Output Improvements:
wp_print_inline_script_tag()
, which is the WordPress-recommended approach for adding inline scripts.<head>
(usingwp_head
) to the footer (usingwp_footer
), ensuring scripts are loaded at the optimal time.Version and Documentation Updates:
additional-javascript.php
,package.json
, and updated the stable tag inreadme.txt
. [1] [2] [3]CHANGELOG.md
andreadme.txt
to document these changes. [1] [2]