-
Notifications
You must be signed in to change notification settings - Fork 5
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
Table Option changes not persistent #43
Comments
Unfortunately, I could not reproduce the issue. I tested it with different browsers, closed the browsers, restarted OS and waited three hours. |
well, according to the message post time you could not have waited more then 2h 15 min. (at max.) ;-) Either way, it's very bizarre. I've used a completely new installation with a single entry only. Especially in a Yunohost environment it should be easy to reproduce. |
Well, since I also read the issues on Grocy itself - I can :)
However, I have not tested this way, but I will and will then report. |
Is this an upstream issue? |
After testing it exactly like this, I can confirm this issue. While this practice is uncommon and rare, it should not result in this error. However, I can't imagine that this is related to YunoHost. |
@memo-567 from my point of view it's something helpful in my daily Grocy work, to be able to change a table view and expecting it to be still here the next day, without having to refresh the page constantly. |
I did test this issue grocy/grocy#1366 with Grocy on non-Yunohost environment and I was able to reproduce the error. So for me the issue doesn't appear to be related to Yunohost. |
Resolved by grocy/grocy#2494, thanks for sharing your time help tracking this down in the last 2 years. |
Describe the bug
changed table options are no persistent where the should be persistent.
Context
Steps to reproduce
Expected behavior
changes made in the table options should be persistent. They should not revert back to default (according to the Grocy developer)
Grocy developer says that this issue is not reproduceable in a regular Grocy installation and the issue may be related to Yunohost.
grocy/grocy#1366
Logs
N/A
The text was updated successfully, but these errors were encountered: