Crud: [Bug] Multiple Repeatable Field save content of the first one in every field

Created on 26 Aug 2020  路  8Comments  路  Source: Laravel-Backpack/CRUD

Bug report

What I did

After updating from 4.1.15 to 4.1.19 content with multiple repeatable field save for every field the content of the first one losing data.

What I expected to happen

Every field should save self data.

What happened

Seems js of repeatable overwrite value of input

What I've already tried to fix it

No

Backpack, Laravel, PHP, DB version

When I run php artisan backpack:version the output is:

PHP VERSION:

PHP 7.4.3 (cli) (built: May 26 2020 12:24:22) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
with Zend OPcache v7.4.3, Copyright (c), by Zend Technologies

LARAVEL VERSION:

v7.26.0@f64299a11dedaaadf1cfff07b2b3220a9b791837

BACKPACK VERSION:

4.1.19@a47eeda32d08d0d47a3c820416c8a8f880752b80

image

Look at fields: interview, personalData, career, social

Before save content was:
image

Bug MUST triage urgent

All 8 comments

I am on it. Pretty sure it's a bug I introduced yesterday. It should be an easy fix. Sorry for that, I will let you know here when I come up with a solution.

Best

Thank you for a quick reply.
I'm looking with various version of crud at exactly which version it broke.

Yeah, i can confirm that everything work well 'till 4.1.18.

The same thing happens to me after the update too.

Thank you @pxpm ! And of course @bedoz & @DanielKimmich .

Hello @bedoz and @DanielKimmich

Sorry for the introduction of the bug, it slipped me :upside_down_face:

I'v submitted PR #3156 that address this issue. It's a very small change you can do it manually in your project until it gets merged (it should not take long) .

Also if you did try it, let your approval/refusal in the PR to make sure it fixed the problem described. It would help us a lot.

Going to close this, lets keep any discussion in the PR thread.

Wish you guys the best,
Pedro

Merged and tagged - if you get 4.1.20 you should have this fixed.
Thanks again @pxpm , @bedoz & @DanielKimmich !

It is verified that it was solved. Thank you very much.

Was this page helpful?
0 / 5 - 0 ratings