Column not found error when using media package

[abishekrsrikaanth]

@milewski, I get this error when I use this nova package https://github.com/ebess/advanced-nova-media-library. Could you advice how to resolve this? I looked at previous releases where you exclude saves for certain library fields. Does the same need to be done for this as well?

[milewski]

Currently, I don't have a setup where I could quickly try this out, but are you able to modify these lines

conditional-container/src/ConditionalContainer.php

Lines 278 to 304 in 4ac92c2

	/**
	* Imagine the situation where you have 2 fields with the same name, you conditionally show them based on X
	* when field A is saved the db value is saved as A format, when you switch the value to B, now B is feed
	* with the A data which may or may not be of the same shape (string / boolean for example)
	* The following check resets the resource value with an "default" value before processing update
	* Therefore avoiding format conflicts
	*/
	if ($matched && $request->route()->controller instanceof ResourceUpdateController) {
	foreach ($this->fields as $field) {
	if ($field instanceof Field &&
	!blank($field->attribute) &&
	!$field->isReadonly($request) &&
	!$field instanceof RelatableField &&
	!$field instanceof \Whitecube\NovaFlexibleContent\Flexible &&
	!$field instanceof \Benjacho\BelongsToManyField\BelongsToManyField &&
	!$field instanceof \DigitalCreative\ConditionalContainer\ConditionalContainer) {
	$resource->setAttribute($field->attribute, $field->value);
	}
	}
	}

and see if it solves this issue?

[abishekrsrikaanth]

@milewski, do you want me to send you a PR?

[milewski]

If you were able to find the cause of the issue and have a fix for it please feel free to submit it 👍

[chosten]

Can confirm that adding this works.

!$field instanceof \Ebess\AdvancedNovaMediaLibrary\Fields\Media &&
!$field instanceof \Ebess\AdvancedNovaMediaLibrary\Fields\Files &&

[milewski]

Can you submit it as a PR @squarebeard ?

[chosten]

I could, but I'm actually using the flexible-content branch. Are you planning to merge that branch someday ?

[milewski]

... That branch has some bad performance issues... I don't know if it's possible to archive compatibility with the flexible-content field in a clean way ...

[chosten]

I did not notice any obvious performance drop.
Do you remember why ? Is it while saving or on the JS side maybe ?

[chosten]

Anyway here is the PR for the master branch. I've not tested it on that branch but i think there is no reason it would be different.