After upgrade to 9.3.0 – Detail View not opening for some entities

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Paulina
    Member
    • Feb 2022
    • 52

    #1

    After upgrade to 9.3.0 – Detail View not opening for some entities

    Hello,

    After updating EspoCRM to version 9.3.0, I am unable to open the Detail View for some entity records (for example, SalesOrder). The page does not load properly.

    In the browser console I see the following errors:
    Click image for larger version  Name:	image.png Views:	0 Size:	49.8 KB ID:	124689

    It seems that jQuery.js cannot be loaded from:
    Code:
    client/lib/transpiled/src/jQuery.js

    The server returns a 404 error, and then the UI crashes.

    When I checked the file system, I noticed that the folder:
    Code:
    client/lib/transpiled/
    does not exist at all.

    ​Some additional details:
    • The issue happens only for certain entities (e.g. SalesOrder, Template).
    • Other parts of the system work normally.
    • Cache was cleared and rebuild was executed.
    • The system was updated from 9.1.8 version to 9.3.0.
    ​Does anyone know what the problem is here and how to fix it? Any guidance would be appreciated. Thank you.
    Last edited by Paulina; 02-12-2026, 08:35 AM.
  • heint
    Member
    • Jun 2025
    • 68

    #2
    Greetings, Paulina,

    As the most common troubleshooting method here, I would recommend uninstalling all custom extensions you might have, and the same with reviewing all code customization for the problematic entities.

    If the updating process without the mentioned customization parts will not fix the problem, please enable debug mode to see more details for the potential resolving of this issue.

    Comment

    • shalmaxb
      Senior Member
      • Mar 2015
      • 1843

      #3
      You won`t find the mentioned folder in the transpiled path. Transpiling is used in javascript to translate older code to newer code, which happens internally (I admit, quite rough explanation). What heint recommends, is true. Mostly these kind of errors com from third party extensions or other custom code.
      Outdated extensions happen to not work anymore, if they are not adapted to newer code.

      Comment

      • yuri
        EspoCRM product developer
        • Mar 2014
        • 9656

        #4
        Could be an extension using some library that requires 'jQuery' as an AMD module. There were not significant changes in the frontend in the latest version. I don't know why this error occurred only now. Maybe the extension tries to load 'jQuery' too early.

        Comment

        Working...