PeterBP
Forum Replies Created
-
Forum: Plugins
In reply to: [IFTTT Instagram Gallery] Instagram URLsHi, fixed it myself by altering a function in class-ifttt-instagram-gallery.php to this, to lose the url query. Probably a cleaner way…
public function load_instagram_image( $content_struct ) { // Ingredients: Caption, Url, SourceUrl, CreatedAt, EmbedCode $title = htmlspecialchars( $content_struct['title'] ); $description = $content_struct['description']; $description_decoded = json_decode( $description, true ); $instagram_url = $this->get_final_url( $description_decoded['Url'] ); $parts = parse_url($instagram_url); $instagram_url = $parts['scheme'].'://'.$parts['host'].$parts['path']; $image_url = $this->get_final_url( $description_decoded['SourceUrl'] ); $parts = parse_url($image_url); $image_url = $parts['scheme'].'://'.$parts['host'].$parts['path']; $filename = $this->get_filename( $image_url ); $parts = parse_url($filename); $filename = $parts['scheme'].'://'.$parts['host'].$parts['path']; $response = wp_remote_get( $image_url ); $bits = $response['body']; $this->upload_image( $filename, $title, $bits, $instagram_url ); $this->remove_old_images(); }Forum: Plugins
In reply to: [IFTTT Bridge for WordPress] Some trouble making new postsHi 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.Forum: Plugins
In reply to: [IFTTT Bridge for WordPress] Some trouble making new postsHi 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 ”: ” } }
Forum: Plugins
In reply to: [IFTTT Bridge for WordPress] Some trouble making new postsResolved I think.
Forum: Plugins
In reply to: [IFTTT Bridge for WordPress] Some trouble making new postsWorked 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!
Forum: Plugins
In reply to: [IFTTT Bridge for WordPress] Some trouble making new postsForgot to say, I tested also with all plugins except your ones turned off, and still got the error.
PForum: Plugins
In reply to: [IFTTT Bridge for WordPress] Some trouble making new postsThanks 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 AMdebug
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_bridge2014/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 post2014/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, test2014/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,
PeterForum: Plugins
In reply to: [Plugin: Cimy User Extra Fields] Cannot update fields >#11Hi Cimmo,
love your work!Having the same issue as joshkadis here. WP 2.8.5, PHP&MYSQL 5+
Making any changes in extra fields 11 and higher doesn’t work, it is necessary to edit the database manually for those.The Change Order doesn’t work either, so changing the f-order using phpmyadmin.
I have upgraded to 1.5.3 but the problem is still there.
thanks,
Peter