sankari

Hello!

Thank you very much for your quick reply – and you are welcome.

About the disabling: In the case of HivePress, the editing of listings by users happen in the frontend, not the backend. And the problem might be that HivePress doesn’t provide a query parameter for the edit page that Email Encoder could use.

Perhaps a new option in Email Encoder’s settings where specific URL strings can be excluded would help for such cases, for HivePress: /account/listings/? Just thinking loud.

Thank you for investigating. I’m glad that this plugin is maintained again.

@anupamkhatua

Thanks very much for your answer and for noting it as a feature request.

Have a good week!

Hi @anupamkhatua

Hope you are doing well.

Could you please inform me about the status of these enhancements:

The Express plugin does not log any email addresses when sending emails. However, if an error message from the mailing provider contains an email address, that information may be logged. To ensure compliance with GDPR, we plan to replace email addresses with contact IDs in the logs in the upcoming release.

The personal data of contacts who were part of a campaign is retained indefinitely. To enhance data privacy, we may introduce a future update that allows for the anonymization of data belonging to deleted users.

Thank you and have a good weekend!

Hi @anupamkhatua ,

I’m doing fine, thank you. Hope you too.

And I’m sorry that you didn’t read from me before. There was no notification about your message of last week.

Thank you for trying to replicate the issue. Actually, I had just copied what @scribelle found on that plugin testing website. I didn’t see those PHP warnings and notices in our installation before and, after following your instructions, I don’t see them now, neither with PHP 8.1 nor with 8.2.

Perhaps those PHP warnings and notices are false positives resulting from the headless browser that is used for testing:

Does a “failure” mean that the plugin is broken and unusable?

It suggests that there’s something wrong, but it doesn’t always mean that the plugin is broken. Here’s why:

• (…)
• These tests use a headless browser. There are a few plugins that trigger errors in this browser but that work perfectly fine in a “real” browser. These false positives are rare.

Source: https://plugintests.com/#faq

@scribelle : Could you advise if you get those PHP warnings and errors in your WordPress installation after upgrading, see Anupam’s instructions above? You can still revert Icegram Express to the previous version using the WP Rollback plugin.

Thanks.

Hi @shubhanshukandani ,

The new HivePress release is not available yet but since the issue is on there side it makes sense to me to close this thread.

Thank you and have a good weekend!

@anupamkhatua

FYI – HivePress informed that they will include this in their next release. I will close this topic when resolved.

@anupamkhatua

Thank you for resolving the issue!

The warning doesn’t appear in version 5.7.48, therefore I’m closing this topic.

Thanks!