Hello everyone, and a Happy New Year!

Today I just finished to update the AVChat Joomla! 2.5 Integration Kit for the newly released mobile version of AVChat.  Without further ado, here is a list of things of updates for the Joomla! Integration Kits:

  • Never miss a new message from now. New browser tab notification lets you see how many new messages you received if you are in another browser tab.
  • Detect if the browser is mobile or desktop and provide the appropriate content.
  • Detect if you installed the AVChat files into the component directory.
  • Facebook Application ID field integration in backend.

Remember that you need the latest build of AVChat (build 2060) to have access to these great features and also FMS media server. This update is currently available only for Joomla! 2.5, but don’t worry, other versions will come soon.

You can download the latest version(build 2065) from you private client area.

Enjoy!

 

5 thoughts on “NEW! Updated Joomla! 2.5 Integration Kits to support the mobile version of AVChat 3 (build 2065)

  1. R says:

    Hello again,
    the error with the disabled “Ignore PMs” button which I had reported for the previous Joomla integration kit is still there, even if admin Stefan had promised to correct it, see http://avchathq.com/forum/index.php?/topic/1626-major-update-june-to-the-avchat-integration-kit-for-joomla-25/page__view__findpost__p__8229 .
    What a shame that they do not track error reports, and what a shame they focus on lots of new functionality (html5) before correcting such obvious errors.

  2. Richard67 says:

    The error in integration.php regardingh the always disabled “Ignore Pms” button is still there, even if it has been promised to be corrected, see
    http://avchathq.com/forum/index.php?/topic/1626-major-update-june-to-the-avchat-integration-kit-for-joomla-25/page__view__findpost__p__8229 !!!

  3. stefan says:

    Richard, please accept my apologies for the IgnorePM button, but I did make the change when I said so. I don’t know why it hasn’t been propagated with the new build. I must have confused some files.

  4. Richard67 says:

    well, I have just seen that my proposed solution does not work, too, so you might have to investigate a bit more.

  5. Richard67 says:

    Another problem is that the setting “enableHtmlClientForDesktopBrowser” seems not to have any effect

Leave a Reply

Your email address will not be published. Required fields are marked *