miketemby

Thanks, that’s awesome.

It’s not just a few clicks if you need to refresh your whole dev environment first… I’m certainly not going to test a beta release on a live website.

@qtwrk I will need to spend some time updating my dev environment in order to test that. The issue I am experiencing is in production.

Is this test just a shot in the dark, or have you identified the cause of the issue?

mediaelement-and-player.min.js

I don’t see any error in the log file.

log

the combined js file is 2c272.js

@qtwrk That is not a helpful response. Clearly, I am aware that the file can be excluded as my question quite clearly states

how can I fix it without having to switch off combine, or remove this file from being combined?

The question is: Why is a file being truncated, and how can this be fixed without having to exclude the file, or turn off combine?

The file should be getting truncated!

Hello?

***crickets***

• This reply was modified 5 years, 1 month ago by miketemby.

Hi There,

I spoke to EE team about it and they provided me the following code to add to my child theme. This fixes the issue so both footer elements are added.

Including this here in case anyone else needs it. Cheers,

<?php //Please do not include the opening PHP tag if you already have one.
//Remove the EE espresso_admin_footer callback and add another which includes current content.
add_action('admin_init', 'tw_filter_admin_footer_text');
function tw_filter_admin_footer_text() {
    $admin = EE_Registry::instance()->load_core('EE_Admin');
    remove_filter('admin_footer_text', array($admin, 'espresso_admin_footer'));
    add_filter('admin_footer_text', 'tw_filter_powered_by_event_espresso');
}
function tw_filter_powered_by_event_espresso($content = '')
{
    $powered_by_event_espresso = \EEH_Template::powered_by_event_espresso('aln-cntr', '', array('utm_content' => 'admin_footer'));
    return $content ? $powered_by_event_espresso . '<br/>' . $content : $powered_by_event_espresso;
}

I think it is because Event Espresso also adds something to the WP Admin footer…

Maybe add the option to display the memory info elsewhere?

@emanuelas1987 This plug-in does not use Graph API so as mentioned above, it will not work at all for hashtag feeds.
The authentication method suggested above would require you to first build or find a plugin that uses Graph API.

@joshuabarney Instagram have stopped access to the API, so there is no workaround unless someone works out a viable method of scraping the data without using an API…

@bcavs To use the new(ish) Graph API you need to authenticate with a user account that has a role on a FB page that is associated with an Instagram business account… so it appears that there is no easy way to get hashtag feeds anymore for personal accounts.

Further information: https://developers.facebook.com/docs/instagram-api/hashtag-search

You could however create a business account just for authentication purposes and return the hashtag search for whatever you want…

Yeah it will affect everyone, not just this plugin.

• This reply was modified 6 years, 3 months ago by miketemby.
• This reply was modified 6 years, 3 months ago by miketemby.
• This reply was modified 6 years, 3 months ago by miketemby.

Suzie, the issue is not related to users settings and cant be fixed by regenerating access tokens. The issue relates to changes Instagram (FB) made yesterday to their API.

As can be seen here:
****
https://www.instagram.com/developer/changelog/

Dec 11, 2018
Deprecation of Hashtags and Locations endpoints.
****

I contacted 10Web about this earlier today to find out if a fix would be applied via the use of the alternative Graph API but had the following response, so if this response is anything to go by, it appears the plugin will no longer be a viable solution for hashtag feeds…

Dear Customer,

Hi,

I would like to inform you that access to Instagram is closed now and it is not possible for our development team to eliminate the existing issue.

Should you have any questions, please do not hesitate to contact!

Have a nice day ahead!
Best regards,
Shushan Gevorgyan
10Web Customer Care

• This reply was modified 6 years, 3 months ago by miketemby.

…yeah not sure how simple the update will be. I’d say it’s reasonably significant but I don’t really know.
Given there is a premium version of the plugin which would be experiencing the same issue, the developer will no doubt be addressing it asap (hopefully..).

Same here.

looks like the plugin will need to updated to use the Instagram Graph API.

https://www.instagram.com/developer/changelog/

Dec 11, 2018
Deprecation of Hashtags and Locations endpoints.