Subscriber Email Issue – Two links present to read more of the article

Since you’ve also reached out to us via email about this, let’s continue the conversation there. One of my colleagues will reply to you soon if they haven’t already.

@jeherve Jeremy, I wanted to leave this open to see if others have this issue? And also see if you have seen this issue with the latest release of Jetpack? Richard was questioning code snippets that you helped me with but as I said I wanted your opinion on this as well as any area of the new release that could affect this or something I haven’t considered? I haven’t made any modifications nor do I know of any at to modify the email layout coming to me since that’s a Jetpack thing? Please for now could you leave this open and offer any of your own suggestions?

I wanted to leave this open to see if others have this issue?

No worries there, every thread in the www.remarpro.com support forums remains open for a year after its creation.

I can’t say that I’ve heard about this issue since the release, or even before the release, but if someone experiences similar issues they’re welcome to comment here, or contact us via email and forward us an example so we can take a closer look.

The only thing that would come to mind is maybe something specific with your email client, but I’m sure Richard will help you figure this out!

@jeherve I thought the same with my email client too except I checked with another subscriber and their email client and it was the same issue with them. And it only started after Jetpack 4.9’s release with them too. Basically the […] was replaced with a link saying ‘continue reading…<blog title>’, if the blog is longer then the standard email length that comes through. It’s very frustrating because it looks very cluttered now on that email layout and Jetpack, as far as I know, does not give me any options to change that layout.

@jeherve This issue hasn’t been resolved and I have not received any contact from any Jetpack support team member. I have sent three emails now and have gotten no response. And I also asked to leave this support topic open for anyone else who may have experienced the same issue. Regardless, I would like for you to help me know what to do here since no one is responding from my Jetpack support emails. I’ve received only one email and that was on May 5th, that being a week ago, where Richard asked me a question. I have since responded three times and gotten no response back, which is quite unlike my previous experience with the email support. So can you please take this over and help me to figure out what’s going on? As I’ve mentioned to you in each of my postings here and in my emails, there is nothing I’ve changed on my blog in months and months. I have removed all plugins during my testing except AKismet and Jetpack and of course my WordPress 2016 theme to ensure it’s nothing on my end. I have checked multiple subscriber emails from difference email servers and each experience the same result since Jetpack 4.9 was released. There are two links now in the subscriber emails and I really hope that you guys can figure out why that’s happening now in 4.9 and how to turn it back off to be the “[…]” instead. Please respond Jeremey. I need some help from someone in Jetpack and so far you have really only been the one to respond…

I believe we’ve talked about this together before; the way our support system is designed, your ticket will be pushed down to the bottom of the queue every time you send a new email. If you keep sending multiple emails asking for an update, you’re actually pushing your ticket to the bottom of the queue every single time.

I would strongly recommend that you avoid sending multiple emails in the future, and instead await for a reply from one of my colleagues.

I’ve just replied to your ticket with more info!

@jeherve I remember you saying that but then if one has updates to the error found and wants to help provide that information over to Jetpack to help in their testing processes, that ends up penalizing the user? How can they provide new information then without being pushed down? And I just sent you this response in email:

Jeremy, thank you for taking this over.

1. Most important question I have, Is it safe to say that this error will be resolved by the next release of Jetpack if I choose to not use this workaround?

2. Also, I’m not sure I quite understand this work around actually, even after reading the stuff on your site. As I already had the summary selected on that field you indicated to change from long ago. And my home page shows the past three blogs in entirety. That field only changes the feed when a user searches on my site for a search term. So is really the only change to do this workaround for me to add the more tag to each blog post as somehow that affects my subscription emails? Because in doing so, I am assuming that it then sends out the subscription email with the length of my blog until that more tag is found? Yet it also now would affect my home page though and only show the blog up until the more tag too. I am having a hard time understanding how adding the more tag can affect my subscription email because with this error existing now on Jetpacks side of things, even if I put the more tag in it will still show two links to continue reading, one that will be at the more tag and one that is the standard, ‘read more of this post’ which is the exact error that is now showing up?

3. And Lastly, just curious, what changed in Jetpack 4.9 that would have conflicted with the WordPress themes to cause this issue?

Thank you in advance for taking the time to answer these three questions.

Andrew

On May 12, 2017, at 9:18 AM, Jeremy – Jetpack <[email protected]> wrote:

Hi Andrew,

Richard, the only code snippet I have is the one Jeremy had me add for a default picture eons ago. It’s attached to this email back to you. I have done nothing in the last few days to change anything other than Jetpacks update?

Thanks for the extra details. I was able to reproduce the issue on my end, and it seems to be a conflict between Jetpack and certain themes that hardcode a read more link into their excerpts. We’ll get this fixed as soon as possible. You can follow our progress here:
https://github.com/Automattic/jetpack/issues/7178

In the meantime, you can work around the problem by going to Settings > Reading in your dashboard, and switching your feed settings from Summary to Full Text.
You can then still split your posts into 2 thanks to the More tag:
<!–more–>

Everything that is above the More tag will appear on your home page and in the subscription emails, followed by a link inviting users to click to continue reading; everything that is below that tag will only appear on the post’s page.

You can read more about it here:
https://en.support.wordpress.com/splitting-content/more-tag/

I hope this helps, and thanks for the report!

Jeremy
Automattic | Jetpack.com

And please is there any way you can you keep this open till Jetpack fixes the problem in the release they do as I track my stuff by waiting till I have the fix working in my he main release to WordPress and I see it working.

I’ll copy my last email reply here, so others can follow.

1. Most important question I have, Is it safe to say that this error will be resolved by the next release of Jetpack if I choose to not use this workaround?

We’ll try, but we’ll need to find what caused the issue before we can fix it. I can only recommend that you follow the related GitHub issue if you want to know when we start making progress on this. We’ll also update you via email when this gets fixed.

So is really the only change to do this workaround for me to add the more tag to each blog post as somehow that affects my subscription emails?

Yes.

Because in doing so, I am assuming that it then sends out the subscription email with the length of my blog until that more tag is found?

That’s correct.

Yet it also now would affect my home page though and only show the blog up until the more tag too.

That’s correct as well. The more tag will change the way your posts are displayed in your RSS feed, on your home page and archive pages, and in subscription emails.

even if I put the more tag in it will still show two links to continue reading, one that will be at the more tag and one that is the standard, ‘read more of this post’ which is the exact error that is now showing up?

No, if you use the More tag, only one “Read more” link will appear in subscription emails. The bug will be hidden.

3. And Lastly, just curious, what changed in Jetpack 4.9 that would have conflicted with the WordPress themes to cause this issue?

We don’t know that yet, but as soon as we do we’ll fix the issue.

if one has updates to the error found and wants to help provide that information over to Jetpack to help in their testing processes, that ends up penalizing the user? How can they provide new information then without being pushed down

Yes, it does penalize you. That’s an unfortunate side effect of how our current ticketing system, and something we’d like to get fixed in the future.

please is there any way you can you keep this open

Are you referring to this forum thread? It will remain open for a year. Threads only get closed by moderators, or get automatically closed a year after they’ve been opened.

@jeherve Thank you do much for answering so quickly and throughly! ??

I will do my best to wait patiently on this Jetpack bug getting fixed and see about trying out that workaround for the time being.

Regardless, I wanted to keep the status to this as ‘Not resolved’ since it isn’t fixed. What’s resolved is only that we know it’s a Jetpack bug. But it isn’t resolved in the current release of course so I’d rather leave this as ‘not resolved’ like I did the scheduled blog issue out here until finally it was ok? Especially if I have any updates to add…

Regardless, I wanted to keep the status to this as ‘Not resolved’ since it isn’t fixed. What’s resolved is only that we know it’s a Jetpack bug. But it isn’t resolved in the current release of course so I’d rather leave this as ‘not resolved’ like I did the scheduled blog issue out here until finally it was ok? Especially if I have any updates to add…

Oh, I see. That’s fine by me. ??

@jeherve I just wanted to let you know I tried the workaround by adding the <!–more–> tag in the HTML editor. Unfortunately, it didn’t do anything. Not in my email to subscribers nor in the actual home page feed either. It just simply ignored it. And I did check to make sure it was not a formatting issue where I was using other editing around it that could nullify it. It just flat out didn’t work. I just wanted to let you know I tried and sadly it didn’t work for me. Not sure if that’s also related to the other bug or not with the way the WordPress theme is doing things and how Jetpack is with it? Regardless, I just felt I needed to let you know I tried to get it to work to no avail. I did notice in the directions that you are supposed to click over to the “HTML” tab to add that text and in my editor on WordPress, I only have “Visual” and “Text”, no “HTML”. If you have any ideas around this why it didn’t work let me know. Otherwise, I’ll just have to wait with the bug until you guys fix the error we discovered.

• This reply was modified 7 years, 10 months ago by Andrew Arthur Dawson.

Could you give me an example of a post where you inserted the More tag, so I can take a closer look?

Thanks!

So I think I figured out the problem. I was cutting and pasting from your email the <!–more–> tag and it was turning it into straight up text. I was able on one of my tests to get it to work, at least on the main summary of my blog page. I won’t be posting a full article until Tuesday night going into Wednesday, so I will try it then again and see if it shows up in the email correctly and let you know. Thanks. ?? Hopefully though your team is working on fixing this bug though. ??

@jeherve On the plus side, I saw how the “More” feature works for the actual blog posting on my site. On the negative side, it doesn’t affect the email at all Jeremy. Trust me I tried. I placed the “More” button about a paragraph and a half into my blog and while I saw the “More” show up on the actual site, the email remained unchanged. Not sure where you thought that would affect the email, but I’m guessing that maybe the same error that’s causing this problem that your reported already as a bug and recreated prevents this from actually being used as a workaround? So, if you can pass along to Jetpack that there is no workaround for this bug and at the moment, the best I can do is just deal with two links in my emails, hopefully that will motivate them to fix the bug, given it is a known Jetpack bug now. The Github has no activity on it other than me leaving a comment there. No one has been assigned it at Jetpack either. ??