The field type "xxx" does not exist

Kirby 3 Solved ✅
,
21

i’m running debian 9, i suppose yes? :upside_down_face:

22

:woman_shrugging:

23

would it make it a difference if i do a fresh install of kirby directly on the server and then i do a composer install of the composer.json file coming with kirby 3?

eg there might be some package missing on the server… even though kirby is running fine, it’s only the plugin not showing up on the panel.

24

I was mistaken, the symlink is created for plugin assets, not for the index.js files. The index.js file is supposed to be delivered via this route in /kirby/config/routes.php:

    [
            'pattern' => $media . '/plugins/index.(css|js)',
            'env'     => 'media',
            'action'  => function (string $type) use ($kirby) {
                $plugins = new PanelPlugins();

                return $kirby
                    ->response()
                    ->type($type)
                    ->body($plugins->read($type));
            }
        ],
26

what’s the url kirby needs to access for the plugins? because maybe the problem lies in my nginx config file.

27

The URL shown in the error message.

28

this was the culprit

location ~* \.(svg|js|css|png|jpg|jpeg|gif|ico|woff|woff2|ttf|eot)$ {
  expires 1y;
}

some lingo left from the kirby nginx config i found a few years ago (:

29

You might find this useful: Enabling leverage caching on nginx causes panel problems

1 Like
30

I tried with the settings described in the linked thread, without success. Error message (index.js) still the same, custom fields still ‘not existing’ - how can I leverage caching on NGINX then? :S