Discussions
Double src id
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
ID 1 and 2 are valid UUID's while the src param isn't. It would be nice to know, if this is the new default behavior for the source ID and which ID I would need to init the plugin adapter with.
Best regards
Chief
Posted by Chris Langenberg about 3 years ago
New Configuration View
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?
Greetings
Chief
Posted by Chris Langenberg about 3 years ago
Possible to use pluginAdapter without building
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?
Things I tried:
<script type="module">
import { PluginAdapter } from "https://unpkg.com/@coyoapp/[email protected]/build/module/lib/plugin-adapter.js";
// Failed to resolve module specifier "jwt-decode"
</script>
---
<script type="module">
import { PluginAdapter } from "https://unpkg.com/@coyoapp/[email protected]/build/module/lib/plugin-adapter.js";
// Failed to resolve module specifier "core-js/features/promise/any"
</script>
---
<script src="https://unpkg.com/@coyoapp/[email protected]/build/main/index.js"></script>
// Uncaught ReferenceError: exports is not defined
</script>
Posted by Lars Kreisz about 3 years ago
PluginError: Initialization timed out (ERR6)
My Plugin initialization fails when serving from server. No issue during local development, serving via ngrok.
The Bundle is loaded, react execution starts (I get displayed our loading screen), but the call to `await pluginAdapter.init()` never returns and after 60.000ms I get `PluginError: Initialization timed out (ERR6)`
```
$ console.log(pluginAdapter)
> { srcId: "", jwkStore: {}, initAdapter: {}, editAdapter: {}, heightAdapter: {} }
```
We host the plugin at `coyo.domain.com` and the manifest at `coyo.domain.com/manifest.json`.
When running the same `git HEAD` locally and serving it through `coyo-test.eu.ngrok.io`, the plugin init's successfully.
But here the same `console.log` returns {`srcId: "295ca469-300e-43bd-81d3-09d1cb7cb387"}`
Posted by Finn about 3 years ago
Plug-in cannot load custom certificate
My plug-in receives an error code "ERR7" when loading the custom plug-in certificate. What could be the reason?
Posted by Fynn Feldpausch about 3 years ago
Why is the following manifest containing lifecycle endpoints not accpeted?
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.
In our plugin backend logs we can see the following:
POST /lifecycle/install 415 Unsupported Media Type
GET /manifest 200 OK
And inside the browser logs we get
{"errorStatus":"INVALID_RESPONSE","requestUri":"/web/plugins/manage","timestamp":1627294735804,"context":{"source":"PLUGIN"},"message":"Expected JSON"}
BUT: The response header in our 'install' endpoint is clearly set to 'content-type: application/json. So we do not understand why the error message is "Expected JSON".
Posted by Alexander Voigt about 3 years ago
Previously working widget now returning invalid plugin token (Err 2)
Hello,
I have had a widget up and hosted for about a month now and it has been working flawlessly. I've not touched the code for it, but despite this it has stopped working and suddenly returns an error instead.
When loading a page hosting the widget the widget now says "Invalid plug-in token (ERR2)"
And the terminal states a very similar problem, but with slightly more detail referring to JWT.
https://i.imgur.com/AsxQpkn.png
Any help would be appreciated.
Posted by Cameron Shaun Taljaard about 3 years ago
Is there a maximum overall configuration size?
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.
Do you know of an overall size limitation?
(Asking for a friend who plans to put 1mb into a textarea field :)
Posted by Lars Kreisz over 3 years ago
How to update manifest and keeping existing widget?
Every now and then I like to update my plugin and f.e. add a feature that needs a new configuration field.
Is there a way to update the existing plugin without adding a new copy? I like to keep all the existing widgets throuout the COYO instance.
Posted by Lars Kreisz over 3 years ago
Access config in entryPoint request
My`manifest.json` defines a text config `url` and an entry point.
The entry point is called, but the `url` parameter is nowhere in the request.
I am using `koa`.
Is it exclusively accessible inside the plugin?
Posted by Finn over 3 years ago