Announcement

Collapse
No announcement yet.

custom extension entity list view showing 404 error

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • custom extension entity list view showing 404 error

    Hi,

    Good day!

    I have a custom extension and I tried to create a new base entity with Entities, Repositories, Services, Controllers, etc. I also put the module name on the scope of the entity.

    On the clientDefs, I already attached the default controller
    Code:
    "controller": "controllers/record"
    My other entities worked but only this entity is failing. I am trying to added this new entity to the new version of my extension.

    But, it is showing Error 404 page, with error on the request as follows:

    /client/modules/mymodule/src/controllers/entity.js?r=1517359966
    It's looking for entity.js under my module even the controller in the clientDefs is the default controller.

    Any inputs would be appreciated.

    Thanks!

  • #2
    Hello
    Check if json is vald, clear cache

    Comment


    • #3
      Hi Tanya,

      My json is below for scope:

      Code:
      {
      "entity": true,
      "layouts": true,
      "tab": true,
      "acl": true,
      "aclPortal": true,
      "aclPortalLevelList": [
      "all",
      "account",
      "contact",
      "own",
      "no"
      ],
      "customizable": true,
      "importable": true,
      "notifications": true,
      "stream": false,
      "disabled": false,
      "type": "Base",
      "module": "MyModule",
      "object": true
      }
      I already clear cache from my local and the backend. Also done, rebuilding but still error is showing.

      Thanks!

      Comment


      • #4
        You share with a scope json, but I need clientDefs. The path to client controller it there

        Comment


        • #5
          Hi Tanya,

          Below is my clientDefs > MyEntity.json

          Code:
          {
          "controller": "controllers/record",
          "boolFilterList": [
          "onlyMy"
          ]
          }

          Comment


          • #6
            the path to file? also check custom path to file.
            open data/cache/application/metadata.json find clientDefs > YourEntity > controller

            Comment


            • #7
              Hi Tanya,

              @/application/Espo/Modules/mymodule/Resources/metadata/clientDefs/MyEntity.json

              Code:
               { "controller": "controllers/record", "boolFilterList": [ "onlyMy" ] }
              @/data/cache/application/metadata.php

              Code:
               'MyEntity' =>
                  array (
                     'controller' => 'controllers/record',
                    'boolFilterList' => array (
                      0 => 'onlyMy',
                    ),
                  ),

              @/custom/Espo/Custom/Resources/metadata/clientDefs/MyEntity.json

              No MyEntity.json file.

              Comment


              • #8
                Hi Tanya,

                Could this be considered as a bug report? Since, there are no defined controller specified for the module but rather in default controller and still it checks the module controller? Also, my other entities were working with same data but only this entity is not.

                Comment


                • #9
                  I can't reproduce it. Could you share with me this extension in PM? You can remove all, what works well.

                  Comment


                  • #10
                    Hi Tanya,

                    Sorry, the filename is not matched. It is MyEntity.json not MyEntitys.json.

                    Apologies for inconvenience. Thanks!

                    Comment

                    Working...
                    X