WPIntell

Source evidence

Some trouble making new posts

IFTTT Bridge for WordPress · support · 2014-09-15T14:51:00+00:00

mixedsentiment
highseverity
0.95relevance
14replies
Evidence onlycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

1 / 1 rows with source links

100.0% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

0 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
PeterBP resolved
Hi, I have been trying to get your Instagram plugin working but am failing to get the bridge plugin to work properly. The logs show that the data is being received (from both IFTTT instagram and from the testing tool) but then the following error follows: 2014/09/16 12:45:07 AM error An error occurred: Unexpected response code for url ” I have trouble-shooted but can’t resolve. Could you tell me where I might be going wrong please. Regards, Peter https://wordpress.org/plugins/ifttt-bridge/ Hi Peter! It seams that the plugin tries to load the Instagram image from an invalid (or better empty) url “”. Can you check your IFTTT recipe? Does it look the same as showed on the screenshot or as the shared recipe? You could change the log level to debug to see more information. If the error is still present you could sent me the infos from the log or post it here, but be sure that you don’t post the user/password which are part of the request coming from IFTTT. And you could of cause use the “test request” feature to play around with the WordPress plugins and to find out if everything is configured correctly which may be easier than bugfixing with IFTTT. Best regards Björn Thanks for the prompt response Bjoerne. I have checked the IFTTT recipe and it says “recipe checked” so I guess it is OK. I used your one and authorised it with Instagram and the WP site. Log level is already on debug. The error occurs when testing using the test facility. Here is s sample log showing an instagram test and the local tests. —- 2014/09/16 10:19:24 AM debug Received request: <?xml version=”1.0″ ?><methodCall><methodName>metaWeblog.newPost</methodName><params><param><value><string></string></value></param><param><value><string>********</string></value></param><param><value><string>********</string></value></param><param><value><struct><member><name>title</name><value><string>Monsalvat yesterday. My dad likes this wall a lot.</string></value></member><member><name>description</name><value><string>{“Url”:” http://ift.tt/1m5G4tT” ;, “SourceUrl”:” http://ift.tt/1uDxv9U” ;} Monsalvat yesterday. My dad likes this wall a lot.</string></value></member><member><name>mt_keywords</name><value><array><data><value><string>ifttt_bridge</string></value></data></array></value></member><member><name>post_status</name><value><string>draft</string></value></member></struct></value></param><param><value><boolean>1</boolean></value></param></params></methodCall> 2014/09/16 10:19:24 AM info Received data: title: Monsalvat yesterday. My dad likes this wall a lot. description: {“Url”:” http://ift.tt/1m5G4tT” ;, “SourceUrl”:” http://ift.tt/1uDxv9U” ;} Monsalvat yesterday. My dad likes this wall a lot. post_status: draft categories: mt_keywords: ifttt_bridge 2014/09/16 10:19:24 AM error An error occurred: Unexpected response code for url ”: 2014/09/16 10:19:24 AM info xmlrpc call received 2014/09/16 10:19:24 AM debug Received request: <?xml version=”1.0″ encoding=”UTF-8″?> <methodCall> <methodName>metaWeblog.newPost</methodName> <params> <param> <value> <string/> </value> </param> <param> <value> <string>********</string> </value> </param> <param> <value> <string>********</string> </value> </param> <param> <value> <struct> <member> <name>title</name> <value> <string>test</string> </value> </member> <member> <name>description</name> <value> <string>test</string> </value> </member> <member> <name>post_status</name> <value> <string>draft</string> </value> </member> <member> <name>mt_keywords</name> <value> <array> <data> <value> <string>ifttt_bridge</string> </value> <value> <string>test post</string> </value></data> </array> </value> </member> </struct> </value> </param> <param> <value> <boolean>1</boolean> </value> </param> </params> </methodCall> 2014/09/16 10:19:24 AM info Received data: title: test description: test post_status: draft categories: mt_keywords: ifttt_bridge, test post 2014/09/16 10:19:24 AM error An error occurred: Unexpected response code for url ”: 2014/09/16 10:19:24 AM info xmlrpc call received 2014/09/16 10:19:24 AM debug Received request: <?xml version=”1.0″ encoding=”UTF-8″?> <methodCall> <methodName>metaWeblog.newPost</methodName> <params> <param> <value> <string/> </value> </param> <param> <value> <string>********</string> </value> </param> <param> <value> <string>********</string> </value> </param> <param> <value> <struct> <member> <name>title</name> <value> <string>test 2</string> </value> </member> <member> <name>description</name> <value> <string>test again</string> </value> </member> <member> <name>post_status</name> <value> <string>draft</string> </value> </member> <member> <name>categories</name> <value> <array> <data> <value> <string>test</string> </value> </data> </array> </value> </member> <member> <name>mt_keywords</name> <value> <array> <data> <value> <string>ifttt_bridge</string> </value> <value> <string>test</string> </value></data> </array> </value> </member> </struct> </value> </param> <param> <value> <boolean>1</boolean> </value> </param> </params> </methodCall> 2014/09/16 10:19:24 AM info Received data: title: test 2 description: test again post_status: draft categories: test mt_keywords: ifttt_bridge, test 2014/09/16 10:19:24 AM error An error occurred: Unexpected response code for url ”: 2014/09/16 10:19:24 AM info xmlrpc call received 2014/09/16 10:19:24 AM info Method mt.supportedMethods not relevant 2014/09/16 10:19:24 AM info xmlrpc call received 2014/09/16 10:19:24 AM info Method metaWeblog.getRecentPosts not relevant —- Wondering if it might be that the server the site is running on does not support it so may test on another host. Thanks for your time, Peter Forgot to say, I tested also with all plugins except your ones turned off, and still got the error. P Worked it out I think. To get the bridge working, it seems to be mandatory to assign a category. Instant success. Then to get the Instagram working, I assigned a category at IFTTT and removed any changes I made to the description (I’d added the caption but probably done it incorrectly). Works! Looking good, thanks Björn! Resolved I think. Great! Applying a category is optional and it should work without a category. Hi Bjoerne, since last post, it has stopped working twice. I go in and find no logs and missed instagram posts. Usually “rebooted” by reactivating the WordPress channel at IFTTT. Trouble shooting now as launch is soon. PHP5.4.32 on Litespeed – it has never managed to make a WP post, but was successful posting the image which is all I needed for the gallery to work. – currently getting the same error while testing: An error occurred: Unexpected response code for url '': – I wonder if it’s a sanitizing issue of the instagram caption? It seems to stop working when the user posts an @someone link within their post. For now I have switched of the caption posting as title at IFTTT. – other than that I am at a loss! Hope you might be able to spot something wrong below. Following is the dump – regards, Peter array(16) { [0]=> array(3) { [“time”]=> int(1412608668) [“level”]=> string(4) “info” [“message”]=> string(20) “xmlrpc call received” } [1]=> array(3) { [“time”]=> int(1412608668) [“level”]=> string(4) “info” [“message”]=> string(45) “Method metaWeblog.getRecentPosts not relevant” } [2]=> array(3) { [“time”]=> int(1412608669) [“level”]=> string(4) “info” [“message”]=> string(20) “xmlrpc call received” } [3]=> array(3) { [“time”]=> int(1412608669) [“level”]=> string(4) “info” [“message”]=> string(45) “Method metaWeblog.getRecentPosts not relevant” } [4]=> array(3) { [“time”]=> int(1412608670) [“level”]=> string(4) “info” [“message”]=> string(20) “xmlrpc call received” } [5]=> array(3) { [“time”]=> int(1412608670) [“level”]=> string(4) “info” [“message”]=> string(45) “Method metaWeblog.getRecentPosts not relevant” } [6]=> array(3) { [“time”]=> int(1412608671) [“level”]=> string(4) “info” [“message”]=> string(20) “xmlrpc call received” } [7]=> array(3) { [“time”]=> int(1412608671) [“level”]=> string(4) “info” [“message”]=> string(45) “Method metaWeblog.getRecentPosts not relevant” } [8]=> array(3) { [“time”]=> int(1412609168) [“level”]=> string(4) “info” [“message”]=> string(20) “xmlrpc call received” } [9]=> array(3) { [“time”]=> int(1412609168) [“level”]=> string(5) “debug” [“message”]=> string(2200) “Received request: <?xml version=”1.0″ encoding=”UTF-8″?> <methodCall> <methodName>metaWeblog.newPost</methodName> <params> <param> <value> <string/> </value> </param> <param> <value> <string>xuserx</string> </value> </param> <param> <value> <string>xxxxxx</string> </value> </param> <param> <value> <struct> <member> <name>title</name> <value> <string>test 28376</string> </value> </member> <member> <name>description</name> <value> <string>test</string> </value> </member> <member> <name>post_status</name> <value> <string>publish</string> </value> </member> <member> <name>categories</name> <value> <array> <data> <value> <string>instagram</string> </value> </data> </array> </value> </member> <member> <name>mt_keywords</name> <value> <array> <data> <value> <string>ifttt_bridge</string> </value> </data> </array> </value> </member> </struct> </value> </param> <param> <value> <boolean>1</boolean> </value> </param> </params> </methodCall>” } [10]=> array(3) { [“time”]=> int(1412609168) [“level”]=> string(4) “info” [“message”]=> string(129) “Received data: title: test 28376 description: test post_status: publish categories: instagram mt_keywords: ifttt_bridge” } [11]=> array(3) { [“time”]=> int(1412609168) [“level”]=> string(5) “error” [“message”]=> string(56) “An error occurred: Unexpected response code for url ”: ” } [12]=> array(3) { [“time”]=> int(1412610444) [“level”]=> string(4) “info” [“message”]=> string(20) “xmlrpc call received” } [13]=> array(3) { [“time”]=> int(1412610444) [“level”]=> string(5) “debug” [“message”]=> string(2304) “Received request: <?xml version=”1.0″ encoding=”UTF-8″?> <methodCall> <methodName>metaWeblog.newPost</methodName> <params> <param> <value> <string/> </value> </param> <param> <value> <string>xuserx</string> </value> </param> <param> <value> <string>xxxxxx</string> </value> </param> <param> <value> <struct> <member> <name>title</name> <value> <string>this n that</string> </value> </member> <member> <name>description</name> <value> <string>testing</string> </value> </member> <member> <name>post_status</name> <value> <string>publish</string> </value> </member> <member> <name>categories</name> <value> <array> <data> <value> <string>instagram</string> </value> </data> </array> </value> </member> <member> <name>mt_keywords</name> <value> <array> <data> <value> <string>ifttt_bridge</string> </value> <value> <string>hope</string> </value></data> </array> </value> </member> </struct> </value> </param> <param> <value> <boolean>1</boolean> </value> </param> </params> </methodCall>” } [14]=> array(3) { [“time”]=> int(1412610444) [“level”]=> string(4) “info” [“message”]=> string(139) “Received data: title: this n that description: testing post_status: publish categories: instagram mt_keywords: ifttt_bridge, hope” } [15]=> array(3) { [“time”]=> int(1412610444) [“level”]=> string(5) “error” [“message”]=> string(56) “An error occurred: Unexpected response code for url ”: ” } } Hi Peter! The description field has to have the json format with the curly brackets as shown on the screenshot and as configured in the recipe. It seems that your latest test has just “testing” in this field. This can’t be processed correctly and the resolved url is “”. When trying to call this invalid url is comes to an error. I tried some special characters in the title field (@ ä / \ ” ‘. It still works, but I found out that I have to escape some characters to make sure that the resulting html is not broken. So I have to bugfix this, but I don’t think that this is related to your problem. Feel free to ask again if the problems still occur. Regards Björn Hello. I never got this working and noticed I now have the same er...

