• This morning, the template for our email notification was broken. The ‘Continue reading’ button is missing, and the main body text appears to be encrypted or garbled.

    Interestingly, another site of ours sent out a notification this morning without any issues, so it seems the problem is specific to this post.

    Has anyone encountered this issue before? Any advice on how to prevent it from happening again would be greatly appreciated.

    Here is a screenshot of the email: https://ibb.co/RjbnCrr.

    • This topic was modified 1 week, 4 days ago by nahbweb. Reason: deleted miscellaneous text

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Hi there, @nahbweb,

    I’m sorry to hear about the trouble, but thanks for reaching out.

    It’s a hard one to debug since, as you said, seems to be an issue affecting only that specific site. Can you tell us if the other site whose post notifications work well has the ‘Continue reading’?setting too?

    We had a small glitch affecting the newsletter, but it didn’t show errors like the one you shared.

    To avoid leaving any stones unturned should your error is connected to the aforementioned glitch, could you please do the following?

    • go to Jetpack > Settings > Newsletter
    • switch to Excerpt from Email Configuration?For each new post email, include

    Check if the issue persists when you publish another post.

    Hope it helps! Let me know what you find out, and we’ll take it from there if necessary. Thanks!

    Thread Starter nahbweb

    (@nahbweb)

    @erania-pinnera,

    Thank you for the advice. We published another post today, and the glitch happened again. We have yet to change our settings to excerpt, but we will do so today.

    We don’t want to risk sending another email with a glitch. Can we test the notification before it goes out to our subscribers? Thanks!

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.