Discussions

Greeting,

We are currently working on developing a plugin for COYO.
As it should be addable to the different panels (e.g. small side panel, middle panel etc.) of the platform, we experienced some problems with sizing and padding.

Hi there,
I just noticed something strange. I've tried to implement the new configuration view in our plugin which worked pretty good. But I couldn't get the plugin adapter to connect to COYO. I only get ERR6. I tried to debug and found out, that the src query parameter holds 2 UUID's joined with another dash like symbol '-' in between. So it looked something like this:
src param: ef956c74-XXXX-XXXX-XXXX-a4ed02c3d60d-5561ead0-YYYY-YYYY-YYYY-017907e2855c
id 1: ef956c74-XXXX-XXXX-XXXX-a4ed02c3d60d
id 2: 5561ead0-YYYY-YYYY-YYYY-017907e2855c

Hi there,
I tried to implement the new configuration view via configUrl into our plugin, but our instance of COYO refuses to accept the new manifest version. Is there any chance we can get access to the beta version of COYO so we can test the new view b4 it goes live? Or is there any other way we can do tests?

Every now and then I stumble over a problem and I'm unsure if it's on my project or maybe on the library I'm using. I like to get rid of my code and build a minimal reproduction example by using the library on its own. Often enough doing this I discover my mistake. If not, I like to share the minimal reproduction example and like to have it easy to consume. My question: Can I use the plugin adapter from a CDN or without using a local build setup?

My Plugin initialization fails when serving from server. No issue during local development, serving via ngrok.

My plug-in receives an error code "ERR7" when loading the custom plug-in certificate. What could be the reason?

When trying to install a new plugin, it is only successful if we remove the section 'lifecycle' from the manifest. The failure must happen somewhere between the GET request for the manifest and the POST request for the 'install' endpoint.

Hello,

We can add any number of configuration fields and there are f.e. textarea type fields which could contain excessive amount of text.
All those values will make it into the JWT that get sent thru the message-api / plugin-adapter.