|
gkelly
|
August 10, 2015 at 9:30 am
When I go to apply a payment for an invoiced transaction, I get the following: (see screenshot)
http://cl.ly/cCFL
I am using Chrome on a mac, but I have also tried Safari and Firefox.
Kind of sucks if I cannot process payments. 🙁
help!
thanks!
|
|
Tony
|
August 10, 2015 at 9:42 am
Hi gkelly,
Are you using translations at all on the site (be it PO/MO files or via the get_text filter shown here)?
Are you using the latest version of Event Espresso 4 (currently 4.7.9.p)?
|
|
gkelly
|
August 10, 2015 at 9:54 am
Hi Tony,
I am not using any translations. I am running the latest, 4.7.9p
Aside from the EE plugins that I am using, I have the following installed:
– Disable Comments
– Enable MEdia Replace
– Display Widgets
– Cute Slider WP
– Custom Sidebars
– SiteOrigin Page Builder
– Ultimate Member
Grady
|
|
Tony
|
August 10, 2015 at 10:14 am
This could possible be a theme or plugin conflict.
Can you first try switching to one of the default themes such as twentyfourteen, refreshing the transaction page and retesting please? (you can do this without effecting your visitors using the Theme Test Drive plugin)
If it is still the same, temporarily disable all non-ee plugins and retest (create a database backup before doing so, just to be on the safe side, I use BackupWordPress although there are many plugins to chose from)
|
|
gkelly
|
August 10, 2015 at 11:52 am
Ok, Deactivating stuff helped me find the offending plugin. It is the Ultimate Member plugin. 🙁
Is there a membership plugin that works better with EE?
|
|
Jonathan Wilson
|
August 10, 2015 at 2:23 pm
Sorry to hear that!
We use s2member internally, and have recommended it to other customers. I have personally used it on a site that runs EE as well. You can also check out MemberPress.
|
|
gkelly
|
August 13, 2015 at 11:25 pm
I realized that it is kinda odd for that plugin to be affecting an EE specific page, right? Is there any way to figure out what is making it happen?
|
|
Tony
|
August 14, 2015 at 6:52 am
Hi there,
Its happening because Ultimate Member is adding code to all pages within the admin. So then that happens on the Transactions page and it changes the page, the JavaScript used to hide and show the models then gets thrown off and is hiding/showing the models based on the wrong calculations.
We recently had another member report the same issue here:
https://eventespresso.com/topic/plug-in-conflict/
After a little more digging the action that is causing this was found to be:
\ultimate-member\admin\core\um-admin-dragdrop.php
add_action(‘admin_footer’, array(&$this, ‘load_field_order’), 9);
The other member opened a ticket on their support forum here:
https://wordpress.org/support/topic/conflict-with-event-espresso-plug-in
I would recommend posting there for to see if UM can offer any suggestions to removing that action
|
|
gkelly
|
August 14, 2015 at 12:03 pm
thanks sir! The details will be really helpful. I have them looking into it now.
|
|
Tony
|
August 14, 2015 at 12:30 pm
No problem 🙂
Please let us know how you get on.
|
|
gkelly
|
August 15, 2015 at 3:46 pm
They guys over at UM haven’t helped me yet, but I was able to find a way to fix this. I found a plugin that allows you to selectively turn off plugins.
https://wordpress.org/plugins/plugin-organizer/
I created a filter that turned off everything but EE and itself. Now it all works!
Pass it on to the other guy that was having the same issue.
Grady
|
|
Lorenzo Orlando Caum
|
August 17, 2015 at 9:12 am
Hi Grady, thanks for sharing your solution. I’ve notified the other member.
—
Lorenzo
|
|
Andreas Simou
|
August 20, 2015 at 4:48 pm
Hey Grady, I’m having the same issue, any chance you could share show you setup plugin organizer?
Thanks
|
|
Tony
|
August 24, 2015 at 5:13 am
Hi there,
I noticed that the support team for Ultimate Member requested further details within Grady’s post their support forums so I added further details there, you can vie this thread here:
https://ultimatemember.com/forums/topic/modal-problem-occurring-because-of-um/
It looks like UM will be applying a fix to prevent that code loading on all pages in a future version.
|
|
Andreas Simou
|
August 27, 2015 at 2:11 am
Thanks Tony.
|
|
Tony
|
August 27, 2015 at 4:34 am
No problem 🙂
|
