Better detection for symlinks in bbp_enqueue_style() and bbp_enqueue_script()

[r-a-y]

If the bbpress directory or WP_PLUGINS_DIR is symlinked, bbp_enqueue_style() and bbp_enqueue_script() has trouble calculating the asset's URL.

This is mostly due to those functions using the WP_CONTENT_DIR constant for replacement.

Attached patch does replacement from the plugins directory, stylesheet directory and template directory, instead of looking at WP_CONTENT_DIR.

Plugins directory is calculated from bbpress()->plugin_dir.

[johnjamesjacoby]

Hey @r-a-y, thanks for this.

Did you test this with bbPress in mu-plugins, or some other directory like wp-content/bbp-plugins/bbpress?

Many installs (like WordPress.com) will have custom plugins locations, and bbPress (and BuddyPress too) need to continue to support them. It's also unlikely we have test cases for this yet, so I doubt anything would perk up there.

[r-a-y]

Sorry for the late reply.

I tested with symlinking the plugins directory locally, as well as on a webhost that has done the same thing (I'm guessing). The host in question is Red Hat OpenShift.

Also see #2739.

[johnjamesjacoby]

I applied the patch, and it doesn't work with custom directories added to the bbp_get_template_stack().

I'd like to bump this to 2.7, only to help get 2.6 across the line. If we can work on this sooner than 2.7, that's a-OK.

[netweb]

I think some unit tests could be beneficial here also

[r-a-y]

Just getting back to this after this issue was talked about in Slack.

Replying to johnjamesjacoby:

I applied the patch, and it doesn't work with custom directories added to the bbp_get_template_stack().

Got any examples I could test with? Are your custom directories located outside the plugins directory?

Replying to netweb:

I think some unit tests could be beneficial here also

I'm not sure how unit tests could be written to test for different, custom-linked bbPress directories...