In some cases the plugin does not run and does not show the contents of the component or the contents is not looking the same as when the component is called standalone.
When the plugin does not show contents of the included component, look into the generated source of the page and search for the comments of the plugin include component. There may be shown errors and give your tips on how to solve it.
You also can use Firebug to look into the generated source and to check if the correct css is used.

The plugin can not work because of the following causes:

• The plugin opens a connection to the same webserver where the script is running from. These types of 'loopback' connections are sometimes blocked on shared hosting for server safety.
  Ask your hosting company for help.
• The plugin opens a url so the webserver must resolve the url to an ip-address and needs to use a DNS server. So the DNS has to be configured on the webserver or the host file on the webserver should redirect it to the localhost.
• If the design of the page is wrong, you must check if css files are loaded multiple times. You can try to ignore the css file that is loaded twice and you can try to ignore the print.css file. For print.css check what the correct url is in the generated source of the page.