Title: Parse error after activation Last modified: August 22, 2016 --- # Parse error after activation * [livadas](https://wordpress.org/support/users/livadas/) * (@livadas) * [11 years, 8 months ago](https://wordpress.org/support/topic/parse-error-after-activation-2/) * Parse error: syntax error, unexpected ‘[‘, expecting ‘)’ in /wp-content/plugins/ ifttt-instagram-gallery/public/class-ifttt-instagram-gallery.php on line 313 * [https://wordpress.org/plugins/ifttt-instagram-gallery/](https://wordpress.org/plugins/ifttt-instagram-gallery/) Viewing 12 replies - 1 through 12 (of 12 total) * Plugin Author [bjoerne](https://wordpress.org/support/users/bjoerne/) * (@bjoerne) * [11 years, 8 months ago](https://wordpress.org/support/topic/parse-error-after-activation-2/#post-5239270) * Thanks for your post! I will have a closer look today. Which PHP version do you use? * Thread Starter [livadas](https://wordpress.org/support/users/livadas/) * (@livadas) * [11 years, 8 months ago](https://wordpress.org/support/topic/parse-error-after-activation-2/#post-5239271) * Thanks for your quick reply! I am using PHP5. * Plugin Author [bjoerne](https://wordpress.org/support/users/bjoerne/) * (@bjoerne) * [11 years, 8 months ago](https://wordpress.org/support/topic/parse-error-after-activation-2/#post-5239281) * I used a syntax which came up with PHP 5.4. But I fixed the issue and published a new version of the plugin (1.0.1). Could you try it and let me know whether it works or not? Thanks again! Björn * Thread Starter [livadas](https://wordpress.org/support/users/livadas/) * (@livadas) * [11 years, 8 months ago](https://wordpress.org/support/topic/parse-error-after-activation-2/#post-5239318) * Hi, Thanks for working on this. I updated to 1.0.1. Now I’m seeing: * Parse error: syntax error, unexpected ‘:’ in /wp-content/plugins/ifttt-instagram- gallery/public/class-ifttt-instagram-gallery-widget.php on line 66 * Plugin Author [bjoerne](https://wordpress.org/support/users/bjoerne/) * (@bjoerne) * [11 years, 8 months ago](https://wordpress.org/support/topic/parse-error-after-activation-2/#post-5239333) * Thanks again for this hint. I fixed this in version 1.0.2 which is available now. * Thread Starter [livadas](https://wordpress.org/support/users/livadas/) * (@livadas) * [11 years, 8 months ago](https://wordpress.org/support/topic/parse-error-after-activation-2/#post-5239434) * Thank you for the update. The plugin is now activated successfully with no errors. However, [my gallery ](http://livadasproperties.com/?page_id=181)is not loading. I tried adding the widget to the sidebar and also using the short code. You can see I have posts sent from IFTTT with the tag ifttt_wordpress_bridge. Thank you for looking at this! * Plugin Author [bjoerne](https://wordpress.org/support/users/bjoerne/) * (@bjoerne) * [11 years, 8 months ago](https://wordpress.org/support/topic/parse-error-after-activation-2/#post-5239437) * The screenshot of the recipe was not correct. The tag has to be ‘ifttt_bridge’. I’m very sorry! I updated the screenshot. * Thread Starter [livadas](https://wordpress.org/support/users/livadas/) * (@livadas) * [11 years, 8 months ago](https://wordpress.org/support/topic/parse-error-after-activation-2/#post-5239456) * I’ve updated my tag to ifttt_bridge but the plugin is no longer working for me. Warning: Invalid argument supplied for foreach() in /wp-content/plugins/ifttt- bridge/admin/class-ifttt-bridge-admin.php on line 110 * Plugin Author [bjoerne](https://wordpress.org/support/users/bjoerne/) * (@bjoerne) * [11 years, 8 months ago](https://wordpress.org/support/topic/parse-error-after-activation-2/#post-5239463) * This time I don’t know what happens. Can you find out more about the variable $log in line 110 of /wp-content/plugins/ifttt-bridge/admin/class-ifttt-bridge- admin.php? You could add the following above this line. * `var_dump($log)`; * Then there should be some output on the admin page wich could give us a hint. * Thread Starter [livadas](https://wordpress.org/support/users/livadas/) * (@livadas) * [11 years, 8 months ago](https://wordpress.org/support/topic/parse-error-after-activation-2/#post-5239476) * Thanks for continuing to help me, bjoerne! Here is the dump of $log: * string(5514) “a:30:{i:0;a:3:{s:4:”time”;i:1409448982;s:5:”level”;s:4:”info”;s: 7:”message”;s:20:”xmlrpc call received”;}i:1;a:3:{s:4:”time”;i:1409448982;s:5:” level”;s:4:”info”;s:7:”message”;s:44:”Method metaWeblog.getCategories not relevant”;} i:2;a:3:{s:4:”time”;i:1409448983;s:5:”level”;s:4:”info”;s:7:”message”;s:20:”xmlrpc call received”;}i:3;a:3:{s:4:”time”;i:1409448983;s:5:”level”;s:4:”info”;s:7:” message”;s:457:”Received data: title: bkrumbles : The view at Daily Refresher is very nice description:
via [bkrumbles](http://ift.tt/1B68bMS) August 30, 2014 at 09:27PM
post_status: publish categories: instagram, nearby mt_keywords: instagram, nearby, ifttt_bridge”;}i:4;a:3:{s:4:”time”;i:1409448983; s:5:”level”;s:5:”error”;s:7:”message”;s:56:”An error occurred: Unexpected response code for url ”: “;}i:5;a:3:{s:4:”time”;i:1409448989;s:5:”level”;s:4:”info”;s: 7:”message”;s:20:”xmlrpc call received”;}i:6;a:3:{s:4:”time”;i:1409448989;s:5:” level”;s:4:”info”;s:7:”message”;s:44:”Method metaWeblog.getCategories not relevant”;} i:7;a:3:{s:4:”time”;i:1409448990;s:5:”level”;s:4:”info”;s:7:”message”;s:20:”xmlrpc call received”;}i:8;a:3:{s:4:”time”;i:1409448990;s:5:”level”;s:4:”info”;s:7:” message”;s:440:”Received data: title: bradym888 : Seeing Magic Moo tonight! description:
via [bradym888](http://ift.tt/1B68d7p) August 30, 2014 at 09:34PM
post_status: publish categories: instagram, nearby mt_keywords: instagram, nearby, ifttt_bridge”;}i:9;a:3:{s:4:”time”;i:1409448990; s:5:”level”;s:5:”error”;s:7:”message”;s:56:”An error occurred: Unexpected response code for url ”: “;}i:10;a:3:{s:4:”time”;i:1409448995;s:5:”level”;s:4:”info”;s: 7:”message”;s:20:”xmlrpc call received”;}i:11;a:3:{s:4:”time”;i:1409448995;s: 5:”level”;s:4:”info”;s:7:”message”;s:44:”Method metaWeblog.getCategories not relevant”;}i:12;a:3:{s:4:”time”;i:1409448996;s:5:”level”;s:4:”info”;s:7:”message”; s:20:”xmlrpc call received”;}i:13;a:3:{s:4:”time”;i:1409448996;s:5:”level”;s: 4:”info”;s:7:”message”;s:411:”Received data: title: livadas : description:
via [livadas](http://ift.tt/1B68do2) August 30, 2014 at 09:35PM
post_status: publish categories: instagram, nearby mt_keywords: instagram, nearby, ifttt_bridge”;}i:14;a:3:{s:4:”time”;i:1409448996; s:5:”level”;s:5:”error”;s:7:”message”;s:56:”An error occurred: Unexpected response code for url ”: “;}i:15;a:3:{s:4:”time”;i:1409451027;s:5:”level”;s:4:”info”;s: 7:”message”;s:20:”xmlrpc call received”;}i:16;a:3:{s:4:”time”;i:1409451027;s: 5:”level”;s:4:”info”;s:7:”message”;s:44:”Method metaWeblog.getCategories not relevant”;}i:17;a:3:{s:4:”time”;i:1409451028;s:5:”level”;s:4:”info”;s:7:”message”; s:20:”xmlrpc call received”;}i:18;a:3:{s:4:”time”;i:1409451028;s:5:”level”;s: 4:”info”;s:7:”message”;s:596:”Received data: title: mskatrinalim : Yeah… So this happened… Biscuits, @fieldroast apple-sage vegan sausage, peppers, onions and chickpea gravy #vegan #whatveganseat #veganfoodshare #veganlatenightfood #fatkid description:
via [mskatrinalim](http://ift.tt/1qVeTSo) August 30, 2014 at 09:36PM
post_status: publish categories: instagram, nearby mt_keywords: instagram, nearby, ifttt_bridge”;}i:19;a:3:{s:4:”time”;i:1409451028; s:5:”level”;s:5:”error”;s:7:”message”;s:56:”An error occurred: Unexpected response code for url ”: “;}i:20;a:3:{s:4:”time”;i:1409451030;s:5:”level”;s:4:”info”;s: 7:”message”;s:20:”xmlrpc call received”;}i:21;a:3:{s:4:”time”;i:1409451030;s: 5:”level”;s:4:”info”;s:7:”message”;s:44:”Method metaWeblog.getCategories not relevant”;}i:22;a:3:{s:4:”time”;i:1409451031;s:5:”level”;s:4:”info”;s:7:”message”; s:20:”xmlrpc call received”;}i:23;a:3:{s:4:”time”;i:1409451031;s:5:”level”;s: 4:”info”;s:7:”message”;s:449:”Received data: title: bizzmaaah : Wedding crafting hard. @rodeobot description:
via [bizzmaaah](http://ift.tt/1ucWsbj) August 30, 2014 at 09:48PM
post_status: publish categories: instagram, nearby mt_keywords: instagram, nearby, ifttt_bridge”;}i:24;a:3:{s:4:”time”;i:1409451031; s:5:”level”;s:5:”error”;s:7:”message”;s:56:”An error occurred: Unexpected response code for url ”: “;}i:25;a:3:{s:4:”time”;i:1409451034;s:5:”level”;s:4:”info”;s: 7:”message”;s:20:”xmlrpc call received”;}i:26;a:3:{s:4:”time”;i:1409451034;s: 5:”level”;s:4:”info”;s:7:”message”;s:44:”Method metaWeblog.getCategories not relevant”;}i:27;a:3:{s:4:”time”;i:1409451035;s:5:”level”;s:4:”info”;s:7:”message”; s:20:”xmlrpc call received”;}i:28;a:3:{s:4:”time”;i:1409451035;s:5:”level”;s: 4:”info”;s:7:”message”;s:473:”Received data: title: rachelgonzalez1 : Wedding fun” * Warning: Invalid argument supplied for foreach() in /wp-content/plugins/ ifttt-bridge/admin/class-ifttt-bridge-admin.php on line 111 * Plugin Author [bjoerne](https://wordpress.org/support/users/bjoerne/) * (@bjoerne) * [11 years, 8 months ago](https://wordpress.org/support/topic/parse-error-after-activation-2/#post-5239485) * Hi! The log you posted ends suddenly at a quote. That leeds to an error because the log is not a correct serialized value. It can’t be unserialized by WordPress and is, at the line of code you mentioned, a string instead of an array. I found a lot about issues with quotes and serialization on the web, but I myself don’t have problems with it. Maybe it’s again something which has been fixed in newer PHP versions. Can you give me your exact PHP version? You can find it out by loading a PHP file with the following content on your webserver and invoking it: * ```