bjoerne

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

Hi!
Sorry that I didn’t answer before, I missed to configure the support forum to be notified.
The solution of Andreas and my plugin are based on the same idea and might be even based on the same source code. The difference is only that Andreas (and the original creator) prefers a theme and I prefer a plugin. The behavior is exactly the same.
Sorry again for the late response!!
Bj?rn

Hi!
Sorry that I didn’t answer before, I missed to configure to be notified.
I created the plugin for the scenario that every language has a URL which is different from the root. There is support for a default language (e.g. English), but in my case this is not on the root site, but on /en.
Sorry again for this late answer which probably won’t help you anymore
Bj?rn

Resolved

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

Hi!

If the whole site hogwine.com is running in WordPress the correct url may be just hogwine.com.

IFTTT Bridge may be a good solution in your case. But the bridge just brings the IFTTT data into WordPress as a WordPress action. To get the IFTTT data “alive” you have to hook into this action and do something with the IFTTT data. Usually you do this with a custom plugin which you have to develop.

Hi!
I updated the ifttt-bridge plugin. The log didn’t work anymore after it had been emptied. I don’t think that this is connected to your problem, but it makes sense to update anyway.
Regards
Bj?rn

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:

<?php
phpinfo();

If you want to get rid of this error you can use the following database script:

DELETE FROM wp_options WHERE option_name = "ifttt_bridge_log";

This removes the log from the database. The log is recreated automatically when there is something logged. You could remove the log and play around with the test request feature of the bridge. Maybe you can find out more, e.g. if there are Instagram images which work fine and which ones break the code.

Thanks for you patience and passion to get this running ??

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.

The screenshot of the recipe was not correct. The tag has to be ‘ifttt_bridge’. I’m very sorry! I updated the screenshot.

Thanks again for this hint. I fixed this in version 1.0.2 which is available now.

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

Thanks for your post! I will have a closer look today. Which PHP version do you use?

If you yourself post something on Facebook you could use the redirect target instead of your homepage. For example if you post on an English Facebook page you could use https://www.example.com/en/.

But even if you mention your homepage on Facebook, Facebook follows the redirect and uses the meta tags of the redirect target.

Just configure like this:

en=https://xx.mysite.com/

Thanks for your question. I will enhance the explanation on the plugin description page and on the option page to make this more clear.