Event log methods other than writing to /tmp (the default)

[Joshua Shipsey]

Are there alternatives to writing this event log to other locations than /tmp? Writing to /tmp is ok for a development environment, but WordPress does not have permissions to write to /tmp in a production environment hosted on WP Engine, so logs for the production environment can not be created. Can either the path be changed, or can this log file be written to an AWS S3 bucket (preferred) ? The only entry accepted by the method drop down is “Default (uses temporary files)”.

[Patricia]

Hi Joshua,

Welcome back! Can you please let us know if the code update suggested in this thread helped to solve the issue you are experiencing?

If that didn’t help you, please let me know so I can further investigate your case.

Thanks!

Patricia

[Support Droid]

Hey there! This thread has been pretty quiet for the last three weeks, so we’re going to go ahead and close it to avoid confusion with other topics. If you’re still looking for help with this, please do open a new thread, reference this one and we’d be more than happy to continue the conversation over there.

Thanks so much!
The Events Calendar Support Team

[Scott]

Following up, the original issue from https://theeventscalendar.com/support/forums/topic/does-the-debug-log-write-to-tmp-causing-a-fatal-error-on-shared-hosting/#dl_post-1367750 was that the error log wasn’t writeable (shared host). I suggested using the filter “tribe_file_logger_directory” in response so that Jason could override the directory of the log file being written.

[Author]

Posts