03-15-2012 06:06 AM
I have created a plugin (.SWF file) and added the full URL to it in my player at Brightcove Studio. I keep adding more features and uploading the .SWF. I add debug messages using com.brightcove.api.modules.ExperienceModule.debug(
And I debug my plugin using the Brightcove debugger at http://admin.brightcove.com/viewer/BrightcoveDebug
However after I add new debug messages, compile my .as file into .SWF and then upload it, I dont see thew new messages appearing immediately - it seems to take a long time before they would show up. It ias as though the previous plugin is cached and used.
Is there a way to fix this ? If it indeed uses a cache, how do I clear it so that I can see my new debug messages and code changes reflected immediately in the plugin.
Thanks in advance,
Solved! Go to Solution.
05-07-2012 01:21 PM
If you are constantly changing the URL of the Plug-in in your Player Settings then it may be a caching issue on our end and you should take the following steps to try flushing the cache:
-If it's a Single Video Player, select a Video from the Media Module screen. Click the 'Quick Video Publish' button to reveal the Quick Video Publish options. Click the 'Play' button that's to the right of the text field. This will open our 'Preview' link for your Player. The URL should begin with 'https://console.brightcove.com/' and will display your Player with the most recent changes.
-If it's a Player that has a Playlist assigned to it, you can do the same steps as above, or you can just use the 'Preview' button from the Publishing Module because the Player already has content assigned to it.
If the URL to your Plugin SWF is not changing, and you are simply overwriting the SWF that is hosted on your own Server then this sounds like the caching issue is external to Brightcove. When the Player is called we are simply making a call to the URL and retrieving whichever SWF the server returns. As always, the best first steps to take for troubleshooting this type of issue is to try a new browser or clearing your browser's cache.