I have setup the enom module for both the live and sandbox environments and get no issues at this time which seems to point to the ID, password and setup at enom all being correct as it fails if I intentionally enter bad data.
I have then setup packages to use the module and when I try to test the order form it seems to work fine if I pick "transfer" of a non existent domain name but it obviously does not do any checks at this time but if I pick "Check Availability" it always comes back with Not Available.
My PHP is very rusty but I added a couple of lines to display the Enom response and it seems to be showing that the login credentials are incorrect, if i try to display the variables I think hold the credentials, it shows both ID and password as being Null so I am either looking at the wrong thing or displaying them before they are updated.
Am I doing something wrong or is there an issues with the module, I have searched everywhere for similar problems and can find nothing.
I am using vesion 4.0.1 of Blesta and the module is version 2.3.1.
I am getting the same result on both the live and sandbox enom setups.
Question
rudders18
I have setup the enom module for both the live and sandbox environments and get no issues at this time which seems to point to the ID, password and setup at enom all being correct as it fails if I intentionally enter bad data.
I have then setup packages to use the module and when I try to test the order form it seems to work fine if I pick "transfer" of a non existent domain name but it obviously does not do any checks at this time but if I pick "Check Availability" it always comes back with Not Available.
My PHP is very rusty but I added a couple of lines to display the Enom response and it seems to be showing that the login credentials are incorrect, if i try to display the variables I think hold the credentials, it shows both ID and password as being Null so I am either looking at the wrong thing or displaying them before they are updated.
Am I doing something wrong or is there an issues with the module, I have searched everywhere for similar problems and can find nothing.
I am using vesion 4.0.1 of Blesta and the module is version 2.3.1.
I am getting the same result on both the live and sandbox enom setups.
Thanks
Link to comment
Share on other sites
1 answer to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.