Unfortunately, the release of Joomla 3.4.2 last night introduced an unexpected problem in HWDMediaShare. We have already released a new update this morning which fixes the problem, and users can update to version 2.0.1 to resolve this issue.

HWDMediaShare supports the display of your videos directly in the Facebook news feed. When someone shares a video URL from your website, the video player will be displayed, allowing Facebook users to watch the video.


TherapyCable recently caught out eye. We believe it uses the HWDMediaShare technology very effectively, to present healthcare information to a wide audience. The website attempts to create a marketplace where healthcare meets technology; in a consumer-friendly way!

Let's continue with the second part of the series with the goal of setting up a virtual server for developing and testing our hwdMediaShare site in an easy, fast and reproducible way.

From 20 April 2015, Google will no longer support Youtube apps using YouTube API v2.0. You can find out more via this official statement from Google.

Generating revenue from your website content is important. We know that some of our community rely entirely on advertising to earn income, and monetizing video is a fantastic way to see great returns in a growing industry. We are constantly seeking new ways to help users monetize videos, and we are pleased to announce our integration with the Google AdSense for Flowplayer (ASF) program.

Recently, one of our users had some problems implementing JComment in the HWDMediaShare gallery. Whilst investigating and resolving this issue we noticed that the HWDMediaShare plugin in the JComment package was slightly out of date. Although the plugin still worked, it resulted in the incorrect information displaying in the administrator when viewing comments that had been added to HWDMediaShare.

The HWDMediaShare language packs have been updated for version 2, and can now be downloaded and used. We are currently offering packs for Arabic Unitag (ar-AA), Brazilian Portuguese (pt-BR), Bulgarian (bg-BG), Catalan (ca-ES), Chinese Simplified (zh-CN), Chinese Traditional (zh-TW), Croatian (hr-HR), Danish (da-DK), Dutch (nl-NL), Finnish (fi-FI), French (fr-FR), German (de-DE), Hungarian (hu-HU), Italian (it-IT), Japanese (ja-JP), Persian (fa-IR), Polish (pl-PL), Portuguese (pt-PT), Russian (ru-RU), Serbian (latin) (sr-YU), Serbian (sr-RS), Slovak (sk-SK), Spanish (es-ES), Swedish (sv-SE), Thai (th-TH), Turkish (tr-TR), Ukrainian (uk-UA) and Vietnamese (vi VN).

Something that struck me about the latest hwdMediaShare v2 release is how many people jumped to upgrade their good old hwdMediaShare v1 to the shiny new version on their live sites. In some cases the process didn't result as expected, as it usually happens with this major version bumps, and resulted in frustrated users and heads banging against the wall.

While I understand the excitement of having your hwdMediaShare supercharged, the pessimistic in me frowns on the idea of doing in on my live sites without having tested them extensively before on my staging environment. That made think about the reasons why so many experienced professionals make the mistake of doing changes on their live sites without testing them first, and, in some cases, without having a plan to roll back if things go south.