- Issue created by @joegraduate
- Merge request !18Issue #3468426: PHP warnings when using CKEditor plugin to access DAM through media library β (Merged) created by joegraduate
- Issue was unassigned.
- Status changed to Needs review
4 months ago 9:04pm 15 August 2024 - Status changed to RTBC
4 months ago 9:19pm 15 August 2024 - πΊπΈUnited States trackleft2 Tucson, AZ πΊπΈ
Tested in tugboat, no errors in the log when I embedded a media item via the media browser using the intelligence bank integration.
- Status changed to Active
4 months ago 9:20pm 15 August 2024 - πΊπ¦Ukraine vlad.dancer Kyiv
@joegraduate I can't reproduce it with steps defined in issue's description. Check it here https://mr18-ofex2zwrcgdavguzjeqiezzieztdtign.tugboatqa.com/node/1 . No errors found in db log https://mr18-ofex2zwrcgdavguzjeqiezzieztdtign.tugboatqa.com/admin/report...
What additional steps did you do to get such errors? Which Drupal, module, php versions are you using? Have you configured settings here admin/config/services/ib_dam/media ?
BTW: "Select the downloaded image in the Media library" step is not necessary because after selecting asset in DAM modal it will be automatically downloaded and preselected in media modal.
- πΊπ¦Ukraine vlad.dancer Kyiv
Oh, I just realized that tugboat deployed Drupal with MR applied there. Ok, I need to test it on gitpod, without the MR.
-
vlad.dancer β
committed 4388fd4f on 4.1.x authored by
joegraduate β
Issue #3468426 by joegraduate, vlad.dancer, trackleft2: PHP warnings...
-
vlad.dancer β
committed 4388fd4f on 4.1.x authored by
joegraduate β
- Status changed to Fixed
4 months ago 10:27pm 15 August 2024 - πΊπ¦Ukraine vlad.dancer Kyiv
Ok, looks like there is no need to store an empty data inside $widget_context['ib_dam_media']:
"field" => array:3 [ "name" => null "entity_type_id" => null "entity_bundle_id" => null ]
when modal has been opened from CKEditor.
For now I'm accepting MR and put into my todo list optimising this case.
Thank for heads up!
- πΊπΈUnited States joegraduate Arizona, USA
Thanks for the quick response @vlad.dancer!
Automatically closed - issue fixed for 2 weeks with no activity.