Akeeba Backup for Joomla!

Monday, 17 March 2014 15:25 CDT

user9198

Hi Nicholas,

Due to your latest improvements I have several end customers websites running the latest Alpha rev2F13CCE but the ' An updated version of Akeeba Backup (3.10.2) is available for installation' warning present at the Akeeba backup control panel is making that some 'end customers' clicked on the provided 'Update to 3.10.2' button rolling back to an earlier and not well working version for their needs :-(

>> How can I hide this warning section when needed? (I don't see a plugin or module managing that)

Image link: http://l.js2go.net/Owl8MB

Thanks in advance for your help,
Rgrds,

Edited by user9198 on 2014-03-17 15:26 CDT

Monday, 17 March 2014 16:18 CDT

user9198

Got it by template overriding this file: \administrator\components\com_akeeba\views\cpanel\tmpl\default.php deleting this part of the default code from line 121 till line 136:

<?php if ($this->updateInfo->hasUpdate): ?>
	<div class="alert alert-warning">
		<h3>
			<span class="icon icon-exclamation-sign glyphicon glyphicon-exclamation-sign"></span>
			<?php echo JText::sprintf('COM_AKEEBA_CPANEL_MSG_UPDATEFOUND', $this->updateInfo->version); ?>
		</h3>
		<p>
			<a href="https://www.akeeba.com/index.php?option=com_installer&view=update" class="btn btn-primary">
				<?php echo JText::sprintf('COM_AKEEBA_CPANEL_MSG_UPDATENOW', $this->updateInfo->version); ?>
			</a>
			<a href="https://www.akeeba.com/<?php echo $this->updateInfo->infoURL ?>" target="_blank" class="btn btn-small btn-info">
				<?php echo JText::_('COM_AKEEBA_CPANEL_MSG_MOREINFO'); ?>
			</a>
		</p>
	</div>
<?php endif; ?>

>> Is there a better and more 'clean' way to disable this warning when needed?

Thanks in advance for your help,
Rgrds,

Monday, 17 March 2014 17:12 CDT

user9198

No way to re-edit last post... rise a 403 error...!? My mentioned solution breaks the akeeba backend CPanel afterwards... Please, ignore the solution I provided. Very sorry for that!
>> I'll wait your answer!

Tuesday, 18 March 2014 02:34 CDT

nicholas

You can just add style="display:none" to the div of the alert box in your template override :)

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Tuesday, 18 March 2014 06:46 CDT

user9198

Thanks Nicholas but...
Something is going wrong! ... As already said there is no way to template override the file \administrator\components\com_akeeba\views\cpanel\tmpl\default.php as \administrator\templates\isis\html\com_akeeba\cpanel\default.php
>> See here the results obtained right after applying the mentioned 'template override' here: http://l.js2go.net/1iZVrhd
>> Only hacking the original file at its default location works. Please, try it yourself and confirm your results (perhaps you can see where is the problem)
Thanks in advance,
Rgrds,

Edited by user9198 on 2014-03-18 06:48 CDT

Tuesday, 18 March 2014 09:10 CDT

nicholas

Oops, right, no template overrides in the back-end.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Tuesday, 18 March 2014 09:35 CDT

user9198

:-) Seems you're very busy!

AS per your short answer seems there is no other way that hacking the file file \administrator\components\com_akeeba\views\cpanel\tmpl\default.php directly in its default location... Or NOT?

When having enough time, could you let me know if finally there is a way to get this *** update warning disabled 'temporarily' mean time an 'Alpha' release life, as the 'latest valid version' available (currently up to 6 days), is longer that the current and latest 'Stable' one (that was only valid during a couple of days till the next 'alpha' one arrived)?

Thanks again for all your help and efforts,
Rgrds,

Edited by user9198 on 2014-03-18 09:36 CDT

Tuesday, 18 March 2014 11:50 CDT

nicholas

Oh, "busy" fails to describe the workload over here. Try "frantic" :D

AS per your short answer seems there is no other way that hacking the file file \administrator\components\com_akeeba\views\cpanel\tmpl\default.php directly in its default location... Or NOT?

Yep. That's exactly what you have to do for now. Of course you will lose the modifications when we launch 3.10.3, but you don't mind that. After all you just want to stop the dev release from complaining that it's out of date :)

When having enough time, could you let me know if finally there is a way to get this *** update warning disabled 'temporarily' mean time an 'Alpha' release life, as the 'latest valid version' available (currently up to 6 days), is longer that the current and latest 'Stable' one (that was only valid during a couple of days till the next 'alpha' one arrived)?

The million dollar question :D You can't. Nobody at Joomla! thought it would be a good idea to let users manage the update channels themselves. Even the one very useful feature, forcing the reload of all updates, was removed in Joomla! 3.2. I don't know if the people who maintain com_installer use it themselves. I suspect not.

If you REALLY want to poke around, you can clear the entries in the #__updates table and disable Akeeba Backup's update site in the #__update_sites table BUT Akeeba Backup will always try to re-enable the update site. It does that because a random network error while fetching the updates will cause Joomla! to disable the update site WITHOUT giving the user the option to re-enable it. So we had to make a bad design choice because Joomla! has made an even more stupid design choice.

I'll take the pitchfork, you take the torch. Let's go find those Joomla! maintainers now ;)

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Tuesday, 18 March 2014 12:28 CDT

user9198

... Of course you will lose the modifications when we launch 3.10.3, but you don't mind that. After all you just want to stop the dev release from complaining that it's out of date :)

That's right!.. Just to have the option to hide temporarily the backend update warning is what I need.

FYI, Upgraded 18 sites to the latest 'alpha' 1 week ago (the ones that needed to use the Box.com remote backup feature through WebDAV) right now 6 of those owners 'clicked on the NEW update button and reinstalled 3.10.2 over. Really annoying and the worst of that I have nothing to complain due that this action has been requested by your NEW backend message & update button.

Surely, what we are suffering is due that the latest 'Alpha' version is taking long time to be converted into 'Stable' (No doubt you have very good reasons! Surely you are still working over with additional improvements and that's the reason by 3.10.3 didn't arrive, yet. Nothing to complain about that)

>> I'll patch the mentioned file in all those sites tonight that will become default at the next update.

Nicholas! Thanks a lot for all! (your time, help and useful comments)

Rgrds,

Wednesday, 19 March 2014 02:30 CDT

nicholas

You're welcome, Gabriel!

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support