[wp-trac] [WordPress Trac] #26886: wp_enqueue_script doesn't load all scripts

[WordPress Trac]

#26886: wp_enqueue_script doesn't load all scripts
----------------------------+---------------------
 Reporter:  alfredocubitos  |       Owner:  azaozz
     Type:  defect (bug)    |      Status:  closed
 Priority:  normal          |   Milestone:  5.3
Component:  Script Loader   |     Version:  3.8
 Severity:  normal          |  Resolution:  fixed
 Keywords:                  |     Focuses:
----------------------------+---------------------

Comment (by mizuki1rg):

 you're encountering an issue with WordPress where scripts are not being
 loaded correctly due to a limitation in how the script names are
 concatenated and split. Let's break down the problem and potential
 solutions:

 Problem Description:

 WordPress concatenates script names into a query string with a maximum
 length of 128 characters.
 When the concatenated script names exceed this length, they are split,
 potentially cutting script names in the middle.
 Impact:

 This issue affects the loading of scripts, causing some scripts to not
 load properly, leading to functionality issues on the website.
 Potential Solutions:

 Core Modification:

 You've mentioned modifying the WordPress core file script-loader.php to
 change how the concatenation is handled. While this can resolve the
 immediate issue, modifying core files is generally not recommended due to
 potential conflicts during updates and maintenance.
 Changing the split length from 128 to a higher value, such as 3000, may
 temporarily resolve the issue, but it's essential to consider potential
 side effects and compatibility issues.
 Plugin Conflict:

 Initially, there was speculation about a plugin conflict causing the
 issue. However, it seems that the problem lies within WordPress core
 itself.
 Resolving conflicts between plugins may improve overall stability but may
 not directly address the core issue of script concatenation.
 Further Considerations:

 It's crucial to understand the implications of modifying core files and
 consider alternative solutions that do not involve core modifications.
 Thorough testing is necessary after any changes to ensure that the website
 functions correctly and that there are no unexpected side effects.
 Community Discussions:

 It appears that this issue has been discussed in the WordPress support
 forums, with users sharing their experiences and potential solutions.
 Engaging with the WordPress community can provide valuable insights and
 alternative approaches to resolving the issue.
 In summary, while modifying core files may provide a temporary workaround,
 it's essential to explore alternative solutions and consider the long-term
 implications of any changes. Engaging with the WordPress community and
 thoroughly testing solutions are crucial steps in addressing the script
 loading issue effectively.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/26886#comment:42>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform