I know there have been other post on the subject, but still I dont know what to do.
I am a novice to wordpress and websites. I have spent time learning everything about my theme, wpml, event espresso etc etc..
Now I have realised that my theme avada from theme fusion is effecting the events description visual plugin. I dont want to change the theme. What can I do????? This is worrying :S
What exactly do I have to say to the theme builder so that they can resolve this issue?
This is not effecting my visual editor on my posts or pages
Regards
Most theme and plugin conflicts can be avoided by only loading custom scripts on the admin pages they need to load on.
In a nutshell, it’s best practice to not hook directly to admin_head to include the theme/plugin scripts. Instead, they can create their own custom hook like: mycustom_admin_head. Then they can avoid their scripts getting loaded onto every page of the admin.
Here are a few additional references that may help:
This a reply I got back.
I hope the advice they have given will be sufficient, I’m not exactly sure if disabling TinyMCE will have an effect on other areas. I’ll ask Muhammad and see, but please keep in mind we are unable to support 3rd party plugins like that so if other issues arise we may or may not be able to help. We certainly try to do what we can though.
We plan on testing some of the more popular plugins soon, and some have already been tested and approved like Ubermnu, but we cant say exactly when we will be able to test Event Espresso. Once we do though, we will guarantee that it works and be able to support it.
With that being said, lets see if that above advice works.
If this can’t been done have I been left buying a theme and a plug in that leaves my site useless?
It looks like they are not excepting responsibility.
Most conflicts like this one can be resolved. In this case, it’s a matter of making sure that the theme scripts that are altering the TinyMCE editor don’t load on the Event Espresso admin pages. Alternatively, if you aren’t using the theme’s custom TinyMCE editor features, they could be disabled for the entire admin.
they said they could disable TinyMCE all together
“Well, that’ll remove the shortcode buttons since that’s all we have done with tinyMCE and any plugin should support custom buttons added by theme.”
It looks like the problem is with the script kd-admin.js that is loading on all the admin pages. If that script can be stopped from loading on the Event Espresso admin pages, that should solve your problem.
Hey Jonathan,
Just to let you know we were having exactly the same problem that you’ve been describing and we’re using Avada as well. Looks like Avada will solve this on their own at some point but until that time we’ve been able to solve the issue to some extent.
The problem is caused by the loading of the shortcode buttons that Avada uses. If you stop them from loading, then the Event Espresso pages will edit properly. I’m not sure what your technical know-how is but if you look in the wp-content/themes/Avada/ folder you’ll see a file called shortcodes.php. Open that in a text editor. Look for the line that reads add_action('init', 'add_button'); It’s around line 894 or so.. Put two slashes in front of it so that it looks like //add_action('init', 'add_button'); then save your file.
This will make it so that you can edit your Event Espresso events, email templates etc. When you want to use your Avada shortcodes again just remove the slashes from the file and save it again. The Avada shortcodes will be back and your Event Espresso items will be uneditable again.I know this isn’t a fantastic solution to the problem but it seems to be the least invasive that I’ve seen so far…and easier than disabling Avada every time you want to edit an Event Espresso event (which is also an option available for you)Hope this helps.
I dont have access to the theme to try this out so this is just theory, but if you wrapped the function like so, it should check to see if it is a post or page edit screen and load the function. EE events dont sue that so it shouldnt load it there.
function ee_resolve_editor($hook) { if ( $hook == 'post-new.php' || $hook == 'post.php' ) {
//the innards of the add_button function here. Don't need the "function add_button { " bit or the add_action
}
}
add_action('init', 'ee_resolve_editor', 10, 1 );
If you want to try this out test it on a testing server first as I cant guarantee it wont break your site.
I posted both of your comments to loge da, they have logged in to my account and have fixed it! Have asked for more info to what he did so I can pass the info on to you shush ton and for anyone else who may have the same problem in the future.
This will be implemented by default in the next version.
Viewing 16 reply threads
The support post ‘event description visual’ 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.