Jon Erickson

Love to see the attribute use! Can’t tell you how many times I’ve screwed up the docblock formatting for my API docs and not realized it. Game changer! Hopefully this applies to the apiOutput method as well or something similar has been created!

Everyone - The app will continue development at the posted link. If you are going to upgrade to IC 5, the AWS SES app will be available at the attached link. You can currently switch your subscription to the newest version: v1.1.0. Thanks everyone. https://store.deschutesdesigngroup.com/checkout/buy/0182a1f0-48ea-4438-9b40-293441be9f85

Did you hit your SES sending limit and it reset? What’s your reputation? Did you get throttled? May be worth it to send them a ticket and see if they noticed anything on their end.

We are working on a way to continue its support. It will be available via an online store. We’ll post the instructions/details to this thread when it is ready.

Are there any CIC users who can confirm it is working/not working on 4.7.13?

Hmm I wonder if it has to due with using CIC. I’m sure they have CIC specific settings to use whoever they use to send emails. Nothing in logs? Are you able to enable to cURL/HTTP logs? I know you can on premise. This would allow us to see the app calling the API.

You can login to AWS go to the IAM section and see when they were last used - if they’re being used at all.

I just fired up my development environment on 4.7.13 using PHP 8.1.20 and have no issues sending email. I checked the release logs for 4.7.13 and it doesnt appear theyve changed anything to the way they send email. Can you verify you have no errors? What PHP version are you running? Try disabling all other apps/plugins and try again.

I see that! We’ll give me patience when v5 comes out and we’ll see what we can do to get it rocking there too.

We will absolutely maintain support for version 4.

Hi Scotty, the app has not been tested against the latest release. Can you rollback to the previous? At this time, we are unclear what the future is. With the unknowing of how Invision 5 will look under the hood, we can’t possibly tell if the app will need to be ported to the new version, or even needed at all. We’ll have to wait till it’s out to make those determinations.

Yes, I looked at that method. For some reason it didn’t do what I needed, but I will revisit…

Trying to figure out a way to effectively retrieve the content item from a given friendly URL. Anyone have any suggestions?

I’ve tried both and messed around with several different flows. This is the fastest way for me. It aligns with other industry standards for project development as well and I can spin up a dev environment in a few key strokes. Not to mention I’ll configure it to the dev container spec as well so it can be used in any dev environment including remote.

Correct, you can create a repo directly from it since it’s a template. Add your Invision core files to the “invision” directory, replace all instances of “yourappkey” and you are ready to rock.

I've posted by Invision app template that I use to build applications to Github and turned it into a template for anyone interested. Feel free to use and pass along. Works well for many workflows. https://github.com/DeschutesDesignGroupLLC/invision-app-template

You can always enable the HTTP logs to see outgoing cURL requests and view everything through the standard system logs.

Gotcha. Are you saying that if I said it was required, they would enable it for you? It technically is not required for the app to function - it is used to just decode the email headers and help display that information in your logs.

If you are on a typical shared hosting environment, you can usually just enable the extension in your web hosting control panel such as cPanel or Plesk. If you are on a VPS or dedicated server, you may have access to WHM. If not, you’ll need to get ahold of a SysAdmin who can enable it for you.

I haven’t seen the screen before. Did you go to the IAM section of AWS and create a new user? If you did, this may be a new screen and I would just use third-party service.

This is what @Dll mentioned above. Still trying to nail down why this happens.

Interesting. Well I am glad you got it working!

I had something similar happen with one of my other applications and it boiled down to composer issues - which as you can see throughout this forum, I think they are still trying to iron out how they manage their dependencies while allowing 3rd party devs to include their dependencies.

Have you removed the subscription and recreated a new one with the correct URL?