Ok, been lots of mucking around but guess it needed to happen. I’d imagine quite a few patch releases coming out so keep an eye. https://github.com/silvershop/silvershop-core/releases/tag/3.0.0
the shipping module is just really the barebones of providing the apis and you’ll need to hook that up to whatever you need to actually power it.
@Dave Collins I haven’t done any UPS integration but yes unless you can find something via search it probably doesn’t exist
Stripe all the way, PHP api for that is easy enough to understand without the Omnipay middle man.
Any smart way to debug why
readOneElementalArea is just a null response rather than the object? ID exists in the database
@bummzack has previously done all the reasons but I think major lack of time investment from either of us to run through and check anything major. But see no reason why we couldn’t do
hey @bummzack I saw you have a discussion with Dan RE the i18n test manifest (rait ‘SilverStripe\i18n\Tests\i18nTestManifest’ not found silverstripe-omnipay/tests/GatewayInfoTest.php). Did that discussion lead to any direction - I can PR framework to get that file moved into the dev namespace or I guess need to replace the use of that file?
composer install --prefer-source doesn’t seem to restore it.
Can’t remember. I thought prefer-source solved the issue... I think I had to clear the composer cache for it to take effect
Ha! true. Ala node