Is there a realistic chance that this will somehow make it into the core?
Ok, I understand. Thanks.
Thanks, fixed!
Okay, but why do you need to turn off spreadsheet protection?
I don't have a newer, supported device, so I can't develop the module further.
nevergone → created an issue.
Related: ✨ Add base class for testing Active
nevergone → created an issue.
nevergone → created an issue.
Thanks, I created a new release.
^10.4 || ^11.1
nevergone → created an issue.
I created a new, Drupal 11 compatible release: 2.0.0
I would be happy to help you with other jobs and projects.
nevergone → created an issue.
nevergone → created an issue.
nevergone → created an issue.
nevergone → created an issue.
nevergone → created an issue.
nevergone → created an issue.
nevergone → created an issue.
The module currently works with a specific content type. Changing this would require a significant rewrite.
I recommend that you reference the required entities using an entity reference field.
Fixed.
No errors.
nevergone → created an issue.
nevergone → created an issue.
Done.
nevergone → created an issue.
nevergone → created an issue.
Done. See subtasks.
Add generic test class (create test user, node types, enable fields etc.)
- ✨ Test "Hide previous value" feature Active
- ✨ Test "Lock previous value" feature Active
- ✨ Test "Disable reorder" feature. Active
- ✨ Test "Hide Add more button" feature Active
- ✨ Test "Remove table header" feature. Active
nevergone → created an issue.
nevergone → created an issue.
nevergone → created an issue.
nevergone → created an issue.
nevergone → created an issue.
nevergone → created an issue.
nevergone → created an issue.
nevergone → created an issue.
nevergone → created an issue. See original summary → .
nevergone → created an issue.
nevergone → created an issue.
nevergone → created an issue. See original summary → .
Please test and review. If it's okay, I'll do the test.
nevergone → created an issue.
Fix #3070487-2: Support migrating weight and dimensions from D7 Ubercart → patch with incorrect field name.
Is there any solution to this?
nevergone → created an issue.
I can't provide a link, this is how I use it. I included rebuildContainer(), because otherwise, even if you set something in the form, you can't query it elsewhere.
rebuildContainer() is needed because after the form settings we remain in the same request and the same service container.
It's perfectly fine to use rebuildContainer().