@dgilbert

We uploaded a fixed version of the 3099844 patch (#45) that resolves the error it was causing (this issue).

I believe this will fix the bug (#41) in the #35 patch for 3.x branch.

dgilbert → changed the visibility of the branch 3099844-required-fields-make to active.

dgilbert → changed the visibility of the branch 3099844-required-fields-make to hidden.

dgilbert → changed the visibility of the branch 3099844-required-fields-make to hidden.

The 3.x branch (#35) version of this patch is causing a POST 500 Internal Server Error having to do with Ajax. The error occurs when you try to add a new entity (adding an existing entity works as expected).

Here's the steps to reproduce the error:
Create a new content type and add a new field "Reference" field. Select "Content" for the entity reference type and configure the field to accept an existing content type. Next select the "Manage form display" tab and edit the new reference field to use "Inline entity form - Complex" and "Allow users to add existing nodes". Create a new page using the new content type and for the new entity reference field, click the "Add existing node" button. Use type-ahead to select an existing node and click the "Add node" button. Nothing happens and errors are displayed in the browser console.

We have determined that the 3.x (#35) version of this patch is causing the issue; https://www.drupal.org/project/inline_entity_form/issues/3099844 🐛 Required fields make an optional IEF (erroneously) required Needs work

dgilbert → created an issue.

dgilbert → created an issue.

@yce Any idea when the dev branch will be moved into prod (3.2.2)? Would it be possible to provide a patch until 3.2.2 is released?

I'm not sure what to say about reproducing the issue other than; update the module from 3.2.0 to 3.2.1 and run the Drupal status report Status Report /admin/reports/status.

Our local dev environments run mysql 5.7 and php 8.2.15. Our remote test environments run mysql 5.7.4 and php 8.2. Drupal is 10.3.2.

In both our local and remote environments the module update ran successfully, but in both cases the db hook update does not appear to be applied per the status report error.

I see that hook in the module code but it does not seem to apply with updatedb?

dgilbert → created an issue.

We ran into the same exact error running updatedb after upgrading from 10.1.5 to 10.1.7. Deleted and reinstalled core and the problem was resolved.

@caspervoogt Thanks for the help, we were able to get the module working with D10.

We're currently using 1.48 but the #16 patch fails to install using composer with this error:
Cannot apply patch https://www.drupal.org/files/issues/2023-09-15/3362505-16-d10additions.patch
Any thoughts on how we can get the patch to install?

Or the other option would be to set composer to use the fork as source but we're not exactly sure how to do that? This seems to work but not sure if it's the correct method;
composer require drupal/media_acquiadam:dev-3362505-upgrade-acquia-dam-1x-to

Added to composer "repositories"

{
      "type": "vcs",
      "url": "https://git.drupalcode.org/issue/media_acquiadam-3362505"
}

Thanks for any help!