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 Integrating Event Espresso with the website theme | Event Espresso - Staging Server
Is there a way to integrate Avada theme with Event Espresso so the look and feel of the registration forms, emails, templates confirms to Avada theme styling?
I dont know the theme that well, but if you head over to the Template Settings page and turn off the ThemeRoller settings then Event Espresso will in most cases use the themes styles. That is mainly for the events/event listings.
Form wise, they should already use the themes styling unless the theme targets forms in an unusual way.
After taking a brief look at the contact form styling (I couldnt access the events) it looks like the theme doesnt target all the form inputs but rather specific ones with certain id’s/classes for example #comment-input input is what is controlling the style on some of the content input fields. This was seen in the all.css file, the themes style.css doesnt seem to target inputs at all.
Only workaround I can see is to take those styles and add them to the bottom of your style.css or via a plugin like My Custom CSS and modify them to style all the fields (input, textarea, etc).
Viewing 1 reply thread
The support post ‘Integrating Event Espresso with the website theme’ 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.