Closed adamthehutt closed 4 years ago
It looks like there may be a number of similar issues in other spots. Most everywhere that a relation is defined the code is relying on Laravel conventions to guess the key names, rather than having them explicitly defined. This only works if the Model class base names are the same as the Mailcoach defaults.
This should be fixed in the latest version thanks to your PR
The mailcoach configuration settings allow for child classes to be used in lieu of the standard Subscriber, EmailList, and Template models. However, the tags() method in the EmailList class fails if different model names have been set.
Currently we have:
This results in an SQL error when the model is named, say, MailcoachList. The fix should be as simple as: