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

[Bug]: Availability settings returns Failed to load availability #48477

Closed
4 of 8 tasks
mczarnecki1986 opened this issue Sep 30, 2024 · 1 comment
Closed
4 of 8 tasks
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap 28-feedback bug

Comments

@mczarnecki1986
Copy link

⚠️ This issue respects the following points: ⚠️

Bug description

After opening page with Availability in settings, Nextcloud returning error: Failed to load availability.

Steps to reproduce

  1. Log in
  2. Navigate to Personal settings->Availability

Expected behavior

Nextcloud should load availability settings according to the previous set up.

Nextcloud Server version

28

Operating system

None

PHP engine version

None

Web server

None

Database engine version

None

Is this bug present after an update or on a fresh install?

Fresh Nextcloud Server install

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

  • Default user-backend (database)
  • LDAP/ Active Directory
  • SSO - SAML
  • Other

Configuration report

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

@mczarnecki1986 mczarnecki1986 added 0. Needs triage Pending check for reproducibility or if it fits our roadmap bug labels Sep 30, 2024
@joshtrichards joshtrichards changed the title [Bug]: Availability settings not working [Bug]: Availability settings returns Failed to load availability Oct 1, 2024
@joshtrichards
Copy link
Member

joshtrichards commented Oct 1, 2024

You didn't fill out the template, but sounds like you're on an outdated release. This was already fixed as of 28.0.10 (and I just double-checked: occurs in 28.0.9 but not 28.0.10 for me). Closing, but let me know if you're somehow seeing this in an up-to-date deployment.

Ref: #47732 / #44344

@joshtrichards joshtrichards closed this as not planned Won't fix, can't repro, duplicate, stale Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap 28-feedback bug
Projects
None yet
Development

No branches or pull requests

3 participants