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 Front-end Event Manager Pre-release Plugin | Event Espresso - Staging Server
Using WordPress 3.8.1 with Genesis 2.0.2 and a new installation of Event Espresso 3.1.36.4.P with Event Espresso – Front-end Event Manager version 1.0.1.b, the page on which I have placed the Front-end Manager has the form wrapped in ‘pre’ tags which appear to cause all sorts of styling problems. The issue occurs in the newest version of Chrome, Firefox and IE.
This is a new EE3 installation on a site currently in development. It appears the ‘pre’ tags are necessary for the WYSIWYG editor functionality. I would love to use the Front-end Event Manager, is there currently a solution to this problem that doesn’t require core modification?
The pre tags should not be required in order for the WYSIWYG editor to work correctly.
If you edit the page, switch the editor to Text mode you’ll see the pre tags around the shortcode, remove both the opening and closing pre tags and update. http://take.ms/7if3y
The support post ‘Front-end Event Manager Pre-release Plugin’ 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.
Home to preview versions of next-generation Event Espresso products.