derpunker

Wow, that's great. Many thanks for the support, that really helps a lot. 👍

Thanks for have a look and fixing it so quick. Let's hope that the next release will come very soon. 🙂

Just to make it more clear: Email-Settings: Sendgrid configuration: Small IPS extension: (sorry, only in German available) PHP code behind: => classToUse delivers the wrong result for TYPE_BULK Bringing the old code from IPS 4.7.19 for this function back, let the system behave as execpted and before the latest update. Hopefully the bug in the latest IPS version is clearly described now.

Again: IPS has sent the emails via SMTP server (general email configuration) But for bulk emails the SendGrid extension is configured but ignored from IPS 4.7.20 software If needed, I can share some screenshots later.

No, errors are not reported. The emails were send, but with the wrong configuration. The problem is that the IPS Community Suite uses the SMTP email server (our default for sending emails) for the bulk mails instead of the configured SendGrid extension (for bulk mails only). Our main problem is that some mail services (GMX, Web.de, ...) has blocked/blacklisted our server after sending bulk emails in the past. That's the reason why we are using SendGrid to avoid this blacklisting.

Dear IPS Support, the SendGrid integration was announced as "deprecated" with the latest IPS 4.7.20. https://invisioncommunity.com/release-notes/4720-r132/ There was no word of complete removal, but it is! Was this intended or removed by accident? Since the last update to IPS 4.7.20, sending via SendGrid no longer works. A look at the source code quickly makes the cause clear. File: ...\system\Email\Email.php IPS 4.7.19 (and before) IPS 4.7.20 It's not hard to see that the code is doing something completely different. I request that you bring back the old logic for IPS 4.7.x. (or declare SendGrid integration as totally removed, but this wouldn't be nice for the 4.7.x line). Many thanks in advance.

Not really, the issue was never seen before the update. (update was installed on Nov. 16) Since the update, the errors are popping up and the root cause is always the same.

The dev environment shows this in both cases. The dev environment shows more details and this system has no language pack installed. The theme is unmodified too.

Looks like there are more texts missing. => rejecting a report => complete a report

I have observed the same issue. There is one kind of parameter which causes the issue for me. I have no idea if this link is coming from the IPS installation itself or somewhere cached in google. Maybe the link was valid in a older version of IPS. Hint: Removing the ' in the URL fixes the issue. After removal the query parameter is correctly translated to page/2/

done 🙂

@Daniel F You mean the code or the UI?

Dear IPS support, affected file: system/Content/Controller.php The function "report()" doesn't check if there is more than one type available. It shows always the selection box with one entry. I have observed this for CMS\records. The function "_report( $commentClass, $comment, $item )" does this check and the dropdown is hidden if there are no custom types defined. Please have a look and add this check in th "report()" function too. Thanks.

Thanks, I had some hope. 😉 Do you have an estimate in which release the fix will be included?

@Marc I guess the fix is not included in IPS 4.7.18, right?