Jon Erickson

20 hours ago, abetts said:

Thanks, I think I will move away from SendGrid and look into an alternative. Sending around 13-14k emails a month, it AWS SES easy enough to set up?

As @Randy Calvert mentioned, AWS SES is one of the lightest and cheapest transactional email services available. I would highly suggest it with the volume of email you are sending. They also have one of the highest reputations which only helps your email deliverability. Our instructions are very detailed and should be easy to set up. If you have any questions, just reach out and we’ll get it solved for you. It’s a set it, and forget it type of solution. 

5 hours ago, AlexWebsites said:

So I had this working on php 8.0 without issue. I just went to update another app and it started to hang. My site went down and would not come back up. I thought it was due to the newsletters app, so I started to troubleshoot. php-fpm: pool processes on the server went through the roof. Traced to this app. I renamed the app folder and the site came back.

@Jon Erickson I'll try to PM you the processes so you can take a look. I've disabled the app, but there is a clear issue when its enabled.

From what I can see from the logs, it is trying to look for files/directories in the vendor folder and it is receiving a not found error. This vendor folder contains all the crucial dependencies needed to run the application. I have double-checked the bundle to make sure the files are present and they are. Can you check your server and see if the files that are named in the log file you provided are indeed present?

Example:

/home/******/public_html/applications/awsses/sources/vendor/aws/aws-sdk-php/

@beats23 are you using PHP-FPM as well?

19 hours ago, beats23 said:

I updated to the latest AWS SES and I have the same issue. When the AWS SES is activated the site won't load.

I now see that it only affects the admin account as members can login and access the site fine, however when Admin try to login to both frontend and backend the site will not load and it gives these 2 different errors in the photo below on different occasions.

When I rename the awsses folder to awsses9 the site loads fine, when I revert back to the original folder name awsses, the site works fine and I can login, however If I change a plugin settings or change any settings in the ACP and click save, the site will freeze and will not load unless I rename the awsses folder to awsses9

Also I disabled all third party plugins and apps and its the same issue 

See error 

 

 

 

 

Can you try with a clean vanilla install not behind cloudflare? What server infrastructure are you using? 

2 minutes ago, beats23 said:

Any info on this issue?

Please read the previous posts. It’s been addressed and waiting for approval. 

An update has been submitted that addresses the backwards compatibility issue. Please update as soon as possible when it releases.

Just now, Daniel F said:

Marketplace submissions should always support the same minimum required PHP & MySQL version as the last IPS release! 

We know. Just looked at the composer.lock and one small package requires PHP 8.1. Will add a PHP 7.4 composer package requirement and update the dependencies to make sure it doesn’t happen again. 

Correct. If you are not running PHP 8.1, do not upgrade to the newest version. Stay on your current version. There is a backwards compatibility issue with the AWS SDK. We’ll see if we can work around it. If not, we will add a system requirement to the app for PHP version. 

Yes, it has always been designed to run on CIC. However, I can’t test against CIC as I do not have a CIC service to use to test. We only use an on premise license to test against. 

A new version has been submitted with support for 4.7.2 and PHP 8.1. The AWS SDK was also updated which added support for PHP 8. Previously did not support PHP 8.

Yeah definitely no support for PHP 8.2 as Invision does not even support that. 

Thanks Randy, glad to hear. I imagine there won’t be many if any issues. 

We have no tested it against 4.7.2. We hope to have it all complete this weekend. 

Thank you for letting us know. When 4.7.2 releases we will be sure to make sure to test against it. Until then we don’t base changes off betas as they are subject to change and inherently full of errors anyways. 

Can you check your PHP logs? You may also enable display_errors in your PHP settings. If you are getting just a white screen, my suspicion is an error is being thrown. 

Any errors being thrown? Are you receiving emails, just not being logged? Did it work for you on 4.7.0? We did test it with 4.7 and everything was functioning correctly. 

Update has been submitted and approved.

Update submitted and waiting for approval.

53 minutes ago, Stuart Silvester said:

If you are a Cloud customer and use this application

Please do not upgrade your community to 4.7 unless you disable this application first. Your community will be unusable after upgrading. The author is aware of the issue and will hopefully have an update available soon.

I am not aware of this issue. Can you elaborate or send me a PM? Thanks. 

@Stuart Silvester just saw your email. Thanks. 

1 hour ago, beats23 said:

Hi, in ACP when using ACP dark mode the error logs are not shown due to inline css codes. Could you fix this issue?

Thanks for bringing this up. Will get this addressed. 

Thanks so much for the review! I’m glad it’s providing so much help to your community!

3 hours ago, MediaDIGI.com said:

I have one AWS SES license and Im thinking to purchase another one for our second community.

But first I would like to know how the bounce management is done? If one address bounces then the member will no longer receive anymore messages?

Every time SES recognizes a bounce, it will send a notification to your community utilizing the API. You can then choose what is done when one is encountered. There is a list of different options include setting their status so they no longer receive emails. 

34 minutes ago, darkdreamingdan said:

Hi there!

It would be very helpful if you added a new bounce/complaint action: set recipient's allow_admin_mails to 0 a/k/a unsubscribe user from admin emails.

We send bulk mail sometimes and we need to currently manually unsubscribe these people from admin mails.

Great suggestion.

As for the error, you need to have the IMAP PHP extension enabled.

https://phpadvices.com/install-or-enable-imap-extension-in-php/

You can also try out the following app to get rid of SMTP and use the AWS SES API for better performance and less impact on your server.

26 minutes ago, jesuralem said:

Funny stuff in my bounce log today :

The email is not a actual email.

Also i don't think you can set "guest" to validating :).

Most likely a spam bot without an account, posting a message, and then being sent the “continue registering…” email to the fake email address. Happens a lot!

Also the application will properly handle the bounce if the email is not an actual member account!