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
ChurcHope theme X Event Espresso TinyMCE Conflict | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › ChurcHope theme X Event Espresso TinyMCE Conflict

ChurcHope theme X Event Espresso TinyMCE Conflict

Posted: March 6, 2013 at 11:06 am

Viewing 2 reply threads


Matt Moore

March 6, 2013 at 11:06 am

There seems to be a conflict between my ChurcHope theme and Event Esspresso that is causing the TinyMCE editor from loading on the event pages.

The error returned on the Chrome console is “Uncaught TypeError: Cannot read property ‘Button’ of undefined” in tiny_mce.js (line 1).

The theme developer isn’t offering much help so how would I track down exactly what is causing the conflict so I may edit it out?
http://help.themoholics.com/discussion/1051/churchope-x-event-espresso-plug-in-conflict#Item_1

WP Ver: 3.5.1
Event Espresso Ver: 3.1.30.7P
Registration Page Link: http://cps.rsgvfx.com/programs/


Matt Moore

March 6, 2013 at 12:55 pm

I actually found a solution (please advise if you think this may cause problems later).
I commented out Line 77 of Event Espresso admin.php (~/wp-content/plugins/event-espresso/includes) and that seemed to have stopped blocking the theme’s additional MCE buttons.

/* remove_all_filters(‘mce_external_plugins’); */


Chris Reynolds

  • Support Staff

    •

March 6, 2013 at 2:18 pm

2 things that you can do with as you see fit.

  1. That function was added for a reason. In the past, there have been issues with themes or plugins that improperly add additional buttons to the WordPress editor. This function was added as a way to alleviate the issues and problems that would result when trying to use those additional buttons.

  2. If you have modified the core plugin, you will need to manually copy those changes over to the file every time you update to a new version of Event Espresso. If possible, you should try copying the entire function that that line is found in and use the custom files add-on to override the function with your version that has the commented out line. Note, this isn’t always possible as not all functions are wrapped in function_exists checks (and if it isn’t, then your only option would be to manually edit the file or not ever update Event Espresso).
Viewing 2 reply threads

The support post ‘ChurcHope theme X Event Espresso TinyMCE Conflict’ 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.

The original Forum description...

Status: closed

Updated by Chris Reynolds 11 years, 10 months ago ago

Topic Tags

Tagged: , , , ,

Notifications

This topic is: not resolved
Event Espresso - Staging Server