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 Recurring events templates and compatibility (cont'd) | Event Espresso - Staging Server
This technology (is it html5?) is such a departure from what I’ve seen with WordPress sites in the past that I’m stumped. Perhaps you can take a look and see.
EE should have no problem with HTML 5 themes. We have had some issues with Themeforest themes in general, especially with javascript not being loaded correctly, or the p tags being formatted incorrectly.
Not all Themeforest themes are like this, but it is difficult to say whether this one will have issues just from the demo.
I would be very cautious with a template that loads content using AJAX. I’ve seen a few of these that do not work with Event Espresso. In one case the customer purchased a theme that loaded up the content with AJAX and this had to be disabled so the registration process would work.
Generally that is the case though we do not test them with every iteration, they are just ones that many/any issues regarding. One customer recently advised on a forum post that MOJO themes don’t work well but we havent confirmed this.
Viewing 8 reply threads
The support post ‘Recurring events templates and compatibility (cont'd)’ 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.