From c5d5379c492059a80eb72cc1dab148dd6e82705f Mon Sep 17 00:00:00 2001
From: Molkobain <lajarige.guillaume@free.fr>
Date: Tue, 16 Aug 2022 14:21:28 +0200
Subject: [PATCH] =?UTF-8?q?N=C2=B05408=20-=20Mentions:=20Fix=20empty=20res?=
 =?UTF-8?q?ults=20for=20class=20with=20no=20image=20attribute?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 pages/ajax.render.php | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/pages/ajax.render.php b/pages/ajax.render.php
index 1c1f2f0f4..ff255bb96 100644
--- a/pages/ajax.render.php
+++ b/pages/ajax.render.php
@@ -2539,7 +2539,12 @@ EOF
 				);
 
 				$oSet = new DBObjectSet($oSearch, [], $aSearchParams);
-				$oSet->OptimizeColumnLoad([$oSearch->GetClassAlias() => [$sObjectImageAttCode]]);
+				// Optimize fields to load
+				$aObjectAttCodesToLoad = [];
+				if (MetaModel::IsValidAttCode($sSearchMainClassName, $sObjectImageAttCode)) {
+					$aObjectAttCodesToLoad[] = $sObjectImageAttCode;
+				}
+				$oSet->OptimizeColumnLoad([$oSearch->GetClassAlias() => $aObjectAttCodesToLoad]);
 				$oSet->SetLimit(MetaModel::GetConfig()->Get('max_autocomplete_results'));
 				// Note: We have to this manually because of a bug in DBSearch not checking the user prefs. by default.
 				$oSet->SetShowObsoleteData(utils::ShowObsoleteData());