This topic contains 4 replies, has 0 voices, and was last updated by Bednar 8 years, 7 months ago.
-
AuthorPosts
-
March 11, 2016 at 8:58 am #6752
spowers.uncHi All,
I am new to NetSuite, so bear with me as I am probably not as up on the NetSuite lingo as most of you.
We have two external web sites that are subscription based. We track subscriptions in a custom record type in NetSuite. We have a Drupal 7 front end that sends a call to a NetSuite RESTlet to verify the users’ subscription status.
Since the upgrade, one of the subscription sites is working fine – we can see the requests come through in the RESTlet’s execution log. The other site shows nothing & the web site acts like the user’s login is not valid. However, we have an old Drupal 6 version of the same site & we are able to log in via that, so we know the logins are good & the RESTlet is returning valid info to allow the user to log in & access the site content.
The challenge is that our Drupal programmer says the 2 sites are using the exact same code to call NetSuite, verify the login & pull back the subscription information.
I am at my wits end because the problem started with the NetSuite update this weekend so the programmers are blaming it on NetSuite changes. Does anyone have any idea where we could begin to troubleshoot this? NetSuite Tech support has been no help – they say they are not seeing any calls to NetSuite from the web site on the backend. The programmers want to be able to see what the NetSuite API is seeing & how it is responding. Are there any tools or sites that can help me with that or am I dependent on NetSuite support?
Thanks in advance
Sue
This is a cached copy. Click here to see the original post. -
March 20, 2016 at 12:15 pm #6753
webbeeHello Sue,
Do both the Drupal sites use same netsuite logins and are hosted on same server / environment.
Since you mentioned the execution log dont show anything , may be the password contain special chars and it is not handled in Drupal site.
There can be other issues too but above is the most common i find.
I will suggest copy the code on local / test environment and check the data / URL being sent in each request, and check if from both are same
thanks
-
March 21, 2016 at 7:15 am #6754
BednarSue:
It’s not making to the RESTlet, but… if you check the login audit trail in NetSuite when you’re connecting from the (non-working) Drupal 7 site, are the attempts showing up there (as either successes or failures)? That might prove the case one way or the other if it’s even reaching NetSuite.
-b
-
March 31, 2016 at 8:39 am #6755
spowers.uncThanks for the responses. Once we put the login back on the main site,”it just worked”. One of life’s little mysteries. Was it the RESTlet that just needed to be kicked? Did our vendor do something to the Drupal script that fixed it? No idea!
Signed “the new Brad”
-
March 31, 2016 at 9:08 am #6756
BednarOriginally posted by spowers.unc
View Post
Thanks for the responses. Once we put the login back on the main site,”it just worked”. One of life’s little mysteries. Was it the RESTlet that just needed to be kicked? Did our vendor do something to the Drupal script that fixed it? No idea!
Signed “the new Brad”
If I had to make a guess, I’d wager that the hook wasn’t working properly on the Drupal7 side, especially if NetSuite wasn’t receiving anything on the RESTlet side. The hooks in Drupal can be a little fiddly, so something probably didn’t migrate perfectly from 6 to 7.
-
AuthorPosts
You must be logged in to reply to this topic.