Does the debug log write to /tmp, causing a fatal error on shared hosting?

[Joshua Shipsey]

I’m getting a fatal error when
wp-content/plugins/event-tickets/common/src/Tribe/Log/File_Logger.php

tries to write the log in a live environment hosted by wp-engine. It looks like it is trying to write to /tmp, and permissions are denied since this is a shared resource by all the installs on a particular instance.

The screen events -> help is now only generating a white screen inside the dashboard, and the debug logging can not be reset or turned off.

[Patricia]

Hey Joshua,

Thank you for reaching out to us! I’m very sorry about this issue you are experiencing, let me help you to solve it!

Can you please enable WP_DEBUG and WP_DEBUG_LOG and share with us any messages you see while trying to access the Events-> Help page? All WP_DEBUG messages will be stored in a debug.log file in /wp-content/debug.log.

Please share with us the errors you find so we can further investigate.

Thanks!

Patricia

[Joshua Shipsey]

This reply is private.

[Patricia]

This reply is private.

[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 on this ticket. It appears that Joshua is asking for the ability to set a custom directory for file logging.

We have a tribe_file_logger_directory filter that you can utilize, it can be seen in action here:

https://github.com/moderntribe/tribe-common/blob/4.6.2/src/Tribe/Log/File_Logger.php#L25

You can customize the directory using that filter, just be sure to add an .htaccess file that restricts HTTP access to that directory so the logs aren’t visible to the public / search engines.

[Author]

Posts