nextcloud / cookbook

🍲 A library for all your recipes
https://apps.nextcloud.com/apps/cookbook
GNU Affero General Public License v3.0
522 stars 89 forks source link

When creating a recipe or editing is , it randomly not save the last ingredient or the last instruction (or both) #2174

Open Tonic8 opened 6 months ago

Tonic8 commented 6 months ago

Description When creating a new recipe it won't save the last ingredient or the last instruction (or both). when editing to add the last ingredient or the last instruction, it won' save it again. to resolve the issue

it's seems to be random.

Reproduction Steps to reproduce the behavior:

  1. Create a recipe
  2. add 6 ingredients
  3. add 6 instructions
  4. Save
  5. count the ingredient list saved
  6. count the instructions list saved

Expected behavior :) the right numbers of ingredients or and instructions

Actual behavior when it occur checking the json file result the last ingredient and/or instruction is not present.

Screenshots

Browser Chrome 122.0.6261.95 on windows 10

Versions Nextcloud server version: 27.1.6 Cookbook version: 0.10.5 Database system: MariaDB

tomdeck commented 6 months ago

I have a very similar (potentially the same) issue: when adding instructions manually, these are not saved. One work-around I found was: add the new instruction; move it up; move it back down to the initial position; save

Tonic8 commented 6 months ago

il will try , as fo rnow i add 1 extra inxtruction and 14 extra ingredient before saving the first time and then remove them

Tonic8 commented 4 months ago

i just added 20 recipes today and had no issue.

i'm now running nextcloud 27.1.8 (previously on 27.1.6), but still with Cookbook 0.10.5

any suggestion or we close the ticket?

christianlupus commented 4 months ago

It will close itself unless someone steps in. Let's see if others have the problem as well.

david-aigner commented 3 months ago

Same issue here! Version 0.11.0 Nextcloud Hub 8 (29.0.2)

github-actions[bot] commented 1 month ago

This issue was not updated for 45 days. It is therefore marked as stale. When no update occurs within the next 7 days, this issue will be closed automatically in the next 7 days.

github-actions[bot] commented 1 month ago

This issue was not updated since it was marked as stale. It will be closed now.

christianlupus commented 3 weeks ago

There seems still to be a user having the issue.

@david-aigner, unfortunately, I cannot reproduce it. Would you be willing to track down the problem on a more technical level? I would try to guide you and see if we can rule out if it is a frontend or backend issue. How reproducible is this for you? Can you somehow "trigger" the effect consistently, or is it just happening from time to time?