Bug 921402

Description of problem:
Some plugins for WordPress in RH Cloud is broken.

Version-Release number of selected component (if applicable):


How reproducible:
It is reproducible

Steps to Reproduce:
1. Install WordPress as in RH Cloud.
2. Install plugins such as PicasaView
3. Activate PicasaView plugin
  
Actual results:

Javascript is not properly loaded-up, hence the lightbox script does not work properly. Javascript debug console shows that the javascript.js is not correctly called i.e. at 

https://appname-space.rhcloud.com/wp-content/plugins/var/lib/openshift/513daeba4382ecd17f000045/app-root/data/plugins/picasaview/picasaview.js

Expected results:

The proper call should be:

https://appname-space.rhcloud.com/wp-content/plugins/picasaview/picasaview.js


Additional info:

The problem can be as follow:
a. Red Hat already have the folder "plugins" in ~/app-root/runtime/repo/php/wp-content as symlink to  /var/lib/openshift/513daeba4382ecd17f000045/app-root/data//plugins

b. Hence, the PicasaView plugin is installed in /var/lib/openshift/513daeba4382ecd17f000045/app-root/data//plugins

c. The problem is that the php code inside picasaview.php with many standard "__FILE__" which translates to the file name with absolute address i.e. /var/lib/openshift/513daeba4382ecd17f000045/app-root/data//plugins/picasaview/picasaview.php, and the coding create 

https://appname-space.rhcloud.com/wp-content/plugins/var/lib/openshift/513daeba4382ecd17f000045/app-root/data/plugins/picasaview/picasaview.js  -- which is broken

instead of 

https://appname-space.rhcloud.com/wp-content/plugins/picasaview/picasaview.js


d. The solution is to delete the "plugins" folder set by RH Cloud, which is symlinked to /var/lib/openshift/513daeba4382ecd17f000045/app-root/data//plugins, and create "plugins" folder without symlink. The risk will be the "plugins" folder can be erased during GIT push.