I have YARPP installed and operating fine on my local OS X development machine, but upon deployment to production, I found that some admin functionality is broken due to bad CSS/JS paths. The plugin operates just fine, in that the related posts are found and displayed properly. This problem is limited to the admin page.
Looking at the source I find that all the paths inserted by the plugin look like this (paths anonymized):
<link rel='stylesheet' id='yarpp_options-css' href='https://www.example.com/content/plugins/home/username/web/example.com/releases/20120204011521/public/content/plugins/yet-another-related-posts-plugin/options.css?ver=3.4.3' type='text/css' media='all' />
As you can see, the full filesystem path is being returned instead of the URL path. This happens to all paths inserted by the plugin.
The problem seems to be related to use of
plugins_url() in class-admin.php. That's a WP function, not yours, but your plugin is the only one I've ever seen this problem with, so I'm not sure what's going on there.
I'm using the latest version of both this plugin and WordPress itself. My dev environment, which works fine is running OS X 10.7.2 with Apache 2.2.20 and PHP 5.3.6. My production server is running Ubuntu 11.10 with Apache 2.2.20 and PHP 5.3.6. All Apache and PHP packages are the system defaults, nothing custom.