-
Posts
283 -
Joined
-
Last visited
-
Days Won
7
nbcommunication last won the day on September 27
nbcommunication had the most liked content!
Profile Information
-
Gender
Not Telling
-
Location
Lerwick, Shetland
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
nbcommunication's Achievements
-
Hi @Stefanowitsch, Have you tried <?php nl2br($item->description); I expect the IG caption uses newlines, this would convert them to <br> tags. The module passes the caption through $sanitizer->entities1() which shouldn't remove the newlines as far as I'm aware. Cheers, Chris
-
Hi, Unfortunately I discovered this morning that the token that is returned by the API expires after 60 days. This is the same as the previous API, but the documentation about generating tokens for this API didn't mention expiry or I wasn't aware of it while developing. Thankfully I've been able to use some of the code from the previous module for token renewal, and have released v1.1.0 of InstagramMediaDisplay which you need to upgrade to if you don't want an existing token to expire. It'll set the existing token to 'renews in 1 day' which triggers the token to be renewed on the next load. After this it should display in the module config as renews in 2 months. Once the token has 7 days left, it'll auto-renew. Cheers, Chris
-
Hi, I've not tried this implementation before with any captcha module, so not sure why it would no longer work, but I would point out that we're still using @flydev's MarkupGoogleReCaptcha on many sites (front-end, v2) without issue, and the recent MarkupCloudflareTurnstile is effectively the same implementation, but with the CF captcha, so if it works for one, it should work for the other. Cheers, Chris
-
Hi @Stefanowitsch, I've only rolled this out to clients where we already have access to the IG account. My expectation is that for the others we'll be doing it at a predetermined time with the client (e.g. a meeting) where they can provide us with temporary access (e.g. changing the password, then changing it back once we're done) and provide any auth codes if necessary. I agree, the process should be a lot simpler, and that's partly my approach to implementation and Meta's offering - I expect a simpler authentication process for the client would mean App Review for the developer and the headache involved with that. Cheers, Chris
-
nbcommunication started following InstagramMediaDisplay and MarkupCloudflareTurnstile
-
This module allows you to add Cloudflare's Turnstile CAPTCHA to your website, providing a user-friendly alternative to Google's reCAPTCHA. It is based on MarkupGoogleRecaptcha, allowing for easy switching between the two CAPTCHA systems. If MarkupGoogleRecaptcha is installed, some of its settings are used to configure Turnstile. https://github.com/nbcommunication/MarkupCloudflareTurnstile We've used reCAPTCHA for many years now but have found that it isn't as effective as it should be in reducing spam. It is also pretty annoying. We've recently switched a couple of our 'bigger' sites to use Turnstile (using this module) as the sites were on Cloudflare already. It is definitely a much friendlier captcha for users, still to determine whether it is better at preventing spam, but I expect it will be. Cheers, Chris
-
It's done, just waiting on module approval. More info here: and here: https://github.com/nbcommunication/InstagramMediaDisplay Cheers, Chris
-
Meta are disabling the Instagram Basic Display API on December 4th, 2024. After this point, the InstagramBasicDisplayApi module will no longer function. Meta do provide an API that can be used to access Instagram media, Instagram API with Instagram Login. Using this API I've been able to refactor InstagramBasicDisplayApi as a new module called InstagramMediaDisplay: https://github.com/nbcommunication/InstagramMediaDisplay The main caveat with using this module (and API) is that personal and/or private accounts cannot be used. If you try to generate an access token for a personal account, IG will prompt you to upgrade to a business account. As far as I'm aware this is still a free account, and the main limitation is that you cannot use licensed music in the same way you can on a personal account. I have access to various IG accounts, some personal, some business, and I've never noticed a difference. This new module is built to supersede InstagramBasicDisplayApi and its implementation is practically identical. Upgrading should simply be a case of installing, configuring your new Meta app, authorising the same account(s), and updating the call to the previous module to call this one: <?php // $instagram = $modules->get('InstagramBasicDisplayApi'); $instagram = $modules->get('InstagramMediaDisplay'); Cheers, Chris
-
Hello, I've had a look at Instagram API with Instagram Login and initial results are pretty promising. I actually found it easier to set up the app and generate an access token, and the actual API is easier to work with too. It'll take a bit of work to create a new module for this API, but I should have something ready in plenty of time. Will update here once I have something. Cheers, Chris
-
Hi @DV-JF, So the limitation is that it isn't for use by personal accounts? For our use cases, I think every one is a business (and should have a business account), so I'll still explore it, but I can understand that'll be frustrating for those using this module for personal projects. I don't think it takes much to switch to a business account - both the band accounts I have access to on Instagram are business accounts, I think it is just a case of specifying that? Or at least it was when these were set up years ago. Given the maze of Meta requirements it wouldn't surprise me if you need to submit yearly accounts to get a business account now... Cheers, Chris
-
Hi @tomasanjosbarao, Thanks for letting us know. I'm not surprised! I'm going to investigate https://developers.facebook.com/docs/instagram-platform/instagram-api-with-instagram-login to see if this will be usable for the same purpose, and if it is, will try and get a new module together before 4/12/24! Cheers, Chris
-
Hi @DV-JF, I've just checked in on one of our sites using this module and its token has renewed again. I was definitely having issues with the FB/META/IG API stuff last week, so my preferred explanation is that there have been issues on that end that's prevented token generation and renewal. Are you still having an issue? Cheers, Chris
-
Hi, Some good news: we did manage to generate a User Token without app review, after setting a new application up from scratch. It's quite possible this bug is not connected to potential changes in the App Review policy, as initially feared. Similar issues have been reported: https://stackoverflow.com/questions/76473468/instagram-basic-display-api-cant-generate-access-token https://developers.facebook.com/support/bugs/185012584505063/ https://developers.facebook.com/community/threads/636065331832545/ We will keep an eye on this. Thanks, Mark
-
Hi, Initial findings aren't positive unfortunately. In our application, whenever I try to generate a User Token I get an Error message on the Instagram popup. I got a colleague to create an application from scratch in a FB dev account not associated with our business one, and we also got the same error when trying to generate a token. There's a message in the App Review section indicating that reviews are delayed for Instagram apps due to volume, which suggests that they've recently made it necessary to submit for App Review and there are a lot of people scrambling to get this done. We're going to investigate further and see if we can find some more information about this, perhaps getting confirmation through developer support and/or the community help. If this is what is going on, this module will still work for 'Live' (reviewed) applications, but my understanding is that the process is a likely a lot of jumping through hoops, and completely overkill for what the application is trying to achieve. It isn't something we'd be attempting willingly! Cheers, Chris
-
Hi @DV-JF, Unfortunately I suspect this may mean an end to this module being able to function. The impression I'm getting here is that the Basic Display API applications now need to be submitted for review/approval. This module took advantage of FB allowing development applications if they were created 'solely for the purpose of generating access tokens with the User Token Generator'. It really isn't clear however. When I try to generate an access token in the User Token Generator I get an error page on the Instagram pop-up window. I don't know whether this is because there's an issue on their end, because of the permissions thing you've highlighted, or something else. The next token renewal we have on a site using this module is in two weeks, so it'll be then before we come up against this issue. I'm going to ask a colleague to set up an application from scratch and see if he comes up against any issues, or other information that might shed some light on this. Will keep you updated on what we find. Cheers, Chris
-
Hi @Arklogic, Apologies, I'd decided many months ago now that developing this module in a way that would be robust enough for production (and listing on the modules directory) was just too complex. I thought I'd posted here to that effect. I see I did not. The latest code is here: https://github.com/nbcommunication/CloudflareAssets I think I did implement the page clone action, but did not implement anything for image editing in the admin, and have no plans to. While we are using this module on the website I'd developed it for, it is tailored for its use-case. Were I approaching the same development now, I'd be looking at using a CDN which would be significantly less work. Cheers, Chris