Currently, your tribe_resource_url function doesn’t seem to play well when the website is served out of a symlinked dir.<\/p>\n
I’m having to run the following code as a mu-plugin to work around the problem:<\/p>\n
With capistrano you have a releases dir, with a symlink point to a current dir. The current dir is what is served up by the webserver.<\/p>\n Here are the PATHS set in our config<\/p>\n With the webserver serving this folder:<\/p>\n but the real directory, the content being in something like:<\/p>\n Because you are using a number of PHP functions to read the current dir, it will return the real dir rather than what the webserver and WordPress says where it is (symlinked dir).<\/p>\n So when you come to compile the resource URL we end up with something like this:<\/p>\n instead of:<\/p>\n<?php
\nadd_filter('tribe_resource_url', function ($url) {
\n$root = dirname(dirname(__DIR__));
\nif (strpos($url, $root) === 0) {
\n$url = str_replace($root, home_url(), $url);
\n}
\nreturn $url;
\n});<\/code><\/p>\nWP_SITEURL=https:\/\/ngs.staging.bigfish.co.uk\/wp
\nWP_HOME=https:\/\/ngs.staging.bigfish.co.uk
\nWP_CONTENT_URL=https:\/\/ngs.staging.bigfish.co.uk\/app
\nWP_CONTENT_DIR=\/var\/www\/ngs.staging.bigfish.co.uk\/current\/web\/app
\n<\/code><\/p>\n $_SERVER['DOCUMENT_ROOT'] = '\/var\/www\/ngs.staging.bigfish.co.uk\/current\/web'<\/code><\/p>\n\/var\/www\/ngs.staging.bigfish.co.uk\/releases\/XXXXXXXXX\/web<\/code><\/p>\n\/var\/www\/ngs.staging.bigfish.co.uk\/releases\/20170228143114\/web\/app\/plugins\/the-events-calendar\/src\/resources\/js\/aggregator-admin-legacy-settings.js<\/code><\/p>\nhttps:\/\/ngs.staging.bigfish.co.uk\/app\/plugins\/the-events-calendar\/src\/resources\/js\/aggregator-admin-legacy-settings.js<\/code><\/p>\n","protected":false},"template":"","class_list":["post-1247579","topic","type-topic","status-closed","hentry"],"yoast_head":"\n