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 Where to put EE custom styles? Editor or Edit CSS? | Event Espresso - Staging Server
I was going to make some non-EE theme related adjustments and I realized that I had put my custom EE styles in the “Appearance > Edit CSS” input area – thinking this was the same as style.css of the child theme. Needing to customize the theme, I realized after using Firebug/Firefox that the EE customization in “Edit CSS” is not on the child theme’s style.css but on some strange planet!
The EE customization is for rules such as hiding elements, adjusting some backgrounds, etc. (I have customized the overall UI colors with Themeroller following your instructions and understand the proper location for those styles.)
I see that it is time for an EE update, so naturally I am wondering if updating will override my custom styles?
Can you confirm if using the child theme’s style.css, accessed through the Editor option under Appearance is the best practice for these kinds of updates.
Using a child themes styles sheet or a plugin such as My Custom CSS are definitely the best ways of doing it as neither will be affected by plugin or theme updates.
Viewing 1 reply thread
The support post ‘Where to put EE custom styles? Editor or Edit CSS?’ 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.