teraßyte Posted March 26 Share Posted March 26 In the file /system/File/Amazon.php inside the function deleteContainer() this code is executed when adding a new delete task to delete the files in a bucket folder (container): /* Turn on task */ \IPS\Db::i()->update( 'core_tasks', array( 'enabled' => 1 ), array( '`key`=?', 's3_delete' ) ); The problem is that the task's key is not s3_delete but s3Delete (no space + capitalized). This causes the task to delete the S3 files to not activate correctly. The same issue is also present inside the code of the s3Delete task to disable itself in 2 different locations. Lines 44-50: if ( !( $obj instanceof \IPS\File\Amazon ) ) { /* Class is not Amazon, so just stop here and truncate the table as there's nothing we can really do now. */ \IPS\Db::i()->delete( 'core_s3_deletions' ); \IPS\Db::i()->update( 'core_tasks', array( 'enabled' => 0 ), array( '`key`=?', 's3_delete' ) ); return NULL; } Lines 96-97: /* Nothing to do, so switch off the task */ \IPS\Db::i()->update( 'core_tasks', array( 'enabled' => 0 ), array( '`key`=?', 's3_delete' ) ); Again s3_delete is being used instead of s3Delete. SeNioR- and Afrodude 2 Link to comment Share on other sites More sharing options...
Marc Posted March 27 Share Posted March 27 Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release. SeNioR- 1 Link to comment Share on other sites More sharing options...
Solution teraßyte Posted May 14 Author Solution Share Posted May 14 This is fixed in 4.7.17 Beta 1. Marking as resolved. SeNioR-, Jim M and Marc 3 Link to comment Share on other sites More sharing options...
Recommended Posts