SeAT - thread: connector data is broken - Page 1

As reported here:https://discord.com/channels/821361165791133716/821361566184112181/1438545750765080606

it is broken for discord and qq driver

and teamspeak

To clarify: what's broken here? Are you referring to the api endpoints for connectors? Because the connectors seem to work fine

Yeah it's the API endpoints. Data is not returned to API properly so lots of nulls in instead of actual data

Yes, the responce is

{
  "data": [
    {
      "user_id": null,
      "connector_type": null,
      "connector_id": null,
      "connector_name": null
    },
    {
      "user_id": null,
      "connector_type": null,
      "connector_id": null,
      "connector_name": null
    },
    {
      "user_id": null,
      "connector_type": null,
      "connector_id": null,
      "connector_name": null
    },
    {
      "user_id": null,
      "connector_type": null,
      "connector_id": null,
      "connector_name": null
    },
    {
      "user_id": null,
      "connector_type": null,
      "connector_id": null,
      "connector_name": null
    },
    {
      "user_id": null,
      "connector_type": null,
      "connector_id": null,
      "connector_name": null
    }
  ],

A quick followup on this, it seems fixed when I modified these lines: https://github.com/zenobio93/seat-connector/blob/3.0.x/src/Http/Resources/UserResource.php#L78

from

        return [
            'user_id'        => $this->user_id,
            'connector_type' => $this->connector_type,
            'connector_id'   => $this->connector_id,
            'connector_name' => $this->connector_name,
        ];

to

    return [
        'user_id'        => $this->resource->user_id,
        'connector_type' => $this->resource->connector_type,
        'connector_id'   => $this->resource->connector_id,
        'connector_name' => $this->resource->connector_name,
    ];

https://github.com/zenobio93/seat-connector/pull/7 pull request is created @user_301981661761896449 could you have a review?

@user_614098468218339348 , could you give a review?

also @user_171582310783647744 pinged

Just tested it, seems to work. You can clean it up some more, the variables in the class aren't used. Also I've fixed the issue where it displays the wrong api url: https://github.com/recursivetree/seat-connector/commits/fixes/

feel free to cherry-pick the commits

Hi @user_614098468218339348 , I saw the Commits on Nov 24, 2025, they have been merged into the forked branch, could you help to merge into the branch under the plugin repo?

@user_614098468218339348 just a gental ping, could we push it to the repo?

I can’t commit to zenobios repository

ok, if I want to pick up these commits for my docker, how should I modify it, is it written somewhere? packages.yml?

pick thess commits from your fork, recursivetree/seat-connector

I can’t do that either, I don’t have access to your fork

sry for the confusion, I meant the deployment

for the plugin, I just need modify .env like this SEAT_PLUGINS=hermesdj/seat-calendar,recursivetree/seat-transport,cryptatech/seat-prices-janice,feibam/seat-qq-connector,warlof/seat-discord-connector But does this work for seat-connector ?

I'm still a bit confused. What do you want? Install the contents of the pull request on your production server? You can do that the same way you install it in your development environment

solved, thanks