Support

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

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.

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

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

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?

Front end localised language files include the LC4 date format.

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.