You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading to 5.3.0, selecting an Asset in a Container throws a 500 error.
{
"message": "Class Statamic\\Http\\Controllers\\CP\\Assets\\ActionController contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (Statamic\\Http\\Controllers\\CP\\ActionController::getItemData)",
"exception": "Symfony\\Component\\ErrorHandler\\Error\\FatalError",
"file": "/Users/Marty/Code/asseterror/vendor/statamic/cms/src/Http/Controllers/CP/Assets/ActionController.php",
"line": 8,
"trace": []
}
This means Assets cannot be deleted.
If you were to select an asset, across the top of the list I expect to see options, such as delete.
If you select an Asset's "..." and then select Delete, you get the same error.
This issue is not present in 5.2.0. Current workaround is to rollback to 5.2.0.
How to reproduce
Install a new site
Upload an asset
Select the asset, or click "..." then Delete and follow the prompts
Logs
[2024-05-21 06:31:54] local.ERROR: Class Statamic\Http\Controllers\CP\Assets\ActionController contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (Statamic\Http\Controllers\CP\ActionController::getItemData) {"exception":"[object] (Symfony\\Component\\ErrorHandler\\Error\\FatalError(code: 0): Class Statamic\\Http\\Controllers\\CP\\Assets\\ActionController contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (Statamic\\Http\\Controllers\\CP\\ActionController::getItemData) at /Users/Marty/Code/asseterror/vendor/statamic/cms/src/Http/Controllers/CP/Assets/ActionController.php:8)[stacktrace]#0 {main}"}
Environment
EnvironmentApplication Name: StatamicLaravel Version: 11.7.0PHP Version: 8.3.7Composer Version: 2.7.6Environment: localDebug Mode: ENABLEDURL: asseterror.testMaintenance Mode: OFFCacheConfig: NOT CACHEDEvents: NOT CACHEDRoutes: NOT CACHEDViews: CACHEDDriversBroadcasting: logCache: statamicDatabase: sqliteLogs: stack / singleMail: logQueue: syncSession: fileStatamicAddons: 0Sites: 1Stache Watcher: EnabledStatic Caching: DisabledVersion: 5.3.0 Solo
Installation
Fresh statamic/statamic site via CLI
Additional details
No response
The text was updated successfully, but these errors were encountered:
duncanmcclean
changed the title
[5.x] 500 error in JS console trying to delete an asset after 5.3.0 upgrade
500 error in JS console trying to delete an asset after 5.3.0 upgrade
May 21, 2024
Bug description
After upgrading to 5.3.0, selecting an Asset in a Container throws a 500 error.
This means Assets cannot be deleted.
If you were to select an asset, across the top of the list I expect to see options, such as delete.
If you select an Asset's "..." and then select Delete, you get the same error.
This issue is not present in 5.2.0. Current workaround is to rollback to 5.2.0.
How to reproduce
Logs
Environment
Installation
Fresh statamic/statamic site via CLI
Additional details
No response
The text was updated successfully, but these errors were encountered: