|
Seth Huckstead
|
February 12, 2014 at 1:51 pm
Reported this error: Fatal error: Cannot redeclare class AuthorizeNetAIM_Response in /var/www/mywebsite.com/wp-content/plugins/event-espresso-core-reg1/modules/gateways/Aim/EE_Aim.class.php on line 567
Added the AIM folder that was recommended to fix this problem (a year ago). Got the plugin to activate, but I now do not have the ability to activate/decativate or change settings with Authorize.net
|
|
Tony
|
February 12, 2014 at 2:13 pm
Hi Seth,
Can you describe steps to how the original error was produced please?
Was it straight from activation?
Reg the AIM folder.
It is very unlikely this was intended as a fix for EE4, may I ask where you found this fix?
|
|
Seth Huckstead
|
February 13, 2014 at 7:04 am
Upgraded from 3.1.36. I decided to reset the entire program (still just building the registration site, so nothing big lost) I can run the program, but I have a blank section when I go to payment settings section–I cannot activate any payment methods.
The solution where I added a different AIM folder came from other threads on this site regarding this same/similar issue. If I add the new folder I can edit all of the other payment methods, but AIM. See here: https://eventespresso.com/topic/payments-not-working-with-authorize-net/
I realize version 4 is still beta, so I am not complaining, just trying to help bug test so I can help move it to GM.
I would like to get this issue resolved in the next two weeks, however, so I can go live with my event–the new ticket method is exactly what I need.
|
|
Tony
|
February 13, 2014 at 7:29 am
Thank you Seth, we appreciate the feedback as it helps narrow down the issue 🙂
This may well be a conflict with another plugin that has already setup a class AuthorizeNetAIM_Response. Would is be possible to get a list of active plugins?
The easiest method is to go to Event Espresso -> Maintenance. System Information tab.
Copy all of the Information within ‘Raw System Data’ and send that to support@eventespresso.com with a reference to this thread.
We will investigate this issue and update asap.
|
|
Seth Huckstead
|
February 13, 2014 at 7:50 am
I reinstalled v.3, just so I could test things a bit more reliably. Here is my data:
vent Espresso version 3.1.36.4.P
WordPress version WP 3.8.1
Installed plugins
Gravity Forms by rocketgenius version 1.8.4,
All in one Favicon by Arne Franken version 4.3,
Event Espresso by Event Espresso version 3.1.36.4.P,
Force Strong Passwords by Steve Taylor version 1.3.2,
Genesis eNews Extended by Brandon Kraft version 1.4.0,
Genesis Simple Edits by Nathan Rice version 1.7.1,
Genesis Simple Hooks by Nathan Rice version 2.0.1,
Genesis Toolbar Extras by David Decker – DECKERWEB version 1.6.0,
Gravity Forms Authorize.Net Add-On by rocketgenius version 1.5,
Gravity Forms MailChimp Add-On by rocketgenius version 2.4,
Image Widget by Modern Tribe, Inc. version 4.0.8,
PeRT Admin by topher version 1.0,
PRTS Custom Functions by topher version 1.0,
Really Simple CAPTCHA by Takayuki Miyoshi version 1.7,
Revolution Slider by ThemePunch version 3.0.95,
SermonAudio Widgets by Dan Alexander version 1.9.2,
Shortcode Widget by gagan0123 version 0.3,
Shortcodes Ultimate by Vladimir Anokhin version 4.6.2,
Simple Social Icons by Nathan Rice version 1.0.5,
Table of Contents Plus by Michael Tran version 1311,
W3 Total Cache by Frederick Townes version 0.9.3
|
|
Seth Huckstead
|
February 13, 2014 at 7:51 am
Didn’t read your reply thoroughly. Will send to support.
|
|
Josh
|
February 13, 2014 at 8:04 am
Hi Seth,
It’s most likely the Gravity Forms Authorize.Net Add-On is using the same classes as EE4 does. In EE3 we prefixed all the gateway classes to avoid conflicts like this one but that hasn’t been done for EE4 yet (and should be done soon).
|
|
Seth Huckstead
|
February 13, 2014 at 8:25 am
Thanks. Implementation/testing question than. I need to go live March 3, 2014. Should I just continue to build in EE4? Or, should I just stick w/E3? I need to use Gravity Forms as it powers my donation system.
|
|
Josh
|
February 13, 2014 at 1:46 pm
Hi Seth,
This was a simple fix and we’ll have an update out today that includes the fix. I’ve tested it out on my test site that has Gravity Forms + its authnet add-on and it works great.
|
|
Seth Huckstead
|
February 13, 2014 at 2:29 pm
Thanks. Should this also fix the issue where the payment options screen is left blank (at least for me)? It was visible when I added the the other AIM file.
|
|
Josh
|
February 13, 2014 at 2:45 pm
You’ll need to remove the old AIM folder that you uploaded to /wp-content/uploads/espresso/gateways. That’s not compatible with ee4.
|
|
Seth Huckstead
|
February 13, 2014 at 4:33 pm
I just reloaded the original file to overwrite any changes I had made.
|
|
Tony
|
February 13, 2014 at 4:43 pm
Hi Seth,
Have you also removed the folder AIM from wp-content/uploads/espresso/gateways/?
|
|
Seth Huckstead
|
February 13, 2014 at 5:55 pm
I removed the modified file. What resides there now is the file as included in the EE4 beta. The install I have now has no changes to it.
|
|
Tony
|
February 14, 2014 at 4:02 am
Hi Seth,
On a default install, with no modifications, there should be no files/folders within uploads/espresso/gateways/
Basically the uploads/espresso/* directories are used only for modified files. You can remove the AIM from from gateway directory and EE will revert back to using the default one that come with the install.
So I would remove that AIM folder from uploads/espresso/gateways/ and use the defaults unless you are making modifications.
|
