Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 [MULTISITE] Email From field, logging | Event Espresso - Staging Server
The email on my multisite install is coming from the primary domain, like this:
"primary.domain.com" <ee-configured@email.add>
I’d read previous posts on this, however Fancy Headers doesn’t make a difference, nor does toggling it off and on again. I can’t use the recommended plugin, as it will intefere with the rest of the sites, and I’d prefer not to hack the source as it’ll make upgrades a pain. Is there another solution?
Also, where do the logs go on a multisite install? This doesn’t seem to be documented, but from some digging it would appears they’re supposed to go in wp-content/upload/espresso/logs; however the upload directory isn’t in multisite installs and blogs.dir seems unlikely.
Event Espresso does not formally support Multisite, which is why you will fond no reference to it in the documentation. However some users have managed to make it work for them and their setups.
Regarding the logs, I found the logs where in the main uploads directory -wp-content/upload/espresso/logs – however this is a local set up.
Ideally, the plugin must NOT be network activated as we have heard this does cause issues.
Regarding the email issue, well I havent tested this but so long as the plugin isnt network activated then it should use the admin of the sub sites email address, but again I havent confirmed this.
Viewing 1 reply thread
The support post ‘[MULTISITE] Email From field, logging’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.