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
Changing default css used by messenger in EE4 | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Changing default css used by messenger in EE4

Changing default css used by messenger in EE4

Posted: March 18, 2014 at 3:10 pm

Viewing 2 reply threads


Miguel Ángel García Martínez

March 18, 2014 at 3:10 pm

Hi,

I was wondering if there’s a way to change the default css file used by the messenger in EE4 when sending emails. I found the two files that are used, but would like to see if there’s a safer way to overriding defaults.

Best regards,
Mike


Darren Ethier

March 18, 2014 at 4:27 pm

Hi Miguel,

Currently there isn’t a way to modify the css used with the default templates and not lose your modifications when EE is updated.

However, I’ve created a ticket for this and we’ll be adding a WordPress filter around the css that’s loaded so people can swap out the css file loaded.

In the meantime, as a workaround, you can add inline styles directly in the message templates via the style tag.


Miguel Ángel García Martínez

March 18, 2014 at 4:33 pm

Thank you Darren!

Miguel
Viewing 2 reply threads

The support post ‘Changing default css used by messenger in EE4’ 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.

The original Forum description...

Status: closed

Updated by Miguel Ángel García Martínez 10 years, 10 months ago ago

Topic Tags

Notifications

This topic is:
pending
Event Espresso - Staging Server