question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Bug] Repeatable field issue after update to Version 5

See original GitHub issue

Bug report

What I did

I was using repeatable field on a dynamic form by using JS to modify the hidden field holding the value before calling initializeFieldsWithJavascript and it was working correctly in version 4.1 but after migrating to version 5 it’s no longer working the value must be set while rendering the form

What I expected to happen

the input value should have been rendered correctly

What happened

the field is rendered based on the default configuration

Is it a bug in the latest version of Backpack?

After I run composer update backpack/crud the bug is it still there

Backpack, Laravel, PHP, DB version

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

PHP VERSION:

PHP 7.4.21 (cli) (built: Sep 30 2021 13:37:02) ( NTS ) Copyright © The PHP Group Zend Engine v3.4.0, Copyright © Zend Technologies

LARAVEL VERSION:

v8.83.0@29bc8779103909ebc428478b339ee6fa8703e193

BACKPACK VERSION:

5.0.5@c7c74166244f7995a07abb83f2a83e914e515c9f

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:10 (9 by maintainers)

github_iconTop GitHub Comments

1reaction
basselhossamcommented, Feb 17, 2022

Alternatively @basselhossam … if you’re in a rush and can’t change your logic right now, you should be able to:

  • copy-paste the old repeatable.blade.php file to your resources/views/vendor/backpack/crud/fields with a different name (say… repeatable_v4.blade.php);
  • use repeatable_v4 where you have those customizations - it should still work in v5;

Do keep in mind that it might not work in the next version, though. So you should plan on rewriting that custom logic at some point anyway.

Hope it helps. Cheers!

I will probably go with this for now

0reactions
pxpmcommented, Feb 17, 2022

Haaa ok @basselhossam . It makes sense then using @tabacitu solution. If it worked previously it would still work now. My mistake then, I misunderstood, apologise! 🙏

👍

Read more comments on GitHub >

github_iconTop Results From Across the Web

Not working on Repeater field - WordPress.org
Hey,. This field works inside a repeater in my testing. But it's possible that there's an edge case bug or there's a conflict...
Read more >
Update 5.7.11 causes strange repeater field behaviour - Support
After updating to 5.7.11 with latest WordPress version, I've had issues where trying to retrieve a subfield returns the data from an ...
Read more >
Repeater Field Bug edits made on one version appear to be ...
When making edits to a products technical information (repeater field) across multiple language; edits made on one version of the product ...
Read more >
UPDATE EVENTS NOT MEET 'CURRENT-READ' RULE
Description: Mysql is at the 'REPEATABLE-READ' isolation level: It is no problem to meet the read snapshots when it is not update or...
Read more >
Release Notes - Flyway by Redgate • Database Migrations ...
Flyway 8.5.5 (2022-03-28). Bug fixes. SQL*Plus 'spool' now ignores value of 'feedback' for update statements; Issue 3413 Script migrations applied ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found