You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -19,18 +19,6 @@ is fully unit tested, and even comes with an example application to get you star
19
19
* Because most payment gateways have exceptionally poor documentation
20
20
* Because you are writing a shopping cart and need to support multiple gateways
21
21
22
-
**Important Note: Compatibility with Symfony 3 Event Dispatcher**
23
-
24
-
If you are using Symfony 3 (or Symfony 3 components), please note that Omnipay 2.x still relies on Guzzle3, which in turn depends on symfony/event-dispatcher 2.x. This conflicts with Symfony 3 (standard install), so cannot be installed. Development for Omnipay 3.x is still in progress at the moment.
25
-
26
-
If you are just using the Symfony 3 components (eg. stand-alone or Silex/Laravel etc), you could try to force the install of symfony/event-dispatcher:^2.8, which is compatible with both Symfony 3 components and Guzzle 3.
27
-
28
-
```
29
-
composer require symfony/event-dispatcher:^2.8
30
-
```
31
-
32
-
**Please do not submit any more issues or pull requests for updating Omnipay from Guzzle 3 to GuzzleHttp. The update is going to happen in Omnipay version 3.0 which is not yet ready for release.**
33
-
34
22
## TL;DR
35
23
36
24
Just want to see some code?
@@ -65,7 +53,8 @@ Omnipay is a collection of packages which all depend on the
65
53
[omnipay/common](https://github.com/thephpleague/omnipay-common) package to provide
66
54
a consistent interface. There are no dependencies on official payment gateway PHP packages -
67
55
we prefer to work with the HTTP API directly. Under the hood, we use the popular and powerful
68
-
[Guzzle](http://guzzlephp.org/) library to make HTTP requests.
56
+
[PHP-HTTP](http://docs.php-http.org/en/latest/index.html) library to make HTTP requests.
57
+
A [Guzzle](http://guzzlephp.org/) adapter is required by default, when using `omnipay/omnipay`.
69
58
70
59
New gateways can be created by cloning the layout of an existing package. When choosing a
71
60
name for your package, please don't use the `omnipay` vendor prefix, as this implies that
@@ -76,20 +65,26 @@ payment library, a good name for your composer package would be `santa/omnipay-g
76
65
77
66
## Installation
78
67
79
-
Omnipay is installed via [Composer](https://getcomposer.org/). For most uses, you will need to require an individual gateway:
68
+
Omnipay is installed via [Composer](https://getcomposer.org/).
69
+
For most uses, you will need to require `omnipay/omnipay` and an individual gateway:
80
70
81
71
```
82
-
composer require omnipay/paypal:~2.0
72
+
composer require omnipay/omnipay omnipay/paypal
83
73
```
84
74
85
-
To install all officially supported gateways:
75
+
If you want to use your own HTTP Client instead of Guzzle (which is the default for `omnipay/omnipay`),
76
+
you can require `omnipay/common` and any `php-http/client-implementation` (see [PHP Http](http://docs.php-http.org/en/latest/clients.html))
0 commit comments