From c3cfee7b2c8bdfe72426f6fba0889a76d4adff35 Mon Sep 17 00:00:00 2001
From: Warren Buckley <warren@umbraco.com>
Date: Wed, 12 Sep 2018 11:33:19 +0100
Subject: [PATCH] Need to use the EscapleLikeExpression method instead for the
 fallback check

---
 src/Umbraco.Core/Logging/Viewer/LogViewerSourceBase.cs | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/src/Umbraco.Core/Logging/Viewer/LogViewerSourceBase.cs b/src/Umbraco.Core/Logging/Viewer/LogViewerSourceBase.cs
index 6fffb52482..08a19ec202 100644
--- a/src/Umbraco.Core/Logging/Viewer/LogViewerSourceBase.cs
+++ b/src/Umbraco.Core/Logging/Viewer/LogViewerSourceBase.cs
@@ -54,16 +54,15 @@ namespace Umbraco.Core.Logging.Viewer
             if (string.IsNullOrEmpty(filterExpression) == false)
             {
                 Func<LogEvent, bool> filter = null;
-
+                
                 // If the expression evaluates then make it into a filter
-                // TODO: Why does any single word evaluate?
                 if (FilterLanguage.TryCreateFilter(filterExpression, out Func<LogEvent, object> eval, out string error))
                 {
                     filter = evt => true.Equals(eval(evt));
                 }
                 else // assume the expression was a search string and make a Like filter from that
                 {
-                    var filterSearch = $"@Message like '%{FilterLanguage.EscapeStringContent(filterExpression)}%'";
+                    var filterSearch = $"@Message like '%{FilterLanguage.EscapeLikeExpressionContent(filterExpression)}%'";
                     if (FilterLanguage.TryCreateFilter(filterSearch, out eval, out error))
                     {
                         filter = evt => true.Equals(eval(evt));