Bug: Strapi 5 fails with plugin rest cache and custom fields in schema

[PidginEnemy]

Hello, i found a bug in new version of this plugin, to demonstate this i created basic example on clear new strapi with plugin-rest-cache and one custom field in schema.
New config:

strapi: 5.29.0
@strapi-community/plugin-redis: 2.0.0
@strapi-community/plugin-rest-cache: 5.0.1
@strapi-community/provider-rest-cache-redis: 5.0.0 

When i started strapi project in development mode, after few seconds strapi fails with error: Error: Could not find Custom Field: ..... If i delete custom field from schema everything is okay. On old strapi 4 and old version of this plugin no errors occured with the same case.
Old config:

strapi: 4.25.23
strapi-plugin-redis: 1.1.0
strapi-plugin-rest-cache: 4.2.9
strapi-provider-rest-cache-redis: 4.2.9

Please, see my exaple: https://github.com/PidginEnemy/strapi5-rest-cache-bug

[jonloh]

I've encountered the same issue too with Color Picker plugin

[Nirbhay007]

I am facing the similar issue. Any update on this?

[Nirbhay007]

Error: Could not find Custom Field: plugin::ckeditor5.CKEditor

It's happening with CKEditor in my case.

[PidginEnemy]

It's happening with any custom field, color picker is just for example.I can't figure out the reason for this error yet.

[derrickmehaffy]

I doubt that rest cache would have anything to do with other custom fields, can you provide the entire error stack trace?

[derrickmehaffy]

I doubt that rest cache would have anything to do with other custom fields, can you provide the entire error stack trace?

[kyujin-cho]

Apparently the issue is raised by flattenRoutes calling strapi.api without all other plugins loaded (ref). I was able to get around with the issue by manipulating strapi plugin loading mechanism to force load plugin::rest-cache at the end, like:

            const moduleNames = Array.from(Object.keys(modules)).filter(x => x != "plugin::rest-cache");
            if (modules["plugin::rest-cache"] != undefined) moduleNames.push("plugin::rest-cache");
            for (const modName of moduleNames) {
                const mod = modules[modName]
                await mod.register();
            }

[Nirbhay007]

Apparently the issue is raised by flattenRoutes calling strapi.api without all other plugins loaded (ref). I was able to get around with the issue by manipulating strapi plugin loading mechanism to force load plugin::rest-cache at the end, like:

        const moduleNames = Array.from(Object.keys(modules)).filter(x => x != "plugin::rest-cache");
        if (modules["plugin::rest-cache"] != undefined) moduleNames.push("plugin::rest-cache");
        for (const modName of moduleNames) {
            const mod = modules[modName]
            await mod.register();
        }

Did you do patchDependency over strapi/core in your package json?

[derrickmehaffy]

Plugins should be loaded in the order defined in your plugin config file, can you try moving rest cache to the end?

[boazpoolman]

I believe this has something to do with the fact that we're injecting our route middlewares during the regiter phase of the plugin. Once we get the routes from the strapi.apis global, it will validate the schema from within Strapi core. If the custom field hasn't been registered yet, we're seeing this issue.

Wondering if the order manipulation that Derrick suggested will solve this, I guess it should.

Apart from that, there is open issue about this on the Strapi repo: strapi/strapi#24394