-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not for channels #2
Comments
@TELLO0815 I'm new to Sylius - I'm trying to make it work with baselinker plugin with multiple channels. Right now, at baselinker tester I get this response while trying to perform action Array
(
[[error](https://developers.baselinker.com/shops_api/index.php?tester=1&prod_id=error)] => 1
[[error_code](https://developers.baselinker.com/shops_api/index.php?tester=1&prod_id=error_code)] => 0
[[error_text](https://developers.baselinker.com/shops_api/index.php?tester=1&prod_id=error_text)] => Channel could not be found! Tip: You can use the Web Debug Toolbar to switch between channels in development.
) I assumed I must implement |
@TELLO0815 Not sure if I understand what is the issue. It is ok to use one key for all channels. If you want to use separate keys let me know. I can manage it. |
@jakublech I use the version I posted. Works fine ;-) |
@jakublech All my channels in table have |
Also channel is already set in DebugToolbar while I'm accessing any other endpoint. So sylius knows which one to use in other cases but baselinker tester for some reason gets this error with channel not found. |
My bad, I had |
@TELLO0815 So I assume you need to define separate baselinker password per channel? |
@jakublech Yes, to get a connection for multiple domain = channel. |
I think its easy to make it for channels available. I put the base linker key to the DB channel themselfe. If you create a channel, I think it must be there. So it runs simple for each channel, if you call the base linker-connector over other channel domain.
`use Spinbits\SyliusBaselinkerPlugin\Handler\HandlerInterface;
use Spinbits\SyliusBaselinkerPlugin\Rest\Exception\ForbiddenException;
use Spinbits\SyliusBaselinkerPlugin\Rest\Exception\InvalidArgumentException;
use Spinbits\SyliusBaselinkerPlugin\Rest\Exception\RestException;
use Spinbits\SyliusBaselinkerPlugin\Rest\Input;
use Spinbits\SyliusBaselinkerPlugin\Rest\Response;
use Spinbits\SyliusBaselinkerPlugin\Rest\ResponseError;
use Spinbits\SyliusBaselinkerPlugin\Rest\ResponseInterface;
use Exception;
use Sylius\Component\Channel\Context\ChannelContextInterface;
class RequestHandler
{
private const HANDLER_NOT_FOUND = 'Handler for action "%s" is not configured. Please use "setHandler" to map it.';
}`
<service id="Spinbits\SyliusBaselinkerPlugin\RequestHandler"> <argument key="$channelContext" type="service" id="Sylius\Component\Channel\Context\ChannelContextInterface"/> <call method="registerHandler"> <argument type="string">FileVersion</argument> <argument type="service" id="Spinbits\SyliusBaselinkerPlugin\Handler\FileVersionActionHandler" /> </call> .....
And Sylius admin channel as well.
The text was updated successfully, but these errors were encountered: