This commit removes a reference to the minimum required PHP version (which is presumably outdated as it mentions PHP 5.6) from the MailPoet API documentation.
I'm assuming that the minimum required version to use the API is the same as the one to run MailPoet. If that is the case, I don't see a reason to mention it in the API documentation, and removing it has the benefit of reducing the maintenance burden when the minimum required version is updated.
The .env.sample file contained a few comments using `//`. The problem is
that `//` is not supported by vlucas/phpdotenv and this was resulting in
the following fatal error when following the dev environment setup
instructions and running `./do install`:
```
ERROR: Uncaught Dotenv\Exception\InvalidFileException: Failed to parse dotenv file due to unexpected whitespace. Failed at ["" // URL of your site (used for multisite env and equals to DOMAIN_CURRENT_SITE from wp-config.php)]. in /srv/www/mailpoet/public_html/wp-content/plugins/mailpoet/vendor/vlucas/phpdotenv/src/Parser.php:148
```
To fix this problem, this commit replaces all instances of `//` in
.env.sample with the `#` (see
https://github.com/vlucas/phpdotenv#comments).
Quick test show that `//` doesn't work and `#` does:
```
>>> Dotenv\Dotenv::parse("FOO=Bar // some comment")
Dotenv\Exception\InvalidFileException with message 'Failed to parse dotenv file. Encountered unexpected whitespace at [Bar // some comment].'
>>> Dotenv\Dotenv::parse("FOO=Bar # some comment")
=> [
"FOO" => "Bar",
]
```
Commit d143cd20d1 added composer.phar to the root directory of the plugin apparently by mistake as nothing about composer is mentioned in the commit message or the related issue. We use a copy of composer.phar that lives in `tools/vendor/composer.phar`, so I'm assuming there is no reason to have another copy on the root directory.
This commit updates the README.md file and bumps the PHP version required to run the development environment to PHP >= 7.3 and add a note informing that the requirements to just run the plugin are different.
This commit removes docker and docker compose as requirements to run Mailpoet. They are only required to run the acceptance tests and not the plugin itself.
When using a subscription form as an iframe, our CSP catched up that the reCAPTCHA API was included despite MailPoet being configured to use its internal CAPTCHA. The following change will only output the relevant <script> tag when MailPoet uses reCAPTCHA.
Test was flaky because by default sorting is done using created_at and all users have the same.
Fixed by reordering subscribers by email.
[MAILPOET-3365]
