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

Back button takes you back to the general settings screen #598

Closed
ZTetriminos opened this issue Sep 11, 2024 · 1 comment · Fixed by #599
Closed

Back button takes you back to the general settings screen #598

ZTetriminos opened this issue Sep 11, 2024 · 1 comment · Fixed by #599
Assignees

Comments

@ZTetriminos
Copy link

Swiping back on any screen will take you back to the general settings screen of the app, instead of the previous screen you were on.

This is particularly annoying when trying to edit the Knowledge Base, as I'm trying to delete a few terms but each time I delete and confirm, swiping back takes me two screens back. I would like to be taken back to the Knowledge Base list..

This issue happens to other menu sections as well.

When I click here or swipe back in this screen...
ResizedImage_2024-09-11_07-55-25_2267

I want to be taken back here...
Screenshot_20240911-075133

...not here!
Screenshot_20240911-075226

@eb1 eb1 self-assigned this Sep 11, 2024
eb1 added a commit to eb1/adapt-it-mobile that referenced this issue Sep 17, 2024
Add URLs for each of the settings, so that the Back functionality is consistent.
@eb1 eb1 mentioned this issue Sep 17, 2024
@eb1 eb1 closed this as completed in #599 Sep 17, 2024
@eb1 eb1 closed this as completed in 2a72d5e Sep 17, 2024
@eb1 eb1 added this to the Patch release 1.17.2 milestone Sep 17, 2024
@eb1
Copy link
Contributor

eb1 commented Sep 17, 2024

Hi @ZTetriminos: I was able to find and fix this issue for the next patch release. Should be a couple days. Thanks!

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 a pull request may close this issue.

2 participants