Title: acleach's Replies | WordPress.org

---

# acleach

  [  ](https://wordpress.org/support/users/acleach/)

 *   [Profile](https://wordpress.org/support/users/acleach/)
 *   [Topics Started](https://wordpress.org/support/users/acleach/topics/)
 *   [Replies Created](https://wordpress.org/support/users/acleach/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/acleach/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/acleach/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/acleach/engagements/)
 *   [Favorites](https://wordpress.org/support/users/acleach/favorites/)

 Search replies:

## Forum Replies Created

Viewing 15 replies - 1 through 15 (of 23 total)

1 [2](https://wordpress.org/support/users/acleach/replies/page/2/?output_format=md)
[→](https://wordpress.org/support/users/acleach/replies/page/2/?output_format=md)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WPtouch - Make your WordPress Website Mobile-Friendly] Favicon and WPTouch](https://wordpress.org/support/topic/favicon-and-wptouch-2/)
 *  Thread Starter [acleach](https://wordpress.org/support/users/acleach/)
 * (@acleach)
 * [1 year, 4 months ago](https://wordpress.org/support/topic/favicon-and-wptouch-2/#post-18271595)
 * Although this should have worked — I examined the served code and Google’s use
   of it — maybe I was impatient for Google to reindex the site. It’s entirely possible
   that my reindex request didn’t happen as quickly as it normally does.
 * I ended up having a brainwave and adding the required lines into my own custom
   plugin with _**add\_action(‘wp\_head’,…)**_ so they are served for all themes.
   Having requested reindexing again, the search results now show the correct icon.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WPtouch - Make your WordPress Website Mobile-Friendly] Favicon and WPTouch](https://wordpress.org/support/topic/favicon-and-wptouch-2/)
 *  Thread Starter [acleach](https://wordpress.org/support/users/acleach/)
 * (@acleach)
 * [1 year, 4 months ago](https://wordpress.org/support/topic/favicon-and-wptouch-2/#post-18266242)
 * Thanks! That certainly looks like it will do the trick — the image at that location(
   or “…/wptouch/…”) is what Google has decided to use. I wondered where it was 
   getting it from.
 * I’ve changed it, and shouldn’t have to wait very long to see that it works (when
   I’ll be very happy to mark this as Resolved).
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[10Web Social Post Feed] I need to refresh Cache daily](https://wordpress.org/support/topic/i-need-to-refresh-cache-daily/)
 *  [acleach](https://wordpress.org/support/users/acleach/)
 * (@acleach)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/i-need-to-refresh-cache-daily/#post-16527434)
 * My feed usually updates around 6:30pm daily, but I haven’t found where this is
   set or triggered.
 * Or at least, it did until yesterday, when that didn’t happen. A manual refresh
   today now shows “There are no items in this feed.”
 * _Sigh._ I guess Facebook has broken the plug-in again.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[10Web Social Post Feed] Version 1.2.5](https://wordpress.org/support/topic/version-1-2-5/)
 *  [acleach](https://wordpress.org/support/users/acleach/)
 * (@acleach)
 * [4 years, 1 month ago](https://wordpress.org/support/topic/version-1-2-5/#post-15648720)
 * [@noddemix](https://wordpress.org/support/users/noddemix/) No, it means they’ve
   just broken it again by putting an unapproved version live.
 * It should be possible to have a development process where a version is approved
   _before_ being released for the community to use, but this “Still in development”
   seems to happen with depressing regularity.
 * Pity, because this plug-in does everything I want, except for this behaviour.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[10Web Social Post Feed] v1.2.1 Timeline videos cause issues in PopupBox](https://wordpress.org/support/topic/v1-2-1-timeline-videos-cause-issues-in-popupbox/)
 *  Thread Starter [acleach](https://wordpress.org/support/users/acleach/)
 * (@acleach)
 * [4 years, 7 months ago](https://wordpress.org/support/topic/v1-2-1-timeline-videos-cause-issues-in-popupbox/#post-15026256)
 * No: there are no further issues with Facebook videos. I should have returned 
   to this and marked it as resolved (which I will do now).
 * Thank you for your attention here.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[10Web Social Post Feed] v1.2.1 Timeline videos cause issues in PopupBox](https://wordpress.org/support/topic/v1-2-1-timeline-videos-cause-issues-in-popupbox/)
 *  Thread Starter [acleach](https://wordpress.org/support/users/acleach/)
 * (@acleach)
 * [5 years ago](https://wordpress.org/support/topic/v1-2-1-timeline-videos-cause-issues-in-popupbox/#post-14561135)
 * Thanks for the update.
 * I changed the option to “Do nothing” (which caused entries to do nothing) and
   then back to “Redirect to Facebook” and it appears to have worked: clicking the
   still image now opens a new tab for Facebook. Hopefully, now that it no longer
   uses the `admin-ajax.php` call it should also fix Google’s issues.
 * I’ll mark this as resolved once Google have confirmed all is well with their 
   indexing.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[10Web Social Post Feed] Getting v1.2.0 to reload FB content](https://wordpress.org/support/topic/getting-v1-2-0-to-reload-fb-content/)
 *  Thread Starter [acleach](https://wordpress.org/support/users/acleach/)
 * (@acleach)
 * [5 years ago](https://wordpress.org/support/topic/getting-v1-2-0-to-reload-fb-content/#post-14555866)
 * I have found the “Reset cache” button which works and causes new posts to be 
   collected from Facebook.
 * It would be really helpful to know how the plugin schedules its own refreshes.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[10Web Social Post Feed] (#12) description field is deprecated for versions v3.3 and higher.](https://wordpress.org/support/topic/12-description-field-is-deprecated-for-versions-v3-3-and-higher/)
 *  [acleach](https://wordpress.org/support/users/acleach/)
 * (@acleach)
 * [5 years, 1 month ago](https://wordpress.org/support/topic/12-description-field-is-deprecated-for-versions-v3-3-and-higher/#post-14444055)
 * If I can interrupt here again, I’ve done some investigation [on my thread](https://wordpress.org/support/topic/12-description-field-is-deprecated-for-versions-v3-3-and-higher-2/).
 * This is Facebook, not Instagram, and the library file is WDW_FFWD_Library.php.
 * The token issue appears to be caused by requesting the deprecated fields. I’ve
   removed all the deprecated fields from the request in WDFacebookFeed.php and 
   I no longer have a #12 error, nor is the token invalidated after each request.
   Removing them one at a time caused the error message to change, referencing a
   different deprecated field until they were all removed. However, I can’t get 
   refreshed data stored by the plugin, so the feed displayed in the widget remains
   out of date.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[10Web Social Post Feed] (#12) description field is deprecated for versions v3.3 and higher.](https://wordpress.org/support/topic/12-description-field-is-deprecated-for-versions-v3-3-and-higher-2/)
 *  Thread Starter [acleach](https://wordpress.org/support/users/acleach/)
 * (@acleach)
 * [5 years, 1 month ago](https://wordpress.org/support/topic/12-description-field-is-deprecated-for-versions-v3-3-and-higher-2/#post-14443938)
 * OK. I believe I’ve found what to do with `$description` and the other deprecated
   fields and it looks like this will fix the token issue (that is, trying to fetch
   deprecated fields caused the token error).
 * Removing the all deprecated fields from the request to Facebook no longer reports
   an error, nor does it invalidate the token.
 * I’ve amended how the deprecated fields like `$description` are set from the retrieved
   data, using the `['attachments']` array as described in the [Facebook deprecation notice](https://developers.facebook.com/docs/graph-api/changelog/version3.3/#pages),
   and no errors are reported.
 * However, I still can’t get new data from Facebook — the `wp_wd_fb_data` table
   is not updated. Clicking **Reset cache** on the Options page shows “Success”,
   but nothing is stored. This may be because the Facebook `type` has fundamentally
   changed with the deprecation and how it is set at around line 817 of WDFacebookFeed.
   php needs to be reworked: it’s got more complicated.
    -  This reply was modified 5 years, 1 month ago by [acleach](https://wordpress.org/support/users/acleach/).
      Reason: Found the deprecated fields in the plugin code
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[10Web Social Post Feed] (#12) description field is deprecated for versions v3.3 and higher.](https://wordpress.org/support/topic/12-description-field-is-deprecated-for-versions-v3-3-and-higher-2/)
 *  Thread Starter [acleach](https://wordpress.org/support/users/acleach/)
 * (@acleach)
 * [5 years, 1 month ago](https://wordpress.org/support/topic/12-description-field-is-deprecated-for-versions-v3-3-and-higher-2/#post-14443686)
 * [@kimabaghdasaryan](https://wordpress.org/support/users/kimabaghdasaryan/) You’ve
   asked [elsewhere](https://wordpress.org/support/topic/12-description-field-is-deprecated-for-versions-v3-3-and-higher/#post-14443609)
   for someone to alter plugin code and check database values. I’m happy to do that
   if no-one else is confident to do so: but I’m using the Facebook feed and I don’t
   have framework\WDILibrary.php (I have WDW_FFWD_Library.php) nor an option “wdi_instagram_options”(
   all my options start “ffwd”).
 * However, it’s not just the Facebook authentication token which is the issue, 
   but also the deprecation of the description field. This would appear to be defined
   in line 737 of WDFacebookFeed.php, and $description in line 884 needs to be extracted
   from the attachments array. Removing “description” from line 737 means the error
   is not reported, but of course without the Facebook token, data cannot be retrieved.
   I’m not familiar enough with the API or your code to work out how to extract 
   the description from the attachments array, which I can see is included in the
   request.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[10Web Social Post Feed] (#12) description field is deprecated for versions v3.3 and higher](https://wordpress.org/support/topic/12-description-field-is-deprecated-for-versions-v3-3-and-higher-4/)
 *  [acleach](https://wordpress.org/support/users/acleach/)
 * (@acleach)
 * [5 years, 1 month ago](https://wordpress.org/support/topic/12-description-field-is-deprecated-for-versions-v3-3-and-higher-4/#post-14438776)
 * [@virtualtopia](https://wordpress.org/support/users/virtualtopia/) The plugin
   page [https://wordpress.org/plugins/wd-facebook-feed/#description](https://wordpress.org/plugins/wd-facebook-feed/#description)
   currently shows v1.1.34 was released three weeks ago. I would expect a new version
   to change that.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[10Web Social Post Feed] (#12) description field is deprecated for versions v3.3 and higher.](https://wordpress.org/support/topic/12-description-field-is-deprecated-for-versions-v3-3-and-higher-2/)
 *  Thread Starter [acleach](https://wordpress.org/support/users/acleach/)
 * (@acleach)
 * [5 years, 1 month ago](https://wordpress.org/support/topic/12-description-field-is-deprecated-for-versions-v3-3-and-higher-2/#post-14415420)
 * Link to affected site — the developer’s own: [https://demo.10web.io/facebook-feed/](https://demo.10web.io/facebook-feed/)
   View the “Tablet” version.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[10Web Social Post Feed] (#12) description field is deprecated for versions v3.3 and higher.](https://wordpress.org/support/topic/12-description-field-is-deprecated-for-versions-v3-3-and-higher/)
 *  [acleach](https://wordpress.org/support/users/acleach/)
 * (@acleach)
 * [5 years, 1 month ago](https://wordpress.org/support/topic/12-description-field-is-deprecated-for-versions-v3-3-and-higher/#post-14414874)
 * It appears that the plugin is attempting to get the “description” field using
   v3.3 of the API. That field was deprecated two years ago, although the [documentation](https://developers.facebook.com/docs/graph-api/changelog/version3.3/#pages)
   implies it should still be available until August. A new version of the plugin
   would have been required then. It seems that Facebook have _either_ brought the
   expiry forward _or_ started to warn explicitly of its impending demise, and the
   message isn’t handled well. However, I gave up on trying to understand the Graph
   API ages ago, and now rely on plugin developers!
 * That doesn’t obviously explain why access tokens are also expiring immediately,
   though.
 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[ICS Calendar] Simple, reliable, solid](https://wordpress.org/support/topic/simple-reliable-solid/)
 *  Thread Starter [acleach](https://wordpress.org/support/users/acleach/)
 * (@acleach)
 * [5 years, 6 months ago](https://wordpress.org/support/topic/simple-reliable-solid/#post-13755713)
 * I’m very happy to add that prompt support has identified an issue with the theme(
   s) I’m using, so there’s no cause to dock a star at all. In fact I’d add one 
   if I could for the support which is offered!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[ICS Calendar] Grid not changing to list on mobile](https://wordpress.org/support/topic/grid-not-changing-to-list-on-mobile/)
 *  Thread Starter [acleach](https://wordpress.org/support/users/acleach/)
 * (@acleach)
 * [5 years, 6 months ago](https://wordpress.org/support/topic/grid-not-changing-to-list-on-mobile/#post-13753007)
 * Many thanks for investigating!
 * The difference in behaviour between phone browsers (which don’t cause an unresponsive
   theme to respond) and desktop browsers (where it does) is a little surprising,
   but you’ve given me a steer as to what to look at. I’ll certainly consider adjusting
   the theme, but that will be a long-term project, I think.
 * The workaround of using a 35-day list in the mobile theme will do for the moment.

Viewing 15 replies - 1 through 15 (of 23 total)

1 [2](https://wordpress.org/support/users/acleach/replies/page/2/?output_format=md)
[→](https://wordpress.org/support/users/acleach/replies/page/2/?output_format=md)