Comments

14 shown
bjoerne 2014-09-15T16:44:00+00:00

Hi Peter! It seams that the plugin tries to load the Instagram image from an invalid (or better empty) url “”. Can you check your IFTTT recipe? Does it look the same as showed on the screenshot or as the shared recipe? You could change the log level to debug to see more information. If the error is still present you could sent me the infos from the log or post it here, but be sure that you don’t post the user/password which are part of the request coming from IFTTT. And you could of cause use the “test request” feature to play around with the WordPress plugins and to find out if everything is configured correctly which may be easier than bugfixing with IFTTT. Best regards Björn

PeterBP 2014-09-16T00:25:00+00:00

Thanks for the prompt response Bjoerne. I have checked the IFTTT recipe and it says “recipe checked” so I guess it is OK. I used your one and authorised it with Instagram and the WP site. Log level is already on debug. The error occurs when testing using the test facility. Here is s sample log showing an instagram test and the local tests. —- 2014/09/16 10:19:24 AM debug Received request: <?xml version=”1.0″ ?><methodCall><methodName>metaWeblog.newPost</methodName><params><param><value><string></string></value></param><param><value><string>********</string></value></param><param><value><string>********</string></value></param><param><value><struct><member><name>title</name><value><string>Monsalvat yesterday. My dad likes this wall a lot.</string></value></member><member><name>description</name><value><string>{“Url”:” http://ift.tt/1m5G4tT” ;, “SourceUrl”:” http://ift.tt/1uDxv9U” ;} Monsalvat yesterday. My dad likes this wall a lot.</string></value></member><member><name>mt_keywords</name><value><array><data><value><string>ifttt_bridge</string></value></data></array></value></member><member><name>post_status</name><value><string>draft</string></value></member></struct></value></param><param><value><boolean>1</boolean></value></param></params></methodCall> 2014/09/16 10:19:24 AM info Received data: title: Monsalvat yesterday. My dad likes this wall a lot. description: {“Url”:” http://ift.tt/1m5G4tT” ;, “SourceUrl”:” http://ift.tt/1uDxv9U” ;} Monsalvat yesterday. My dad likes this wall a lot. post_status: draft categories: mt_keywords: ifttt_bridge 2014/09/16 10:19:24 AM error An error occurred: Unexpected response code for url ”: 2014/09/16 10:19:24 AM info xmlrpc call received 2014/09/16 10:19:24 AM debug Received request: <?xml version=”1.0″ encoding=”UTF-8″?> <methodCall> <methodName>metaWeblog.newPost</methodName> <params> <param> <value> <string/> </value> </param> <param> <value> <string>********</string> </value> </param> <param> <value> <string>********</string> </value> </param> <param> <value> <struct> <member> <name>title</name> <value> <string>test</string> </value> </member> <member> <name>description</name> <value> <string>test</string> </value> </member> <member> <name>post_status</name> <value> <string>draft</string> </value> </member> <member> <name>mt_keywords</name> <value> <array> <data> <value> <string>ifttt_bridge</string> </value> <value> <string>test post</string> </value></data> </array> </value> </member> </struct> </value> </param> <param> <value> <boolean>1</boolean> </value> </param> </params> </methodCall> 2014/09/16 10:19:24 AM info Received data: title: test description: test post_status: draft categories: mt_keywords: ifttt_bridge, test post 2014/09/16 10:19:24 AM error An error occurred: Unexpected response code for url ”: 2014/09/16 10:19:24 AM info xmlrpc call received 2014/09/16 10:19:24 AM debug Received request: <?xml version=”1.0″ encoding=”UTF-8″?> <methodCall> <methodName>metaWeblog.newPost</methodName>...

PeterBP 2014-09-16T00:36:00+00:00

Forgot to say, I tested also with all plugins except your ones turned off, and still got the error. P

PeterBP 2014-09-16T01:32:00+00:00

Worked it out I think. To get the bridge working, it seems to be mandatory to assign a category. Instant success. Then to get the Instagram working, I assigned a category at IFTTT and removed any changes I made to the description (I’d added the caption but probably done it incorrectly). Works! Looking good, thanks Björn!

PeterBP 2014-09-16T01:33:00+00:00

Resolved I think.

bjoerne 2014-09-16T02:37:00+00:00

Great! Applying a category is optional and it should work without a category.

PeterBP 2014-10-06T16:39:00+00:00

Hi Bjoerne, since last post, it has stopped working twice. I go in and find no logs and missed instagram posts. Usually “rebooted” by reactivating the WordPress channel at IFTTT. Trouble shooting now as launch is soon. PHP5.4.32 on Litespeed – it has never managed to make a WP post, but was successful posting the image which is all I needed for the gallery to work. – currently getting the same error while testing: An error occurred: Unexpected response code for url '': – I wonder if it’s a sanitizing issue of the instagram caption? It seems to stop working when the user posts an @someone link within their post. For now I have switched of the caption posting as title at IFTTT. – other than that I am at a loss! Hope you might be able to spot something wrong below. Following is the dump – regards, Peter array(16) { [0]=> array(3) { [“time”]=> int(1412608668) [“level”]=> string(4) “info” [“message”]=> string(20) “xmlrpc call received” } [1]=> array(3) { [“time”]=> int(1412608668) [“level”]=> string(4) “info” [“message”]=> string(45) “Method metaWeblog.getRecentPosts not relevant” } [2]=> array(3) { [“time”]=> int(1412608669) [“level”]=> string(4) “info” [“message”]=> string(20) “xmlrpc call received” } [3]=> array(3) { [“time”]=> int(1412608669) [“level”]=> string(4) “info” [“message”]=> string(45) “Method metaWeblog.getRecentPosts not relevant” } [4]=> array(3) { [“time”]=> int(1412608670) [“level”]=> string(4) “info” [“message”]=> string(20) “xmlrpc call received” } [5]=> array(3) { [“time”]=> int(1412608670) [“level”]=> string(4) “info” [“message”]=> string(45) “Method metaWeblog.getRecentPosts not relevant” } [6]=> array(3) { [“time”]=> int(1412608671) [“level”]=> string(4) “info” [“message”]=> string(20) “xmlrpc call received” } [7]=> array(3) { [“time”]=> int(1412608671) [“level”]=> string(4) “info” [“message”]=> string(45) “Method metaWeblog.getRecentPosts not relevant” } [8]=> array(3) { [“time”]=> int(1412609168) [“level”]=> string(4) “info” [“message”]=> string(20) “xmlrpc call received” } [9]=> array(3) { [“time”]=> int(1412609168) [“level”]=> string(5) “debug” [“message”]=> string(2200) “Received request: <?xml version=”1.0″ encoding=”UTF-8″?> <methodCall> <methodName>metaWeblog.newPost</methodName> <params> <param> <value> <string/> </value> </param> <param> <value> <string>xuserx</string> </value> </param> <param> <value> <string>xxxxxx</string> </value> </param> <param> <value> <struct> <member> <name>title</name> <value> <string>test 28376</string> </value> </member> <member> <name>description</name> <value> <string>test</string> </value> </member> <member> <name>post_status</name> <value> <string>publish</string> </value> </member> <member> <name>categories</name> <value> <array> <data> <value> <string>instagram</string> </value> </data> </array> </value> </member> <member> <name>mt_keywords</name> <value> <array> <data> <value> <string>ifttt_bridge</string> </value> </data> </array> </value> </member> </struct> </value> </param>...

bjoerne 2014-10-06T17:22:00+00:00

Hi Peter! The description field has to have the json format with the curly brackets as shown on the screenshot and as configured in the recipe. It seems that your latest test has just “testing” in this field. This can’t be processed correctly and the resolved url is “”. When trying to call this invalid url is comes to an error. I tried some special characters in the title field (@ ä / \ ” ‘. It still works, but I found out that I have to escape some characters to make sure that the resulting html is not broken. So I have to bugfix this, but I don’t think that this is related to your problem. Feel free to ask again if the problems still occur. Regards Björn

livadas 2014-10-12T23:10:00+00:00

Hello. I never got this working and noticed I now have the same error as Peter. The test doesn’t work and my recipe is triggering. PHP Version 5.2.17 2014/10/12 10:38:21 PM info xmlrpc call received 2014/10/12 10:38:21 PM info Received data: title: Test post description: http://ift.tt/1vkDbZv http://ift.tt/1vZSTGf via livadas post_status: publish categories: instagram mt_keywords: ifttt_bridge 2014/10/12 10:38:21 PM error An error occurred: Unexpected response code for url '':

livadas 2014-10-12T23:12:00+00:00

Note – I deleted this instagram photo so that is not the issue.

bjoerne 2014-10-13T18:34:00+00:00

Hi! The description has to have a special format! You can find it on the screenshot or in the shared recipe. Otherwise the Instagram data can’t be resolved. Cheers, Björn

livadas 2014-10-13T18:51:00+00:00

Thank you bjoerne. The error still says: Warning: Invalid argument supplied for foreach() in /wp-content/plugins/ifttt-bridge/admin/class-ifttt-bridge-admin.php on line 110 I have checked my recipe to match yours. https://ifttt.com/myrecipes/personal/15003793 Debug log: 2014/10/13 06:47:54 PM info Received data: title: description: post_status: publish categories: mt_keywords: ifttt_bridge 2014/10/13 06:47:54 PM error An error occurred: Unexpected response code for url ”:

bjoerne 2014-10-14T04:49:00+00:00

How was this request triggered? By IFTTT oder with the test request feature? The test request feature exists to simulate IFTTT and has nothing to do with the productive IFTTT system. You could even use it without having an IFTTT account. The warning: Invalid argument supplied for foreach() in /wp-content/plugins/ifttt-bridge/admin/class-ifttt-bridge-admin.php on line 110 doesn’t sound good. Could you delete the option ‘ifttt_bridge_log’ again manually so that the log is reset. I’ve never had this error myself, but it didn’t happen the first time for you, did it?

PeterBP 2014-12-08T13:19:00+00:00

Hi Bjoerne, just to let you know all has been working well for about two months now, since I removed the caption short code. I still suspect the client’s use of emoticons (etc) was tripping it up. Thanks for your help.