Support

June 7, 2017 at 3:43 am

Hi there,

Those warnings are not errors, they are warnings thrown by your server informing you the file path currently being checked is longer than the server allows (260 characters).

For the majority of templates EE uses, it also checks for custom versions of the template within various locations including your site’s theme.

What is happening is EE is passing the full path to our template function and the first step within that function is to check within the site’s theme (and child theme) for the template it has been passed. So EE passes something like:

C:/CustomerData/webspaces/webspace_xxxxxxxxx/webapps/SiteAppxxxxx/htdocs/wp-content/plugins/event-espresso-core-reg/modules/ticket_selector/templates/ticket_details.template.php

As the template to load, which is passed to locate_template

locate_template is then checking for that file in your theme which ends up being:

C:\CustomerData\webspaces\webspace_xxxxxxxxx\webapps\SiteAppxxxxx\htdocs/wp-content/themes/x/C:/CustomerData/webspaces/webspace_xxxxxxxxx/webapps/SiteAppxxxxx/htdocs/wp-content/plugins/event-espresso-core-reg/modules/ticket_selector/templates/ticket_details.template.php

Normally that wouldn’t cause too much of an issue, the file doesn’t exist so EE continues on through its various other checks and returns a working template from wherever it finds it… however on your server, the above throws a warning because the file path is too long.

Right now your server has display_errors set to true meaning all warnings, notices, errors etc will display on the front-end of the site. On production servers it is recommended to not display them, for that you can add something like this:

define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );

Within your wp-config.php file. You can then enabled logging to log the errors if needed during debugging.

The above doesn’t ‘fix’ the cause of the warning but it should prevent the warnings from being thrown on the event page.