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 Template Customization and CSS | Event Espresso - Staging Server
We had our forms/templates looking just the way we wanted, and then upgraded to the new EE because our email confirmations were no longer sending. I downloaded all of our files before upgrading because I knew I would have to compare and correct the new CSS files to match our style changes. However, when I upgraded, it doesn’t matter what CSS files we change, upload, etc…the styles DO NOT change to our specifications. I realize that the way CSS works in the new version of EE is different than before, so I have read your tutorial and played with both themeroller styles and putting our custom CSS in the content/uploads/espresso/templates folder. However, again, nothing is recognized.
My main question is that I just want to remove the 1px borders around all of the tables that show up in the registration system. Please tell me where I can make this change and move on with my life. Thank you! Note: We have not made any changes to our theme, and have only updated EE, so I have only been looking in EE related files. If upgrading EE changed anything in our theme, please advise. I am about to go batty.
The support post ‘Template Customization and 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.