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
EE 3 Template Comments | Event Espresso - Staging Server

Support

Home › Forums › Pre-Sales › EE 3 Template Comments

EE 3 Template Comments

Posted: February 28, 2014 at 6:06 am

Viewing 4 reply threads


Thomas Mengwasser

February 28, 2014 at 6:06 am

Hi,

i’ve got some HTML Comments in my Source and would love to hide them. How and where can i delete them? I bought the Plugin already for a client and he doesn’t like them.

<code>&lt;!--Event Espresso Template Files:

Dir:  .
Dir:  ..

--&gt;
</code>


Thomas Mengwasser

February 28, 2014 at 6:34 am

found them in plugins/event-espresso/includes/functions/admin.php line 1416. Is there a option to hide them? I couldn’t find it.


Josh

February 28, 2014 at 10:45 am

Hi Thomas,

While there isn’t an option to hide them, they are added via a WordPress action hook. So they can be removed by creating a little function that removes them from the wp_footer action.


Thomas Mengwasser

March 5, 2014 at 1:34 am

ok thank you. could you provide me a function that will do that?


Dean

  • Support Staff

    •

March 5, 2014 at 4:55 am

Add the following to your themes functions.php

remove_action('wp_footer', 'espresso_files_in_uploads', 20);

please note that theme updates will remove that line of code unless you have a child theme. You could alos add that line of code to a custom plugin.
Viewing 4 reply threads

The support post ‘EE 3 Template Comments’ 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.

Status: closed

Updated by Dean 10 years, 10 months ago ago

Topic Tags

Tagged: , ,

Notifications

This topic is: not resolved
Event Espresso - Staging Server