Currently, Airmail uses Civi::cache() for settings, mailing IDs and mailing jobs. On a multi-site, the last two are the same across domains, but settings are per-site. This leads to errors when loading/saving settings on child sites.
Moreover, Civi::settings() is already cached, so I was able to cut down the getSettings() and saveSettings() code considerably, and Airmail now works on multi-site installations.
I also took out some debug code from #14.
PS - The docs for SES setup are out of date again with SESv2, though good enough to muddle through. If I get around to updating them, I'll also make a note for multi-site installs that all sites must have the same bounce "address" as the first site.
Currently, Airmail uses
Civi::cache()
for settings, mailing IDs and mailing jobs. On a multi-site, the last two are the same across domains, but settings are per-site. This leads to errors when loading/saving settings on child sites.Moreover,
Civi::settings()
is already cached, so I was able to cut down thegetSettings()
andsaveSettings()
code considerably, and Airmail now works on multi-site installations.I also took out some debug code from #14.
PS - The docs for SES setup are out of date again with SESv2, though good enough to muddle through. If I get around to updating them, I'll also make a note for multi-site installs that all sites must have the same bounce "address" as the first site.