Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FIX: asset-admin is a suggested, not required module #203

Closed
wants to merge 1 commit into from
Closed

FIX: asset-admin is a suggested, not required module #203

wants to merge 1 commit into from

Conversation

sminnee
Copy link
Member

@sminnee sminnee commented Aug 5, 2020

This lets you install the module in apps that don’t have asset-admin
(such as ModelAdmin-focused apps, where batch editing would be handy)

Fixes #202.

This lets you install the module in apps that don’t have asset-admin
(such as ModelAdmin-focused apps, where batch editing would be handy)

Fixes #202.
@sminnee
Copy link
Member Author

sminnee commented Aug 15, 2020

Any thoughts on this?

@sminnee
Copy link
Member Author

sminnee commented Sep 10, 2020

@robbieaverill @colymba do you think that this will cause issues for people who expect to have asset-admin pulled in for them? I'd note that I haven't tested this module on an installation lacking asset-admin, and while I'd like to, it's difficult to pull it into a project without this PR.

@robbieaverill
Copy link
Contributor

It's a tricky thing to answer really, because this module provides two equally valuable features: bulk uploading, and bulk editing. If you use this for the bulk uploading then maybe you would expect asset-admin to be installed. I have a feeling that people are more likely to install this on a full Silverstripe installation though, so this PR seems sensible to me.

"silverstripe/framework": "~4",
"silverstripe/framework": "~4"
},
"suggest": {
"silverstripe/asset-admin": "~1"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"silverstripe/asset-admin": "~1"
"silverstripe/asset-admin": "Provides an admin interface for managing your Silverstripe assets"

The suggest schema is key => value: module => description

Copy link
Member Author

@sminnee sminnee Sep 10, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right, good point. I think I might rewrite it to say "Necessary to make use of bulk-upload features." ie to explain why we're suggesting that module.

@GuySartorelli
Copy link
Member

Just had a look through the codebase. There's one concrete reference to AssetAdmin and a few references to File and Image.
I think there should probably be some logic to not load the classes that depend on silverstripe/assets and silverstripe/asset-admin if we're going to remove those as a dependency.

@sminnee
Copy link
Member Author

sminnee commented Jul 2, 2022

Fair enough, the assumption was that BulkUploadHandler wouldn't be used on a project without AssetAdmin, but it can probably be patched to provide an error message to that effect if you try and use it.

@sminnee sminnee closed this Feb 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Drop asset-admin requirement
3 participants