Skip to:
Content

BuddyPress.org

Opened 12 years ago

Closed 9 years ago

Last modified 9 years ago

#5797 closed enhancement (wontfix)

Dynamically generated asset handles not available to other plugins

Reported by: boonebgorges Owned by:
Priority: normal Milestone:
Component: Templates Version:
Severity: normal Keywords:
Cc:

Description

In r7205 (#4949) we introduced the concept of a "template stack" for CSS and JS assets. This means that the handle used when enqueuing the assets is dynamic. This causes problems when, in another plugin, you want to be able to make a script dependent on the BP scripts - it's not possible to tell (without reaching into the $wp_scripts global) what the handle for the JS file is.

Might be nice to store the handles in the buddypress() object or something.

Change History (7)

#1 @DJPaul
12 years ago

#5972 needs fixing before this one.

#2 @DJPaul
12 years ago

  • Component Core → Theme / Template Parts

#3 @DJPaul
12 years ago

  • Milestone 2.2 → Future Release

#4 @DJPaul
11 years ago

#5972 is now fixed with r9524, and that ticket contains some initial discussion about whether we should make BP-Legacy's CSS and JS files have non-dynamic handles, or whether we should leave BP-Legacy as-is and instead use non-dynamic handles for the CSS/JS in a future template pack.

#5 @DJPaul
10 years ago

  • Component Appearance - Template Parts → Templates

#6 @DJPaul
9 years ago

  • Milestone Future Release
  • Resolution → wontfix
  • Status new → closed

Closing most tickets related to BP-Default and BP-Legacy, since the upcoming BP-Nouveau template pack (planned for 3.0) will make these redundant.

#7 @DJPaul
9 years ago

Closing most tickets related to BP-Default and BP-Legacy, since the upcoming BP-Nouveau template pack (planned for 3.0) will make these redundant.

Note: See TracTickets for help on using tickets.