Support

Akeeba Backup for Joomla!

#19180 Date format in Manage Backups not being processed

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by nicholas on Friday, 14 February 2014 07:11 CST

Thursday, 13 February 2014 07:22 CST

Adam_NZ
Description of my issue:
Hi Nicholas - I think a PHP tag is corrupt somewhere, as the date in the (3.10.1 updated) Manage backups/RESTORE POINTS page isn't being interpreted correctly (the BACKUPS page is OK):

System Restore Point - component: com_admintools l, d F Y H:i Obsolete (830.05 Kb)
System Restore Point - component: com_akeeba l, d F Y H:i Obsolete (1.23 Mb)
System Restore Point - component: com_admintools l, d F Y H:i Obsolete (829.34 Kb)
System Restore Point - component: com_akeeba l, d F Y H:i Obsolete (1.22 Mb)
System Restore Point - component: com_admintools l, d F Y H:i Obsolete (817.22 Kb)

Adam.
Edited by Adam_NZ on 2014-02-13 07:25 CST

Thursday, 13 February 2014 09:49 CST

tampe125
Hello Adam,

please install Akeeba Backup twice in a row, without uninstalling it. Sometimes Joomla "forgets" to copy all the files.

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Thursday, 13 February 2014 10:49 CST

Adam_NZ
Hi Davide ... did that. Install went OK ... same error though.

Adam.

Thursday, 13 February 2014 11:20 CST

nicholas
Hello Adam,

I have fixed this bug quite a while ago and it's certainly not happening on Joomla! 3.2 and Akeeba Backup 3.10.1. However I am missing quite a lot of information which would enable me to provide a proper reply. Namely, I need to know the exact versions of Akeeba Backup, Joomla! and PHP running on your site. I am suspecting that you have an old version of Akeeba Backup which was, indeed, affected by this bug.

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!

Thursday, 13 February 2014 20:38 CST

Adam_NZ
Hi Nicholas! Thanks for jumping in. I should have given that info right at the beginning - sorry.

Akeeba Backup Professional 3.10.1 (2014-02-13)

PHP Built On Linux rakiura 2.6.32-bpo.5-amd64 #1 SMP Wed Jul 20 09:10:04 UTC 2011 x86_64
Database Version 5.5.32-0ubuntu0.12.04.1-log
Database Collation utf8_general_ci
PHP Version 5.3.28
Web Server Apache
WebServer to PHP Interface cgi-fcgi
Joomla! Version Joomla! 2.5.16 Stable [ Ember ] 06-November-2013 22:30 GMT
Joomla! Platform Version Joomla Platform 11.4.0 Stable [ Brian Kernighan ] 03-Jan-2012 00:00 GMT
User Agent Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0

Regards,

Adam.

P.S. I don't mind an uninstall/fresh install if that cures it.

Thursday, 13 February 2014 21:16 CST

Adam_NZ
UPDATE: I just tried another site *on the same server*. This one went OK ... BUT I notice that the site that doesn't show the bug is (a newer) 2.5.18.

I went back to the "problem" site and re0installed (again) but using the "Standard" installer option, in case that made any difference. It didn't.

Should I just upgrade 2.5.16 to 2.5.18? Many of my other sites are now Joomla 3.0.

Adam.

Thursday, 13 February 2014 21:49 CST

Adam_NZ
Sorry for the multiple posts. The "edit" option times out before I can report back from the latest test.

The 2.5.16 to 2.5.18 thing is a red herring.

I just updated another five 2.5.16 sites to 3.10.1 (all on the same server - all previously AKB Pro 3.10.0). In 4/5 cases, all is OK. For the one case, it also displays the bug. Go figure!

Adam.
Edited by Adam_NZ on 2014-02-13 21:49 CST

Friday, 14 February 2014 01:31 CST

nicholas
What you see is part of the description that's being saved at the time the system restore point is taken. Apparently you are talking about old system restore points which were created by older versions of Akeeba Backup affected by this bug. This bug is resolved, but since these are old restore points and the failed date/time stamp was statically stored in them at the time they were taken you still see the old, failed date/time stamps on these records. This is normal and you can't do anything about it.

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!

Friday, 14 February 2014 02:27 CST

Adam_NZ
Fantastic - thanks, Nicholas - that explains why it appears to be sporadic.

Sorry to have taken up so much of your time about such a trivial thing that ended up being irrelevant (LOL!!).

Wonderful program - and tremendous service (as ever).

All the best,

Adam.

Friday, 14 February 2014 07:11 CST

nicholas
Thank you for your kind words, Adam!

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 Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!