The documentation of shopify APIs is pretty good. Unfortunately I failed miserably to authenticate – and this is because from my point of view the naming of the PHP client is wrong – at least for private apps.
Big shout out to Fatih Samur whos blog entry helped me a lot!
This is the app info for private apps in the backend.
Context::initialize(
$_ENV['SHOPIFY_API_KEY'],
$_ENV['SHOPIFY_API_SECRET'],
$_ENV['SHOPIFY_APP_SCOPES'],
$_ENV['SHOPIFY_APP_HOST_NAME'],
new FileSessionStorage('/tmp/php_sessions'),
'2021-04',
true,
false,
);
And this is the code example of the shopify php client.
$_ENV['SHOPIFY_API_KEY'], // => API-Schlüssel (the value in the middle)
$_ENV['SHOPIFY_API_SECRET'], // => TOKEN(!!) NOT THE SECRET!
$_ENV['SHOPIFY_APP_SCOPES'], // => Whatever you defined, comma separated.
$_ENV['SHOPIFY_APP_HOST_NAME'], // => your host without https:// and / as suffix.Hope that helps someone in the future.
The examples are from Shopware 6.5.6.1. Today I debugged code with my colleague Bruno. We had the problem, that our Subscriber triggers, but at the wrong moment. As Shopware developers, we often implement our subscribers using the eventClass. This method is commonly used „everywhere“ … Well, not entirely… One small village of indomitable Gauls still […]
I had the pleasure to give a workshop today at the Shopware Community Day 25 in Cologne. To not forget it, here are the slides: And here is the repository with the current code: https://bitbucket.org/winkelwagen/deployer-pub/src/sw-workshop/ If you have any questions, feel free to comment and I’ll update the blog post!
If your bitbucket shell runner is doing weird stuff, you might have started the runner two times – in my case under different users (root + winkelwagen) and therefore it didn’t show up when looking for the screen.
Schreibe einen Kommentar