Closed (fixed)
Project:
Inline Entity Form
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
8 Feb 2016 at 14:02 UTC
Updated:
1 Apr 2016 at 11:04 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
tedbowUnassigning myself. I took a quick and couldn't figure it out. I will get back to it but not actively looking at it now
Comment #3
slashrsm commented#2568991: Improve tests for IEF simple field widget was committed and includes workaround for this issue in test. Attached patch shows that test fails if we remove that workaround. Goal of this issue is to make the test green.
Comment #4
slashrsm commentedComment #6
tedbowfixed title
Comment #8
tedbowOk finally think I figured this out.
Re-rolled the TEST_ONLY patch but it is the same as before.
I wanted to test this with a nested simple widget but I get a "Maximum function nesting level" and increased the limit to 1500 and then I get a memory error. I don't think we have tested nesting the simple widget so this is probably a separate issue.
Comment #9
tedbowComment #11
bojanz commentedWell, if you nest the simple widget on the same entity type/bundle, you'll get an endless loop :)
We should protect against that.
Comment #12
skyredwangI tested ief-add_another-2664626-8.patch, it works well. What else needs to be done in this issue?
Comment #13
tedbow@skyredwang thanks for testing. I made 1 small change so the patch would work when field is nested could you test this?
Thanks
Comment #14
skyredwangI don't know what situation is that.
See the screenshot, is this nested? It works with ief-add_another-2664626-8.patch already.
Comment #15
skyredwangComment #17
bojanz commentedCommitted, thanks.
Comment #18
skyredwangAfter I applied the latest patch, now IEF always opens an empty entity form, which won't pass validation. Is this something intended? Please see screenshot attached.
Comment #19
bojanz commentedSounds like we need more tests then.
Comment #20
tedbowAfter I applied the latest patch, now IEF always opens an empty entity form, which won't pass validation. Is this something intended? Please see screenshot attached.You should always get an empty entity form if you have no current value in the field. This because the simple widget can only be used with required fields.
It looks like from your image that you are editing a parent entity where the IEF field has one value is that correct. In that case there should not be an empty IEF field when you edit the parent entity.
Is that what you are seeing? I can't reproduce this
@skyredwang can you give more details about the field setup? And how you are using IEF in this case? Also when do you see this? When you are editing? adding? when the field already has a value?
Also can you try the latest 8.x-1.x-dev or clone? You shouldn't need to apply the patch because this has been committed. I just want to make sure you have all latest changes.
thanks!
Comment #21
tedbowI did see the problem @skyredwang was describing when writing this patch but I can't reproduce.
I made a issue for adding related test coverage to make sure it doesn't show up in the future #2685789: Add test coverage to ensure that empty entity form does not appear with simple widget when not expected.
Comment #22
tedbowI am marking this as fixed again.
The problem @skyredwang describes is different that this issue and I can not reproduce it.
@skyredwang if you have another issue please create a new one.
Thank,s
Comment #23
skyredwangI tested the latest dev packaged on Mar.16th with a fresh Drupal 8.0.5 install. Inline editing form can no longer save any value for my commerce_stock module https://github.com/INsReady/drupal-commerce-stock
If I revert it back to Inline Entity Form 8.x-1.0-alpha4+27-dev (2016-Mar-01), then saving works again.
Comment #24
bojanz commented@skyred
Please open a new issue for that, along with more details ("can no longer save" -> what does that mean? any error message/)