Support

Akeeba Backup for Joomla!

#13896 Setting output directory fails

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 Monday, 22 October 2012 03:28 CDT

heiligenfeld
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? No
Have I searched the tickets before posting? Yes
Have I read the documentation before posting (which pages?)? Yes
Joomla! version: 2.5.7
PHP version: 5.3.13
MySQL version: 5.1.63
Host: allinkl.com
Akeeba Backup version: 3.6.7

EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 2Mb, please upload it on your server and post a link to it.

Description of my issue:
When I set my output directory to a new I can save without errors. But when I leave akeeba and come back the default directory is set again.
The new folder has enough rights and is located on level below my website directory, but one level higher than the server root.
I tried different things, without success.

nicholas
Akeeba Staff
Manager
Are you always looking at the same backup profile?
Set the Output Directory, clicking on Save & Close, then click again the Configuration. Is the directory saved?
Do you have the same issue saving any other setting or is it just the Output Directory?

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!

heiligenfeld
Thats strange. Tested it today again and now it worked. I don't know why.

nicholas
Akeeba Staff
Manager
There is an explanation – albeit it's a long shot. Browsers do cache Javascript files. It's possible that after a while the broken, cached Javascript file expired and the browser downloaded the new one, therefore fixing the issue you had.

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!