Support

Akeeba Backup for Joomla!

#8523 [SOLVED] Administer BU Files issues in SVN183

Posted in ‘Akeeba Backup for Joomla!’
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

user12388
Noticed that in SVN181 and 183 the Administer BU Files interface has some issues:
There is no default description as in 3.0
Archive files are not shown
Type column shows Full Backup when actual type is db archive

There are some residual .svn files in the distribution (in the plugin folders). They cause some problems on a shared host as they get root gid and then I need support to delete them for me :-)

David

dlb
David,

The Administer Backups problem was reported this morning by another user. I'll flag this for Nicholas too for the .svn issue. Thank you.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

nicholas
Akeeba Staff
Manager
SVN186 uploaded about an hour ago fixes the Administer Backup Files issues. The .svn issue is being worked on, I'll have it fixed by the end of the day :)

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!

user12388
I installed SVN186 (over 183) and found that the Administer Backup Files interface still has the same issues:
1. Short description does not appear
2, Start date is not correct
3. Type is fixed on Full Site Backup when db archive and site files are used
4. Archive file that is retained in local storage does not appear
5. Profile number is fixed on 1 when other profiles were used

I've attached a screen capture

nicholas
Akeeba Staff
Manager
I can not replicate these issues on my servers. The only ways these could happen are:

1, 3, 4, 5: The akb_ak_stats database table didn't get updated during installation. Please use your host's copy of phpMyAdmin to get the CREATE TABLE command of this table (e.g. run SHOW CREATE TABLE jos_ak_stats) and paste here the result so that I can check for it.

2: Your Joomla! language files are out of date. Make sure that you've upgraded to at least Joomla! 1.5.18 (ideally, 1.5.19 which is the current release). I can't read the version in the screenshot :) Since you're using a localised installation, you also have to update the localised language files to the latest release. Older versions are missing the translation string which is used to produce the date format LC4 we're using in the SVN release.

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!

user12388
I installed SVN186 from a fresh install.
The BU admin table is still not working
Following is the result of a SHOW CREATE query I ran
---------------------------------------------------------------------
CREATE TABLE `jos_ak_stats` (
`id` bigint(20) unsigned NOT NULL auto_increment,
`description` varchar(255) NOT NULL,
`comment` longtext,
`backupstart` timestamp NOT NULL default '0000-00-00 00:00:00',
`backupend` timestamp NOT NULL default '0000-00-00 00:00:00',
`status` enum('run','fail','complete') NOT NULL default 'run',
`origin` varchar(30) NOT NULL default 'backend',
`type` varchar(30) NOT NULL default 'full',
`profile_id` bigint(20) NOT NULL default '1',
`archivename` longtext,
`absolute_path` longtext,
`multipart` int(11) NOT NULL default '0',
PRIMARY KEY (`id`),
KEY `idx_stale` (`status`,`origin`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8
--------------------------------------------------------------------
I also exported the created record to csv and following is the result. (The backup was of db-archive type)

"1";;NULL;"0000-00-00 00:00:00";"2010-07-18 20:59:51";"complete";"backend";"full";"1";NULL;NULL;"0"

I ran a compare file check on the install.sql in SVN186 against the same file in 3.0 pro distribution and found that they are the same.

My Joomla! version is 1.18.

Hope this helps

user12388
Regarding the language files. I'm using the original en-GB files for the backend but I am using localised for the front end. Can this have an effect?

user12388
Front end localised language files include the LC4 date format.

nicholas
Akeeba Staff
Manager
You can safely try SVN189. This time I fixed the issue ;) In SVN188 and previous versions there were two missing fields from the stats table which caused all the problem.

Regarding the language issues. The English back-end language file administrator/language/en-GB contains the LC4 date format:
DATE_FORMAT_LC4=%d.%m.%y

The top line of the file in one of my outdated but operational local installations reads (so that you can compare your version):
# $Id: en-GB.ini 16380 2010-04-23 09:19:48Z ian $

The front-end language INIs also contain LC1 through LC4. If one of those strings is missing, you have an outdated translation.

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!

user12388
Happy to report that with SVN189 the BU Admin Table is perfect.

Thanks for a quick response on this.

I checked and I have all language files fully up to date.

nicholas
Akeeba Staff
Manager
Great! I am glad we got that fixed :)

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: Typically we work Monday to Friday, 9am to 7pm Cyprus timezone (EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets, but we cannot respond to them, outside of our working hours.

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!

Summer vacations: Our support will be closed for replies and new tickets from August 6th to August 21st, 2022 due to summer vacations.