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

[Enhancement]: (Cosmetic) Add line about ensuring permission is provided to ereader provider when setting up ereader devices #2990

Closed
ZLoth opened this issue May 19, 2024 · 1 comment · Fixed by #3010
Labels
enhancement New feature or request

Comments

@ZLoth
Copy link

ZLoth commented May 19, 2024

Type of Enhancement

Web Interface/Frontend

Describe the Feature/Enhancement

In the Settings → Email Settings → Ereader Devices , there needs to be a disclaimer line stating that permission has to be provided in order for the ebooks to be emailed to the user.

Why would this be helpful?

While it is documented in https://www.audiobookshelf.org/guides/send_to_ereader#common-issues , this will actually call the issue out.

Future Implementation (Screenshot)

image

Audiobookshelf Server Version

2.9.0

Current Implementation (Screenshot)

I don't have a image, but this would be something that would be assist a new administrator.

@ZLoth ZLoth added the enhancement New feature or request label May 19, 2024
@ZLoth ZLoth changed the title [Enhancement]: (Cosmetic) Add [Enhancement]: (Cosmetic) Add line about ensuring permission is provided to ereader provider when setting up ereader devices May 19, 2024
@advplyr advplyr added the awaiting release Issue is resolved and will be in the next release label May 25, 2024
@advplyr
Copy link
Owner

advplyr commented May 27, 2024

Updated in v2.10.0

@advplyr advplyr removed the awaiting release Issue is resolved and will be in the next release label May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants