Skip to content

Commit 93a73ca

Browse files
committed
Merge branch '3.4' into 4.3
* 3.4: [SwiftMailer Spool] Fix double negative
2 parents 142bdaf + c6e3cba commit 93a73ca

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

email.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -564,11 +564,11 @@ interval.
564564
If you use the memory spool, this change is transparent and has no impact.
565565
But when using the filesystem spool, the message class is serialized in
566566
a file with the randomized class name. The problem is that this random
567-
class name changes on every cache clear. So if you send a mail and then you
568-
clear the cache, the message will not be unserializable.
567+
class name changes on every cache clear.
569568

570-
On the next execution of ``swiftmailer:spool:send`` an error will raise because
571-
the class ``Swift_Message_<someRandomCharacters>`` doesn't exist (anymore).
569+
So if you send a mail and then you clear the cache, on the next execution of
570+
``swiftmailer:spool:send`` an error will raise because the class
571+
``Swift_Message_<someRandomCharacters>`` doesn't exist (anymore).
572572

573573
The solutions are either to use the memory spool or to load the
574574
``swiftmailer`` service without the ``lazy`` option (see :doc:`/service_container/lazy_services`).

0 commit comments

Comments
 (0)