Kim.Bertelsen

Hei, ja. Dette ser ut til ? skje hver gang. Har ikke testet med forskjellige type kupong-typer. Kun med rabattkupong som gir produktrabatt p? fixed sum.

Agreed, this was just an example. Thank you for planning to tag going forward.

For downloading older releases, yes, github would be possible. But it wouldnt solve the composer issue.

To elaborate:
Lets Say you have an old composer-based project laying around. WooCommerce is version 3.9.0 and vipps is something similarly old, lets Say 1.0.0. The composer.json has WooCommerce version locked to 3.9.0 and vipps plugin locked to 1.0.0

However, the reference to 1.0.0 source in composer.lock is not referencing a tagged release, its referencing trunk, since tags are missing.

If we (or other companies having similar workflow) make a single change in the repo of that project, that would trigger a composer install during deployment, which will download vipps as is from trunk. Without you knowing it, vipps is now at a potential 2 year newer version, while WooCommerce is still 2 year old. Something is bound to break at some point.

Actually it’s not in nginx logs, not in sentry, but shows up in Dynatrace wich we’re using currently to monitor some stuff.

Stacktrace:
throw(****/releases/949/content/plugins/wp-sentry-integration/build/vendor/php-http/discovery/src/Strategy/PuliBetaStrategy.php:37)
WPSentry\ScopedVendor\Http\Discovery\Exception\PuliUnavailableException.__construct(****/releases/949/content/plugins/wp-sentry-integration/build/vendor/php-http/discovery/src/Strategy/PuliBetaStrategy.php:37)
WPSentry\ScopedVendor\Http\Discovery\Strategy\PuliBetaStrategy.getPuliFactory(****/releases/949/content/plugins/wp-sentry-integration/build/vendor/php-http/discovery/src/Strategy/PuliBetaStrategy.php:57)
WPSentry\ScopedVendor\Http\Discovery\Strategy\PuliBetaStrategy.getPuliDiscovery(****/releases/949/content/plugins/wp-sentry-integration/build/vendor/php-http/discovery/src/Strategy/PuliBetaStrategy.php:69)
WPSentry\ScopedVendor\Http\Discovery\Strategy\PuliBetaStrategy.getCandidates(****/releases/949/content/plugins/wp-sentry-integration/build/vendor/php-http/discovery/src/ClassDiscovery.php:48)
WPSentry\ScopedVendor\Http\Discovery\ClassDiscovery.findOneByType(****/releases/949/content/plugins/wp-sentry-integration/build/vendor/php-http/discovery/src/MessageFactoryDiscovery.php:26)
WPSentry\ScopedVendor\Http\Discovery\MessageFactoryDiscovery.find(****/releases/949/content/plugins/wp-sentry-integration/build/vendor/sentry/sentry/src/ClientBuilder.php:267)
Sentry\ClientBuilder.createDefaultTransportFactory(****/releases/949/content/plugins/wp-sentry-integration/build/vendor/sentry/sentry/src/ClientBuilder.php:250)
Sentry\ClientBuilder.createTransportInstance(****/releases/949/content/plugins/wp-sentry-integration/build/vendor/sentry/sentry/src/ClientBuilder.php:227)
Sentry\ClientBuilder.getClient(****/releases/949/content/plugins/wp-sentry-integration/src/class-wp-sentry-php-tracker.php:179)
WP_Sentry_Php_Tracker.initializeClient(****/releases/949/content/plugins/wp-sentry-integration/src/class-wp-sentry-php-tracker.php:116)
WP_Sentry_Php_Tracker.get_client(****/releases/949/content/plugins/wp-sentry-integration/src/class-wp-sentry-php-tracker.php:56)
WP_Sentry_Php_Tracker.__construct(****/releases/949/content/plugins/wp-sentry-integration/src/class-wp-sentry-php-tracker.php:42)
WP_Sentry_Php_Tracker.get_instance(****/releases/949/content/plugins/wp-sentry-integration/wp-sentry.php:83)
include_once(****/releases/949/wp/wp-settings.php:377)
require_once(****/releases/949/wp-config.php:70)
require_once(****/releases/949/wp/wp-load.php:42)
require_once(****/releases/949/wp/wp-blog-header.php:13)
require(****/releases/949/index.php:16)

I need / want to pull it from the settings, so that it can be a reusable plugin for multiple clients. I had a feeling that it was the instance ID, but I haven′t figured out how to check what instance id is applied to a shipping method.