Hello there @cihomewood,
Thank you for reaching out to us and detailing the issue you’ve been experiencing with the Mailpoet new post notifications. We understand how important it is for your communications to run smoothly, and we apologize for the inconvenience this has caused you.
From the description you provided, it seems like the issue might be related to the tracking parameter appended to your links. This is not a common issue, but it is something we can definitely look into to ensure it gets resolved.
Given that the issue appears to resolve itself when the tracking parameter is removed (as observed when switching in and out of desktop mode and potentially affecting the URL), this does give us a valuable clue. It’s particularly interesting that the problem is evident across different devices but not universally on all platforms, such as your Windows laptop and iPad.
A HTTP ERROR 500 usually indicates a server-side error, which could mean that the issue is related to how the tracking requests are being handled by your server or potentially conflicting with another plugin or theme after an update.
Here are a few steps we recommend:
- Plugin Conflict Check: Temporarily disable other plugins and see if the issue persists. This helps us rule out conflicts with other plugins. Here’s a guide to help: https://kb.mailpoet.com/article/204-how-to-test-for-plugins-conflict
- Server Logs: Check your website’s error logs through your hosting provider’s control panel. Look for any error entries that correspond to the times when the errors occurred, as these logs may provide more insight into what’s causing the issue.
- Mailpoet Update: Ensure that Mailpoet and all other plugins/themes are updated to their latest versions. Although you mentioned not changing any settings, updates could sometimes introduce changes that might affect functionality.
- Contact Hosting Support: Given the nature of the error, it might be helpful to check in with your web hosting provider’s support team. They can review server resources and configurations that might be contributing to the problem.
We realize you’ve already attempted some troubleshooting steps like refreshing caches and rebuilding permalinks, but these additional checks can be crucial in pinpointing the exact cause.
Let’s start with these steps and see if any help in resolving the issue. Please keep us updated on your progress or if you uncover more specific errors in your logs related to this issue.
If the issue persists, we may need to look into more detailed logs on your website or explore other technical avenues.
Looking forward to hearing back from you.