Maybe the page was cached. But good to read that it's fine now. If this question can be closed, please accept an answer. Thank you.
It's been almost a week. What happens? Is it time to uninstall Widgetkit and start looking for an alternative?
Can Yootheme please provide any information on this issue?
All we know is, that Instagram changed its API and Yootheme is working on this issue. ????
When will You provide a solution?
Will there be any solution at all?
Thank You for a quick statement.
Instagram seems to have changed something in the API. The developers are currently investigating this issue and an update shall be provided once a fix is available. I don't have an ETA, though, as this is still under investigation.
Same on Joomla
Yes, it affects both Widgetkit for Joomla and WordPress as they are using the same API of Instagram.
Unfortunately, I don't have an update by now, I'm sorry. The developers are still working on getting this issue resolved caused by an API change on the side of Instagram.
There shall be a partial fix in the next release, also see this update.
I'm sorry for the inconveniences
Please...Can a developer provide an answer?
is there a hotfix for this? Can we change something in the current widgetkit to make the feed working again?
Do we need to make it clearer that this is an important bug to fix. Do we need dozens of replies before this gets patched? I've got multiple sites with this problem.
Any update on this problem ?
I have the same issue here as well. At first I thought it was broken after the update. However I finally realized that it is not. I wish that yootheme can provide an update on this as soon as possible.
Hello, Can you please speed up the resolving of this issue. This is a really painful problem to a lot of users. Thanks
Widgetkit has been updated to version 2.9.13 including an update to the Instagram content provide. Please update to the latest version.
I don't quite see the problem with the part following "Följ vår vardag @calcioakademin". This is what I see in Chrome
Can you please explain what behaves different than you expected?
I didn't saw it yesterday (in Firefox) but today I do! GREAT!!