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:
We've spoken in the past 48hrs on another medium, about my WD MyCloud NAS and wanting to set my Akeeba up to not just CRON backup back to my VPS server, but also to upload an FTP copy in to my WD MyCloud.
I've logged in to my joomla admin, selected my cron (no.2) profile and then in the "Post-processing engine" section, select "Upload to Remote FTP Server" and when I do, then select the 'Configure' button and ftp option fields stay visible for a couple of seconds but it then disappears, reverts back to as you will see in the attached screenshot and hence I can't enter the pertinent details.
I also tried some of the other post-processing options and they do the same, but not all.
I'm using latest G Chrome to access my admin backend but have tried Firefox and that browser seems to be fine, so I just thought I'd let you know - as I do prefer Chrome to be fair but will use FF for now with your component, until we can get to the bottom of the Chrome issue.
Regards, Rob
Description of my issue:
We've spoken in the past 48hrs on another medium, about my WD MyCloud NAS and wanting to set my Akeeba up to not just CRON backup back to my VPS server, but also to upload an FTP copy in to my WD MyCloud.
I've logged in to my joomla admin, selected my cron (no.2) profile and then in the "Post-processing engine" section, select "Upload to Remote FTP Server" and when I do, then select the 'Configure' button and ftp option fields stay visible for a couple of seconds but it then disappears, reverts back to as you will see in the attached screenshot and hence I can't enter the pertinent details.
I also tried some of the other post-processing options and they do the same, but not all.
I'm using latest G Chrome to access my admin backend but have tried Firefox and that browser seems to be fine, so I just thought I'd let you know - as I do prefer Chrome to be fair but will use FF for now with your component, until we can get to the bottom of the Chrome issue.
Regards, Rob
