siteurl=http://ccc.org.mk/
jlibrariesdir=/home/cccorgmk/public_html/libraries
jversion=1.5
lastversion=3.4.3
liveupdate=stuck=0\nlastcheck=1548140199\nupdatedata="{\"supported\":true,\"stuck\":false,\"version\":\"4.7.5\",\"date\":\"2016-12-12\",\"stability\":\"stable\",\"downloadURL\":\"https:\\\/\\\/cdn.akeebabackup.com\\\/downloads\\\/akeebabackup\\\/4.7.5\\\/com_akeeba-4.7.5-core.zip\",\"infoURL\":\"https:\\\/\\\/www.akeebabackup.com\\\/download\\\/akeeba-backup\\\/akeeba-backup-4-7-5.html\",\"releasenotes\":\"<h3>Removal of the Dropbox v1 API integration and how to switch to the v2 API<\\\/h3><p>    We have removed integration with the Dropbox v1 API because Dropbox itself    <a href=\\\"https:\\\/\\\/blogs.dropbox.com\\\/developers\\\/2016\\\/06\\\/api-v1-deprecated\\\/\\\">announced it is deprecated<\\\/a> and will be    turned off by June 28th, 2017. We chose to remove support for the deprecated API now to make sure that all of our    clients will be ready for Dropbox' deprecation next year. If you think that's an overkill please keep in mind that    we added Dropbox v2 support in November 2015 with the documentation note that it's the recommended version and that    the v1 API may stop working at any point.<\\\/p><p>    Unfortunately, Dropbox' v1 and v2 APIs are very different and there is no way to have an automatic migration from    v1 to v2. The access tokens used in the two API versions are and work different. This means that by upgrading to a    new version of Akeeba Backup your backup profiles which were using the deprecated Dropbox v1 API    integration are no longer linked to a post-processing engine and produce errors.<\\\/p><p>    Luckily there's a very simple process you have to follow <strong>once<\\\/strong> on every site and backup profile you    want to (re)link to Dropbox.<\\\/p><p>    <strong>THIS PROCESS ONLY NEEDS TO TAKE PLACE ONCE PER BACKUP PROFILE AND SITE!<\\\/strong><\\\/p><ul>    <li>Go to your Akeeba Backup main page.<\\\/li>    <li>Select the backup profile you want to relink.<\\\/li>    <li>Click on Configuration.<\\\/li>    <li>In the Post-processing Engine dropdown select \\u201cUpload to Dropbox (v2 API)\\u201d<\\\/li>    <li>Click on \\u201cConfigure\\u201d next to it.<\\\/li>    <li>Click on the \\u201cAuthentication \\u2013 Step 1\\u201d button.<\\\/li>    <li>You may have to log in to Dropbox if you are not already logged in. Also, if you had not authorized another        Akeeba Backup or Akeeba Solo installation to use Dropbox you may see a confirmation about it. If you are already        logged in and have authorized our software to use Dropbox you will not see any of that.<\\\/li>    <li>You then see a page with the big title \\u201cDropbox Authentication is almost complete\\u201d. Click on the blue \\u201cComplete        Dropbox authentication\\u201d button below it.<\\\/li>    <li>Now you're back to Akeeba Backup. Click on Save & Close to complete the setup.<\\\/li><\\\/ul><p>    Unlike the Dropbox v1 API you <strong>must not<\\\/strong> copy the token from one profile \\\/ site to another. Instead,    repeat the process above. Dropbox API v2 produces a new token every time you link a new backup profile or site to    Dropbox <em>without<\\\/em> revoking the previous one.<\\\/p><p>    Again, we apologize for having to go through this process but this is due to changes made on Dropbox' side. On the    upside, the Dropbox API v2 is much more stable, allows for bigger uploads and lets us perform \\u201cchunk uploads\\u201d, a    technique which allows us to transfer very large backup archives without you having to set up small part sizes. You    can now safely use a Part Size for Split Archives up to 2047 Mb without any upload worries.<\\\/p><h3>Joomla! 1.6 or later<\\\/h3><p>    This version is compatible with Joomla! 1.6, 1.7, 2.5, 3.0, 3.1, 3.2, 3.3, 3.4 and 3.5.<\\\/p><p>    Please note that we do NOT recommend using Joomla! 1.x \\\/ 2.x or 3.0 to 3.3 inclusive on production sites due to    major security issues. Support for these old versions is intended to give you the option of taking a full site    backup prior to upgrading to the latest available Joomla! release.<\\\/p><h3>PHP 5.3.3 or later 5.x version is required<\\\/h3><p>    <strong>If you have Joomla! 3.4 or later and PHP 5.4 or later please use Akeeba Backup 5.x. This version of        Akeeba Backup (4.7.x) will only receive very irregular security fixes \\\/ critical issue fixes but NO regular bug fixes and new features.<\\\/strong>    This version of Akeeba Backup is only published for people managing older sites so that they can back them up before upgrading them. Any other use is strongly NOT recommended!<\\\/p><p>    The minimum required PHP version is 5.3.03. All versions of PHP from 5.3.03 onwards are supported, including 5.4,    5.5, 5.6 and the just released PHP 7.0. The component will not work on PHP 5.2 or earlier and will, in fact, refuse    to install on it. We'd like to remind you that Joomla! 3.4 and earlier does NOT support PHP 7. Joomla! 3.5 (currently    in beta) does support PHP 7. Akeeba Backup will work just fine in a Joomla! 3.5 site running on PHP 7.0. If you are using a PHP version newer than PHP 5.3 we strongly recommend that you install the latest available version of Akeeba Backup instead of this one.<\\\/p><p>    <small>Note: there is no such thing as PHP 6. PHP versions jumped from 5.6 to 7.0. Why? Well,        <a href=\\\"https:\\\/\\\/philsturgeon.uk\\\/php\\\/2014\\\/07\\\/23\\\/neverending-muppet-debate-of-php-6-v-php-7\\\/\\\" rel=\\\"nofollow\\\">it's a long story<\\\/a>. TL;DR: It doesn't have to make sense, just accept it.    <\\\/small><\\\/p><h3>  Changelog<\\\/h3><p>  No changelog will be provided for 4.7 versions. A summary of the changes made can be found in the release description.<\\\/p>\"}"\n\n

