This question already has an answer here:
Got Http response code 500 when accessing https://api.sandbox.paypal.com/v1/payments/billing-plans/xxxxxxxxxxx
(1 answer)
Closed 6 years ago.
is the sandbox for Paypal broken ? I receive a 500 error.
https://www.sandbox.paypal.com/websc&cmd=_express-checkout&token=EC-78048295RW8002111
I wasnt sure if it needs cgi-bin in the url but that does not work either
https://www.sandbox.paypal.com/cgi-bin/websc&cmd=_express-checkout&token=EC-78048295RW8002111
It's from my prestashop plugin - which seems to be having issues in sandbox mode.
The docs seem to suggest that url should work:
https://developer.paypal.com/docs/classic/express-checkout/ht_ec-singleItemPayment-curl-etc/
thanks for any help ;)
Have just received this response from the support team:
We are already aware of the issue. Our engineers are working on it for a quick resolution.
I will let you know once the issue will be resolved.
Thank you in advance for you collaboration.
Related
For some very weird reason the issue happens just for 2 users and they are waiting patiently for more than week until we solve it.
Other users are working like expected, can't reproduce it local either.
For others Facebook authorization works fine, Email and Password works fine as well.
There is nothing special about these users: iOS 11, latest iPhone etc.
Does anybody had chance to investigate and solve the issue already?
P.S. Firebase Support suggested to create minimal reproducible example, but the issue happens just for 2 users and it doesn't look like possible at the moment.
Thank you,
Alex
The issue happens for users in specific regions which are "banned" by Google (like Crimea etc)
Works fine when user turns on VPN. No other workarounds found by me so far.
I am unable to publish to a new deployment. I get a Error 404. 404. That’s an error.
The requested URL was not found on this server. That’s all we know.
Could you please help me solve this issue?
Thanks,
Maria.
Please check recent update from App Maker Team posted here: https://groups.google.com/forum/#!topic/appmaker-users/XqBpaeDD2Lc
It seems like the data access infrastructure is having some troubles and the App Maker Team are working on it. Please check the above thread for updates. Sorry for the inconvenience.
Note: Please make sure you are using the following tag for future App Maker questions: appmaker
UPDATE: This should be fixed now, but please let us know if you still see any error during the preview / publishing process.
Currently I'm trying to upgrade the application from wicket 1.4 to wicket 6 and I'm stuck with the following issue:
When I try to close ModalWindow, it is closed but I receive PageExpiredException on the page where I was opening this ModalWindow, so I'm redirected to
/myapp/wicket/bookmarkable/org.apache.wicket.markup.html.pages.PageExpiredErrorPage
I thought maybe the way I create ModalWindow is outdated, so I've tried an example from here
http://www.wicket-library.com/wicket-examples-6.0.x/ajax/modal-window?0
and it gives me the same exception.
Maybe I have to configure something in my WebApplication implementation, but I don't know what.
If anyone could help, it'll be really appreciated. Thanks.
Check your server logs for errors related to the serialization of the opener page. PageExpiredException means that the page cannot be found in the page storage. If there was an error with the serialization then it won't be stored and thus later won't be found too.
This question already has answers here:
ERROR: WSDL - SOAP-ERROR: Parsing WSDL: Couldn't load from [duplicate]
(4 answers)
Closed 9 years ago.
Recently I am trying to integrate two system we use now.
We have a customer feedback website that using Helpspot (http://www.helpspot.com/) and the other is Bug tracker Mantis server. we hope some of customer feedback can be added into mantis . Since mantis have a WSDL mantisconnect, so I wrote some code with nusoap to interact with the mantis wsdl. It worked fine..I can update issue or do rest of other things.
But when I uploaded the same code to the Helpspot server, it stop working...
and I got this error msg:
Fatal error: Uncaught SoapFault exception: [WSDL] SOAP-ERROR: Parsing
WSDL: Couldn't load from
'http://Mymantis/api/soap/mantisconnect.php?WSDL' : Extra content at
the end of the document in
/www/eh17275/public_html/custom_code/RequestPush-MantisBT.php:36 Stack
trace: #0
/www/eh17275/public_html/custom_code/RequestPush-MantisBT.php(36):
SoapClient->SoapClient('http://testmant...') #1
/www/eh17275/public_html/custom_code/RequestPush-MantisBT.php(75):
RequestPush_MantisBT->push('test') #2 {main} thrown in
/www/eh17275/public_html/custom_code/RequestPush-MantisBT.php on line
36
the Line 36 in my code is =>$client=new soapclient('http://Mymantis/api/soap/mantisconnect.php?WSDL');
I googled whole day and most of people encountered this error usually because they wrote their own SOAP server, but in my case, I just wrote a client and the code worked.
and the WSDL on my mantis server is up. I can see this page http : / /mymantis/api/soap/mantisconnect.php and I even want my friend at home to check the page and they can see it. So I think the factor of internet service setting can be elimiated.
Is there any people have any thought about this?
Thx for reading
Maybe you are simply trying with a wrong URL ?
The URL you tested was http://Mymantis/api/soap/mantisconnect.php?WSDL but IMO it should end with ?wsdl.
I tested with the online demo site :
http://www.mantisbt.org/demo/api/soap/mantisconnect.php?WSDL does nothing
http://www.mantisbt.org/demo/api/soap/mantisconnect.php?wsdl works and renders the awaited WSDL document
I have a FLEX 3 frontend that worked fine in FlashPlayer 9. But now that I've upgraded to FlashPlayer10, the ?_method=PUT/DELETE hack is not working anymore. All those requests show up as a POST on the backend now. I did some reading and it sounds like I need to use as3httpclientlib AND run a socket policy server to give access to port 80 (or any other port) in order to use as3httpclientlib. So my question is: are you freakin kidding me? How is it that, in earlier versions of Flex/flash player, all I had to do was add a simple string ("_method=") to the url. But now I have to do the hokey pokey AND turn my self around? Really? Please someone tell me that I've got this all wrong, and that _method= is, in fact, still supported. Otherwise, its BYE BYE FLEX/FLASH PLAYER - NEVER AGAIN!
I understand you very much, my friend, just had similar noise with authentication headers in new one Security Policy from Adobe. Anyway, if you'll share your code, maybe I could help you, because your goal is not clearly explained in your post, Buddy. So let me know please, cause java sandbox and silverlight are not the better way in this case. But maybe some javascript stuff could save our time.