I ran a backup profile via the front end using cron with curl. Akeeba went in to an endless loop creating many duplicate archives. Each had a new and unique time stamp. The only way I could stop the process (on a shared host) was to remove the akeeba installation. (On second thoughts - it might have been better to take the front end off-line for a minute :rolleyes: )
The particular profile worked perfectly from the back end.
The cron line worked perfectly on the production version of akeeba (3.0 pro).
Is there any way I can try and control and document this event?
The particular profile worked perfectly from the back end.
The cron line worked perfectly on the production version of akeeba (3.0 pro).
Is there any way I can try and control and document this event?
