Ask a Question

REST API question: finding out if a user has subscribed to a page

Hello, I'm about to write a little Browser Add-On that hooks into the COYO web frontend with a button and allows to collect all the comments of a blog post. We need this because we offer raffles for all employees via a blog post and the employees need to make a comment below that post to be able to win. However, to be eligable the commenting users also need to follow our page. So I want to test for every commenter if he/she follows/has subscribed to our page. In the REST API documentation I found this endpoint: `/users/<user ID>/subscriptions?targetId=<ID of page>` However, this only seems to work for my own user ID. If I use a commenter's user ID I always get a "404" result. Now, because I'm writing a Browser Add-On here I'm "only" authenticated via my own user account agains the API (I'm getting the neccessary token for each REST API call from the `/web/authorization/token` endpoint; this works fine). Is there any way in this constellation to check if a user follows a page? Or is it by design that I can only check for my own subscriptions when using the REST API this way? Thanks, Stefan.

Detect user language preference

Is there any way using to get user environment language to set widget language accordingly ? (based on the twitter plugin there should be but I wasn't able to find it in the guides)

Change Widget content with REST API

Hi, I worked my way through the REST API, but I found no way to change the content inside a Widget, e.g. RichText Wiget or HTML Widget. Can you guys help me out, is this possible? Best Manuel

How to catch all links (that are colored with link color)?

Hello, in addition to the link color, we would like to underline all links that are only colored with the link color. Unfortunately, all `<a>` elements will be colored with the link color, including blog titles, wiki titles, etc. But these are overwritten by new classes. The problem now is that there is no class with which we can underline all links without selecting all `<a>` elements. To exclude the classes individually is inefficient and could become incosistent in the future (with new features from coyo). How to solve this? Just looking at the future (EU plans to make accessible websites mandatory) this is a highly important issue. Best regards, Moritz

Coyo Internal Storage

Greeting, Does Coyo has a internal storage (or cloud), where we can store plugin data? If it exists, could you please sent me a link to documentation? Best Regards!

Plug-in Sizing & White padding problem

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. To give you the explicit problems: - When visualizing the plug-in on the side panel of the platform, there is white padding around the iframe. We would like the iframe to have the full width of the panel, or at least reduce the padding to a minimum - Also, we would like to change the height of the side panel block, since currently the content of the plugin is limited by the panel size. Could someone help us with this? Thanks a lot.

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

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

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>

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"}`