barryvdh / laravel-omnipay Goto Github PK

when i try to vendor:publish givin me this error

"Unable to locate publishable resources."

Hi Barry,

Do you have any plans to support laravel 6 with this package?

@barryvdh are ur going to support l 5.6?

I don't see a reason why is this not supported by Laravel 5.2

I want to use your package on my Laravel Spark SAAS project. is it possible???

I tried to install laravel-omnipay via composer :composer require barryvdh/laravel-omnipayI get :

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Conclusion: remove symfony/event-dispatcher v3.2.4
    - Conclusion: don't install symfony/event-dispatcher v3.2.4
    - omnipay/common 2.4.0 requires guzzle/guzzle ~3.9 -> satisfiable by guzzle/guzzle[v3.9.0, v3.9.1, v3.9.2, v3.9.3].
    - omnipay/common 2.5.2 requires guzzle/guzzle ~3.9 -> satisfiable by guzzle/guzzle[v3.9.0, v3.9.1, v3.9.2, v3.9.3].
    - omnipay/common v2.3.4 requires guzzle/guzzle ~3.9 -> satisfiable by guzzle/guzzle[v3.9.0, v3.9.1, v3.9.2, v3.9.3].
    - omnipay/common v2.4.1 requires guzzle/guzzle ~3.9 -> satisfiable by guzzle/guzzle[v3.9.0, v3.9.1, v3.9.2, v3.9.3].
    - omnipay/common v2.5.0 requires guzzle/guzzle ~3.9 -> satisfiable by guzzle/guzzle[v3.9.0, v3.9.1, v3.9.2, v3.9.3].
    - omnipay/common v2.5.1 requires guzzle/guzzle ~3.9 -> satisfiable by guzzle/guzzle[v3.9.0, v3.9.1, v3.9.2, v3.9.3].

is this need to require the gateway package in composer beside your package or not
when i set testmode to false this is error response haven't redirect ....
when i set it to true the record back with success but the transaction didn't save in sand box transaction or the funds effect this is any reason hear is my code

use Omnipay;

public function getApiInfos() {
  return array(
    'cancelUrl' => URL::route('paypal_response'),
    'returnUrl' => URL::route('success_paypal_response'),
    'amount'    => '50.00',
    'currency'  => 'USD',
    'description' => '#description'
  );
}



public function upgrade_acount_processing()
{

// make paypal payment

$gateway = Omnipay::gateway('PayPal_Express');
    $gateway->setUsername('xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx');
    $gateway->setPassword('xxxxxxxxxxxxxxxxx');
    $gateway->setSignature('xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx');
    $gateway->setTestMode(true);

    $response = $gateway->purchase($this->getApiInfos())->send();
    return $response->redirect();
}

GatewayManager, line 50:

if(!isset($this->gateways[$class])){
            $gateway = $this->factory->create($class, null, $this->app['request']);
            $gateway->initialize($this->getConfig($class));
            $this->gateways[$class] = $gateway;
        }

The config gets checked for the classname instead of the gateways name. I think it should be:

if(!isset($this->gateways[$class])){
            $gateway = $this->factory->create($class, null, $this->app['request']);
            $gateway->initialize($this->getConfig($gateway->getName()));
            $this->gateways[$class] = $gateway;
        }

That way, I can pass a custom gateway without having to use the fully qualified name of the class on the config file...

Am I correct?

Thanks

Class '\Omnipay\FirstData\PayeezyGateway' not found

composer require barryvdh/laravel-omnipay
Using version ^0.2.2 for barryvdh/laravel-omnipay
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

Problem 1
- Installation request for barryvdh/laravel-omnipay ^0.2.2 -> satisfiable by barryvdh/laravel-omnipay[v0.2.2].
- Can only install one of: guzzlehttp/guzzle[6.5.x-dev, 7.0.1].
- Can only install one of: guzzlehttp/guzzle[7.0.1, 6.5.x-dev].
- Can only install one of: guzzlehttp/guzzle[6.5.x-dev, 7.0.1].
- Conclusion: install guzzlehttp/guzzle 6.5.x-dev
- Installation request for guzzlehttp/guzzle (locked at 7.0.1, required as ^7.0.1) -> satisfiable by guzzlehttp/guzzle[7.0.1].

Installation failed, reverting ./composer.json to its original content.

I downgraded and it required to install Laravel 7.

Hi,

I tried to install laravel-omnipay via composer : composer require barryvdh/laravel-omnipay I get :

  Problem 1
    - Installation request for barryvdh/laravel-omnipay ^0.1.2 -> satisfiable by barryvdh/laravel-omnipay[v0.1.2].
    - Conclusion: remove laravel/framework v5.4.9
    - Conclusion: don't install laravel/framework v5.4.9
    - barryvdh/laravel-omnipay v0.1.2 requires illuminate/support 5.0.* || 5.1.* || 5.2.* || 5.3.* -> satisfiable by illuminate/support[v5.0.0, v5.0.22, v5.0.25, v5.0.26, v5.0.28, v5.0.33, v5.0.4, v5.1.1, v5.1.13, v5.1.16, v5.1.2, v5.1.20, v5.1.22, v5.1.25, v5.1.28, v5.1.30, v5.1.31, v5.1.41, v5.1.6, v5.1.8, v5.2.0, v5.2.19, v5.2.21, v5.2.24, v5.2.25, v5.2.26, v5.2.27, v5.2.28, v5.2.31, v5.2.32, v5.2.37, v5.2.43, v5.2.45, v5.2.6, v5.2.7, v5.3.0, v5.3.16, v5.3.23, v5.3.4].
    - don't install illuminate/support v5.1.1|don't install laravel/framework v5.4.9
    - don't install illuminate/support v5.1.13|don't install laravel/framework v5.4.9
....

Please make a new release with laravel 8 supporting.

I'm using Sessions to store the item data. However when user returns to site from Paypal, my sessions will be destroyed.. It's not a url problem (www)..

Can you say something about that?

Hey Barry,

I'd like to use your package with laravel 5.5 and hopefully 5.6 very quicky, but there doesn't seem to be a stable version for 5.5 yet.

Is it possible to tag the current dev version or are there some things not working correctly yet?

Gr,
Ezra

I'm just curious, it seems that ignited's version existed (slightly) before yours, and doesn't seem that this is a branch of ignited/omnipay, but seems to have similar functionality.

Both are a couple years old, and are still being updated with the laravel versions.

So, I'm curious what the differences are / reason for creating a separate package. I've been working with laravel for a couple years now, and am a big fan of your work. I'd honestly rather depend on your package if there were reason to.

Please make a new release for laravel 9 supporting. Someone already added support, but it's not tagged yet @barryvdh.

Hello Barry,

Will there be an update for Laravel 10?