-
pdirect-
Situations like these are best addressed with paid consulting time and if it is a Method Platform issue and not a customization issue we will credit back the time.
I tested the screen I created when you orginally were looking to create the search screen and my version which has been untouched in the last 14 days works as it ...
-
This is especially frustrating because it was working fine and without any changes on our end, suddenly it hangs.
-
Very frustrating! I just spent an hour recreating that screen with one simple customization . . . and now it's still "hanging" (i.e. won't load). What do I do now?
-
pdirect-
If you delete the copied screen it will link back to the orginal screen. Make a copy of the copied screen first(Don't replace the tab links) and then delete the screen, that way you still have access to the customized screen.
-Michael
-
Shawn-
I was able to duplicate this issue and have created a ticket for our development team. I will update this post when there is a resolution or when I have more information.
-Michael
-
You mean test the original search screen? I already did that. But how do I recreate the link to the original search screen?
-
Hi Emily-
Method does support Authorize.net. I did a quick search and based on the developer guide for Authorize.net (Page 26 Link ), the phone number should be optional. You may have to contract Authorize.net about the phone number being required (This may be a setting within AVS), on our end here at Method, I can only make a request ...
-
pdirect-
Since the search screen is not dependent on information from any
other screen, you can go to the screen list (Customize > Screens) and just click
View to bring it up and test it out.
-Michael
-
Michael -
I am confused why you say you support Authorize.Net when it keeps requiring more information. I have reviewed the settings online with Authorize.Net and I can't find where to not look at those fields. Do you have any suggestions how I can make this work? Either with Method or ...
-
Another concern would be that this will create that TOKEN missmatch sync issue I experienced over the weekend.