Tigran Nazaryan

@annettedom
Feed in the footer of the homepage is displayed normally. The conflict fixed.
https://www.pikebrothers.com/

As for the second feed, please change the privacy of WP page to public and select already existing feed instead of the deleted one. The error message is clear.

@annettedom,

there is a conflict with some caching/minify plugin, most probably bwp-minify. That plugin merges and minifies JS files of other plugins, but it missed instagram’s JS files.

there should be wdi_instagram.js, wdi_frontend.js and wdi_responsive.js files included in the frontend. Please deactivate bwp-minify to see if instagram feed displayed. If so, you need to configure minify plugin correctly, so that it does not remove instagram’s scripts.

@annettedom, can you please give the link so that we can see what is wrong there?

hi @annettedom,

I guess confusion comes from the private page, not the private feed in it. Can you view the feed when logged in ?
If so, the feed is ok. Just we make the page with the feed private so that first admin can test it, without being displayed in menu.

Please make the page public and the page with the feed in it will be visible to everyone.
https://gyazo.com/0a4ab6d159c5dc1db3d01a8949480ec3

• This reply was modified 7 years, 2 months ago by Tigran Nazaryan.

If there is a case when the feed in a page sometimes throws this error and sometimes not, this may be because of two reasons.
1. slow connection
2. user feed changed from public to private or vice versa

Please check which of these cases you have.

Hi @klsbo!

Thanks for noting this issue.
We changed how the errors are visible in the frontend (1.2.12), but added a bug.

The error message "Something is wrong. Response takes too long or there is JS error. ..."
should be visible only when there are JS errors or connection errors (if no response from API withing 20 sec). However now there is a new bug: when one of the users in feed is private, this general error message is displayed and the whole feed is not visible. We will fix this ASAP. We will add admin-visible message only, that feed contains some private user’s data. But this message will not stop other user’s media from loading. Thank you very much for discovering this bug.

As for your second request about adding a private user, we will add warning when trying to add private user to feed in one of the future versions.

Hi,

thanks for choosing Instagram Feed WD! We appreciate your feedback and constantly iterating to improve our product.

Currently there are several options when clicking media: opening lightbox, redirecting to Instagram post, or redirecting to custom URL (same URL for the whole feed).
There were some feature requests to make separate redirection to custom URL for each media. However this will complicate UX because media is dynamic.

On the other hand, the feature you want is possible to implement partially.
We will make the link in the bio clickable as well as will display “website” link next to the bio text in the header (there is a bug, it is not visible now anywhere).

We can make links in captions clickable, even though Instagram itself doesn’t allow it :). However we can do it perhaps only in lightbox, image optimizer or blog style views.
Please note that we can’t pull the link from the caption and make redirection on clicking media to that URL. We will do only for clicking on the link in caption itself, not clicking on media.

We will add your request to the backlog. The first part (bio and website) will be implemented soon, the cations – later. But before implementing this feature, there are a lot of other improvements not released yet. So please stay tuned.
Thanks again for this request.

Thanks for your comments,

We checked the problem again and discovered that there are definitely some things to fix in Google Analytics WD plugin. Plugins_loaded hook is used where it is not necessary and Google SDK is loaded too early. We will fix this issue ASAP. However it will require refactoring of large chunks of code, so it may take some time. The fix will be released within several weeks.

Thank you again very much! We owe you one ??

Hi,

thanks for your suggestion. We took a look at the issue, but could not reproduce the error.

Can you please provide typical stack trace for the code throwing error?
Does it include plugins_loaded and inithooks actions?

If backup code runs earlier, we will move loading of Google SDK into these two hooks.
Since GAWD plugin needs Google API data in it’s core functionality, I don’t think we can include the library later.

• This reply was modified 7 years, 4 months ago by Tigran Nazaryan.
• This reply was modified 7 years, 4 months ago by Tigran Nazaryan.

hi @davidanderson,

Thanks for noting this issue. We are aware of it.

Currently there are many plugins using Google SDK, its different versions and its different services and other third-party dependencies. There are new and old versions of Google SDK as well as its versions for PHP 5.4+ and PHP 5.5+.

Google SDK has quite a large size. Some plugins remove its services and do not load whole SDK. Google Analytics checks whether any plugin loaded SDK before, and if it is so, our plugin does not load SDK and uses other plugin’s instance. We hope that any plugin which uses Google SDK, includes its full version. And we also do not strip any service needed for other plugins from our version. Note that we can’t prefix Google SDK. Therefore there is only one instance of SDK running in WP code, and it needs to be whole.

We need to find optimal solution which causes minimal compatibility issues.
Note, that Web-Dorado also has several other plugins using Google SDK, including Backup plugin which is compatible with Google Analytics WD.

So we decided to
1). Use it’s latest version
2). PHP 5.4+
3.) load SDK fully
4). load it quite early

Even if we include Google SDK later, this will still cause compatibility issue with your plugin. We can’t switch back to the older version, because of compatibility issues with other plugins. Can’t you move forward and update the Google library and include it’s full version ?

• This reply was modified 7 years, 4 months ago by Tigran Nazaryan.

Yes, sure

hi @myleent,
thanks for choosing Instagram Feed WD plugin!
We appreciate your feedback.
What can we do to deserve 5 star? ??

hi @viroproject,

thanks for choosing Instagram Feed WD plugin!

The plugin is compatible with multisite WP. There might be a problem when creating database tables because of permissions or some other reasons. Please deactivate and activate the plugin in the site where you have this error. If after that you are still unable create or edit feed, please contact Web-Dorado using the form on this page

hi @freddyjones,

thanks for choosing Instagram Feed WD plugin!

There is no direct limit of number of users in the feed. However maximal length of the corresponding column in the database is limited by 2000 characters, which roughly corresponds to 40 users/hashtags. Is’t that enough for practical use? ??

hi @patrickjim,

thanks for using Instagram Feed WD plugin!

Since you need support for paid version, please write directly to Web-Dorado using the contact form on this page.