Announcement

Collapse
No announcement yet.

Global search no longer possible after update to 7.5.1

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    Global search no longer possible after update to 7.5.1

    Hello all,

    I updated to 7.5.1 today via CLI. Everything was done without any error messages.

    But now I have noticed that the global search in the header no longer works.
    Something is displayed with the fonts. -> see screenshot

    In addition, "Error 500" is displayed in the upper area.​
    1 Photo
    Tags: None
  • #2
    I updated to 7.5.1 also but do not have the issue. So it seems its not a general issue.

    Comment

    • #3
      Hi,
      have you try clear cache browser ?
      i have updated 2 develop instance without any issue.

      Comment

      • #4
        I have cleared the browser cache.
        I have cleared the cache in EspoCRM.
        I restored the backend.
        I have uninstalled all extensions as a test.
        I have used a standard template.

        All without success. The error still occurs.​
        • Likes 1

        Comment

        • #5
          Can you check EspoCRM logs?

          Comment

          • #6
            Damn, I hadn't even thought of that.
            An error message immediately jumped out at me and I knew where the error was.
            The error 500 had nothing to do with the update.
            I had deleted a field from an entity that was no longer needed. However, I had specified this in the entity's settings under text filter fields. I deleted it and it worked again.
            Put it on the list immediately -> check the logs first.​
            • Likes 2

            Comment

            • Kharg
              #6.1
              Kharg commented
              06-13-2023, 08:20 PM
              Editing a comment
              Glad that you solved your issue
            • ChrisSka83
              #6.2
              ChrisSka83 commented
              06-13-2023, 08:33 PM
              Editing a comment
              Kharg But I still get the messages with the fonts.
            • espcrm
              #6.3
              espcrm commented
              06-14-2023, 06:47 AM
              Editing a comment
              Life become good once there no more error when you upgrade.
          • #7
            Ah, I have the same error message in Firefox.You only see it in the browser console.

            If you search the net for "was preloaded using link preload but not used within a few seconds from the window's load event" you will find lots of posts about these kind of error/warning.

            I found this older post. Not sure how valid it still is.

            Preload: What Is It Good For? — Smashing Magazine
            https://www.smashingmagazine.com/2016/02/preload-what-is-it-good-for/#early-loading-of-fonts
            What is that preload? What does it do? And how can it help you? Preload gives developers the ability to define custom loading logic without suffering the performance penalty that script-based resource loaders incur. In human terms, it’s a way to tell a browser to start fetching a certain resource, because you as authors know that the browser is going to need that particular resource pretty soon.


            Last edited by ThomasB; 06-13-2023, 09:36 PM.
            • Likes 1

            Comment

            • ChrisSka83
              #7.1
              ChrisSka83 commented
              06-13-2023, 09:42 PM
              Editing a comment
              It doesn't bother me and it doesn't affect the use of EspoCRM.
              I just didn't know whether it would be considered a mistake or not.
              I only came across it because of the problem above.
          Previous template Next
          Working...
          X