I am a new member.
I have an error when send message using HTTP Post to "graph.facebook.com/v2.11/me/messages?access_token=MY_PAGE_TOKEN"
This is error return:
`{"error":{"message":"(#100) Tried accessing nonexisting field (messages) on node type (Page)","type":"OAuthException","code":100,"fbtrace_id":"EB39Xkxnf6O"}}`
Despite error, tester and developer still able to receive message. But the FB viewer might not and they not approve my review submission:
"We did not receive an automated response when we messaged your Page. Bots should respond to all input from the user within 30 seconds so that the experience feels like a continuous conversation. Please ensure that your experience is functional before you resubmit."
The log show same error with FB viewer when server trying to response.
Any help. Thanks a lot
As the documentation explains you are required to submit a {conversation-id} before the messages.
More info here
Related
I am integrating Woo-commerce API’s in my wordpress site using Woo-commerce official rest sdk. I made a link using authentication endpoint URL. When I click the link it takes the user to Woo-commerce authentication page, where user login and Approve the request.
After approving the request it should take me to return url which i mention in the link. Instead it shows me the following error.
Error: An error occurred in the request and at the time were unable to send the consumer data.
I was having the same issue as well, and in my case, the return_url on my backend server was accepting GET requests, I changed it to POST, and everything worked perfectly. I hope it helps!
I know it's late for the answer but writing it for the people who will face the same issue in the future.
I was having the same issue and my problem was that the callback_url was wrong which was creating the error internally. So if you are getting this error, most probably your callback_url is not correct, please check that properly.
For whoever Shattique's answer
did not work,
check the response status code sent by the callback_url handler.
Anything other than 200 will throw the error in OP's question.
Here is link to woocommerce github repo,
where it throws the error.
TLDR: Make sure callback_url handler returns statusCode: 200
I am getting below error in on my Local wordpress setup after sending form data.
I am using Contact 7 form plugin for inquiry form in my website.
Send There was an error trying to send your message. Please try again later.
Thanks in Advance and please help me to resolve this error.
There might be 2 possible causes of this error. You can refer the guide by plugin author which explains it in detail. Read the guide and identify the type of error you get and based on that you will need to fix the error.
You can check your mail section or try with a different email address.
There could be two causes for this. The first is actual mail server trouble, where email cannot be sent. In this case, the error message would be surrounded with a RED border line. Contact your server admin.
The second possible cause is that the form submission is under suspicion of spam. In this case, the error message would be surrounded with an ORANGE border line.
response message samples
for Reference please follow below link
FAQ > After submitting the form, I get an error message stating “There was an error trying to send your message.” What is wrong?
Contact 7 plugin work on live .Its does not work on local so its showing the the error message "There was an error trying to send your message.” after submitting the form in local.
Try it on live it will work.
Consider the following situation:
I have a MVC setup where the view invokes a mapper to get a specific URL for a href attribute. The mapper holds keys to make the referencing easy.
Now the view requests an invalid key, so the mapper responds with say /invalid_url. But the dispatcher knows this URL and when a user clicks the link an error message will be displayed about how bad we feel.
But what if the Google Bot visits this invalid URL?
What would a search engine friendly status code be? I feel like 500 would be appropriate because it is a server side failure. But then this has the feeling of being a temporary error or somehow not related to the URL but to the internal mechanics. The other option that comes to mind is 404. This is also valid because the requested page does not exist. However 4xx errors are client side errors ("You requested the wrong URL. So it's basically your error"). And it just doesn't feel like a client side error to me.
Am I overthinking things? Should I just go with 404?
When I have a question like this, I refer to a site like http://www.restapitutorial.com/httpstatuscodes.html
5xx error codes imply that the server made a mistake. But you're saying the view (client-side) requested the wrong key. That sounds like a client-side error to me. While it's not the user's fault, the server doesn't know this, and the requested URL really doesn't exist. So a 404 would be appropriate.
But this is a weird case, and you should still want to fix the underlying issue of the client consistently(?) requesting a bad url.
After a few days we always get this email from paypal when someone is paying with paypal on our onlineshop:
Please check your server that handles PayPal Instant Payment
Notifications (IPN). IPNs sent to the following URL(s) are failing:
[OUR_SHOP_URL]/commerce_paypal/ipn/paypal_wps%7Ccommerce_paymen
t_paypal_wps
If you do not recognize this URL, you may be using a service provider
that is using IPN on your behalf. Please contact your service provider
with the above information. If this problem continues, IPNs may be
disabled for your account.
Thank you for your prompt attention to this issue.
Sincerely,
PayPal
We are using Drupal Commerce on Drupal 7. The "funny" thing is: Sometimes this error appear, sometimes not. When this error appear the Drupal-Commerce can not set the Payment status to "Completed" so it costs a lot of time to do this manually ...
I found a "solution" for this here but the *.patch does not removed the problem: https://www.drupal.org/node/1055390
Any other solutions ? :/
Edit:
When take a look at the drupal recent log messages I can find the error which was tracked.
Here's the information I get:
Type commerce_paypal
Date Thursday, October 9, 2014 - 13:15
User Anonymous (not verified)
Location [URL]/commerce_paypal/ipn/paypal_wps%7Ccommerce_payment_paypal_wps
Referrer
Message IPN URL accessed with no POST data submitted.
Severity warning
Hostname 173.0.81.1
Operations
Edit 2:
We found smth ... We have HTTPS. I jsut treid to use the HTTP Url. And ... this works fine. But we want to be at HTTPS isntead of HTTP. But maybe it will help you whats happened here ?
This seems to be an issue with Paypal itself - a user noted that sometimes the Paypal callback is encoded, thus pipe characters ("|") get encoded to "%7C". That user has described your problem - it's very hard to debug this issue, as it only occurs sometimes.
Here is a link to the issue, along with a small patch:
https://www.drupal.org/node/1055390#comment-7436538
This issue occurs on Paypal itself, although I am wondering why this patch hasn't been included in drupal commerce itself...
You need to check your web server log files to see exactly what error is happening on the failures. You'll be able to see the PHP error that you would typically see on screen when something is failing like that.
That will give you direction on what is going wrong and what you might need to do to fix it.
Another thing you could do is replicate the IPN that failed yourself and POST it directly to your IPN listener in a browser so that you can see the result on screen. This can help with troubleshooting and debugging. Just create an HTML form with the action set to your IPN URL and then add a bunch of hidden fields that match the names/values you got in an order that failed. That would trigger the same error so you can see it.
When sending customers to Paypal from my website I am seeing a new error message I've never spotted before:
Error Detected
We are sorry, we are experiencing temporary difficulties. Please try again later. If this error occurred while making a payment, avoid duplicate payments by checking your Account Overview before resending a payment.
Message 3005
Googling this message suggests it is just one shown to the general public when Paypal is overloaded....but I don't think that can apply to me becuase the Paypal site responds normally to other parts of my website which use a HTML link. It is when I use an ASP.NET Response.Redirect that I see the error.
I have checked the URL is correct and encoded correctly. So I really would like clarification that message 3005 is indeed one that can be shown when the incoming request is erroneous, as well as when the Paypal site is under heavy load.
Is this generic message shown in both circumstances? Is Response.Redirect acceptable?
"Googling this message suggests it is just one shown to the general public when Paypal is overloaded..."
And that's why you can't always trust Google results.
No, a '3005 error' does not mean PayPal is 'overloaded'. It is a generic error which can be returned for various internal and external reasons.
It's the PayPal equivalent of 'Something went wrong', without actually saying what went wrong.
Can you reproduce this error consistently? And if so, what are the steps to reproduce it?
Can you include your code?