Authorize.net "in test mode" question

First off, I should state that my web host does not support cURL which of course isn't helpful. However, from the all the info I gatthered here on this forum, I was able to figure out that you can still process payments with authorize.net via SIM without cURL enabled. I have everything set up, just did a test transaction and everything processed correctly.

However, across the top of every page it still says "AUTHORIZENET IS IN TESTING MODE" even though it is not in test mode with them, and it is set to Production Mode in the ZC payment module.

Previously, I couldnt even edit any of the three authorize.net modules (would get the cURL error), but when I deleted the AIM and echeck files from both "Includes folders," I was able to edit authorize.net SIM.

As mentioned before, however, the warning still shows up on each page...any idea how to remove that manually since the payments are correctly processing?

Thanks for any help.

When you say your deleted the files, did you uninstall them first?

There are built in safeties for some modules that could be triggered if you did not ...

One method to check for this is to look in your database at the configuration table and run this SQL statement:

SELECT * FROM configuration WHERE configuration_key LIKE '%MODULE_PAYMENT_AUTHORIZENET%' ;

How many come up?

Do you see any for:
MODULE_PAYMENT_AUTHORIZENET_AIM_stuff_here

I actually just found way around...I just modified the /includes/init_includes/init_header.php file and deleted the warning message from the file and it takes it off...

original:

if ((defined('MODULE_PAYMENT_AUTHORIZENET_TESTMODE') && MODULE_PAYMENT_AUTHORIZENET_TESTMODE =='Test' ) ) {
$messageStack->add('header', 'AUTHORIZENET IS IN TESTING MODE', 'warning');

Changed to:

('MODULE_PAYMENT_AUTHORIZENET_TESTMODE') && MODULE_PAYMENT_AUTHORIZENET_TESTMODE =='Test' ) ) {
$messageStack->add('header', '', '');

I will check the data configuration table though...thanks for the input!

Be fore changing code I would seriously look to find the real reason for this problem ...

I agree ... because if you're getting the warning message, then your admin setting is set to Test mode ... which means no real transactions will be processed ... so, it'll just look like it's taking orders, but you'll never get payment for them. Bad idea to just edit code to skip a warning message without understanding why it's happening in the first place.

Ok, it produces about 50 values...I do notice that both Authorize.net AIM and echeck are both enabled, which is probably causing the error since my web host doesn't support cURL? The SIM is both enabled and in production mode.

keep in mind I don't really have much mySQL knowledge so any and all help is appreciated!

Thanks.

DrByte:

I agree ... because if you're getting the warning message, then your admin setting is set to Test mode ... which means no real transactions will be processed ... so, it'll just look like it's taking orders, but you'll never get payment for them. Bad idea to just edit code to skip a warning message without understanding why it's happening in the first place.

I was actually getting the payments though Authorize.net though, they even confirmed from their end...that is what was so bizarre...

balthajd:

Ok, it produces about 50 values...I do notice that both Authorize.net AIM and echeck are both enabled, which is probably causing the error since my web host doesn't support cURL? The SIM is both enabled and in production mode.

keep in mind I don't really have much mySQL knowledge so any and all help is appreciated!

Thanks.
You should make sure the files are still on the server, and then use the "Remove" button in the admin to properly clean them up.

DrByte:

You should make sure the files are still on the server, and then use the "Remove" button in the admin to properly clean them up.

The files are all still on the server...

So I should just delete each entry associated with AIM and ECheck from the database that shows up after running the query?

Thanks again.

balthajd:

The files are all still on the server...

So I should just delete each entry associated with AIM and ECheck from the database that shows up after running the query?

Thanks again.
I strongly recommend you DO NOT just go deleting things from your database.
The safe way to delete entries that don't belong is to use the "Remove" button from the individual module's options in your Admin->MOdules->Payment menu.

DrByte:

I strongly recommend you DO NOT just go deleting things from your database.
The safe way to delete entries that don't belong is to use the "Remove" button from the individual module's options in your Admin->MOdules->Payment menu.

I was hoping you wouldnt say that...the problem is when the AIM and ECheck files are on the server, I get the following error when going to Modules - Payments and none of the other payment methods are even listed b/c of the error:

Fatal error: Call to a member function on a non-object in ...store\includes\modules\payment\authorizenet_aim.php on line 86

• which indicated the cURL error. That is why I had deleted those files from the server originally, because whenever they are uploaded, I get the error message and can't even edit the other modules. When they arent uploaded, everything displays correctly and I can edit the payment modules. Very confusing.

Ah, I see. It's not a good thing when a hosting company doesn't support CURL nowadays. But that's the cause for that particular error on that particular line number.

Here's the fix for those:
You're getting an error on line 86.
So, edit the file, and add the following as a new line at line 86, pushing the existing line 86 down to line 87:```
global $messageStack;

Then save the file and upload to the server. Then you should be able to use the Remove button properly.
Repeat for both files (adjusting "86" to whatever appropriate line number).

DrByte:

Ah, I see. It's not a good thing when a hosting company doesn't support CURL nowadays. But that's the cause for that particular error on that particular line number.

Here's the fix for those:
You're getting an error on line 86.
So, edit the file, and add the following as a new line at line 86, pushing the existing line 86 down to line 87:```
global $messageStack;

> Then save the file and upload to the server. Then you should be able to use the Remove button properly.
> Repeat for both files (adjusting "86" to whatever appropriate line number).

WOW you just saved me a lot of further time and aggrevation, THANKS!  That did the trick.

And you are right about the web hosting, especially when before I installed they said it was supported...time for a new host I do believe.

Thanks again!