Oops! That page can’t be found

Hello @helenel,

Thank you for reaching out to us.

> Today mailpoet behaved strangely when sending newsletter for a new post:
some newsletters had the hyperlink to the post in the title… and if clicked led to the “Oops! That page can’t be found”
some newsletters did not have the hyperlink in the title (only in the image and read more and there worked perfectly…

Did you mean the title on your new post included in the post notification email had a hyperlink that redirect to the error message “Oops! That page can’t be found”

I can confirm that the title of new posts that triggers that post notification emails are not supposed to have an hyperlink so this is indeed strange.

Can you tell if this just recently happened and you’ve been able to send your post notifications successfully in the past?

You also mentioned about repairing your database. Did you get specific prompting to do this? I know you also mentioned you did not take a screenshot but any other information you can help us with will be appreciated as this is the first complaint we’ve gotten about this.

Have a great day.

Hello Ojoma,
Thank you for your answer.

Did you mean the title on your new post included in the post notification email had a hyperlink that redirect to the error message “Oops! That page can’t be found”

Yes exactly.

Actually, you asnwer is bizarre because we had another batch that left on last Thursday and again the title of the post was a hyperlink… but this time it appeared to lead to the post. You can check that here (hopefully) in the read in browser
https://redanalysis.org/?mailpoet_router&endpoint=view_in_browser&action=view&data=WzU1MTA2LCIzMmI5MjhkNjg1NGIiLDAsMCw1NjY0MCwxXQ

The problem just happened and we have been able to send post notifications with paper.li since 2011 if I remember well ??
For the previous non functioning email the link is
https://redanalysis.org/?mailpoet_router&endpoint=track&action=click&data=WyI1NyIsImFlMzVlNSIsIjU1ODkzIiwiOTI1Y2IzNTRkNTUwIixmYWxzZV0
to compare with another email of the batch
https://redanalysis.org/2022/05/24/information-warfare-and-the-war-in-ukraine/?utm_source=mailpoet&utm_medium=email&utm_campaign=the-red-team-analysis-society-newsletter-post-title_4
that worked.

Re database: no we did not, but we noticed that each time there was a problem with mailpoet, which happens unfortunately every two months or so, when there is an upgrade, most often with created a problme with the database that needed repairing. If we did not repair it promptly, then after a couple of hours the website crashed. Usually once the database is repaired we get many messages that read (approximately) like … error.. failed to close line whatever etc. this has been repaired
Sorry next time I’ll pay more attention.

Hopefully you can find out what went wrong, I know I don’t give you many strong elements
Best regards
Helene

Hi there @helenel,

Thanks for getting back to us!

To clarify, you can decide to have post titles as links or not in your Posts block settings:

Link to image: https://d.pr/i/dbZyY9

The two links you shared are different because the first one has Engagement analytics tracking enabled while another is not. This setting is located in MailPoet > Settings > Advanced tab > Engagement analytics tracking.

Is it possible that you had it enabled for the one sending but not for another?

Still, it should work with Engagement analytics tracking on.

Can you please check if your wp_mailpoet_statistics_opens database table is not corrupted? We’ve seen this issue before and it was resolved by repairing the database.

Let us know how it goes!

• This reply was modified 2 years, 9 months ago by Elvira K..

Hello,
Sorry for the belated answer but I did not get your answer through my emails.
I’ll check.
For the mails sent for all new posts, the title as link link is checked.
In the settings, the Engagement analytics tracking is on full.
However, I don’t know if this pays or not we have the CAOS plugin plus all the stuff related to respect of GDPR “activated” (GDPR settings through jetpack notice).

Also one possible problem could be linked to translatepress, as this happened before.
Today (see crash when sending mailoet email a hour ago), I noticed a weird thing: all the links from mailpoet email are to the page in the French translation (which it should not do): https://redanalysis.org/fr/2022/06/02/the-red-team-analysis-weekly-2-june-2022/?utm_source=mailpoet&utm_medium=email&utm_campaign=the-red-team-analysis-society-newsletter-post-title_6

the link should be without the /fr/

Previously, we had excluded /?mailpoet_router*
/fr/?mailpoet_router*
from the strings to translate and the problem was solved.

I checked the post notifications settings and the post selection is simply tag:featured

The wp_mailpoet_statistics_opens database table appears all right (it was not in the rables idenified for repair.

As we just posted a new article today, the sending of the emails with mailpoet crashed the website with database has gone away (no need to suggest we checked the FAQ, we did that a couple of years ago and everything is in order with a lot of space and resources for mailpoet :)).
This time, i copied the message before repairing the database here they are copied below – also we have fatal errors recorded in our log starting on 31 May linked to mailpoet.

Addition/edit: I just checked the error log and we have fatal errors since 12 May 2022, always the same, taking place each time we send mailpoet emails for post notifications. I am afraid to copy the error log here as it could (?) create security breach issue? Each tme there are 3 errors for each “fatal error” recorded (the tool used is woocommerce log status debug), with things like /mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/EntityRepository.php(73): MailPoetVendor\Doctrine\ORM\Persisters\Entity\BasicEntityPersister-> in … /plugins/mailpoet/vendor-prefixed/doctrine/dbal/lib/Doctrine/DBAL/Driver/AbstractMySQLDriver.php à la ligne 91#!trpst#/trp-gettext#!trpen#

repairing database:
(I did not copy the wc etc tables that were ok):

The wp_users table is okay.

The wp_usermeta table is not okay. It is reporting the following error: 1 client is using or hasn't closed the table properly. WordPress will attempt to repair this table…
    Successfully repaired the wp_usermeta table.

The wp_posts table is not okay. It is reporting the following error: 1 client is using or hasn't closed the table properly. WordPress will attempt to repair this table…
    Successfully repaired the wp_posts table.

The wp_comments table is not okay. It is reporting the following error: 1 client is using or hasn't closed the table properly. WordPress will attempt to repair this table…
    Successfully repaired the wp_comments table.

The wp_links table is okay.

The wp_options table is not okay. It is reporting the following error: 2 clients are using or haven't closed the table properly. WordPress will attempt to repair this table…
    Successfully repaired the wp_options table.

The wp_postmeta table is not okay. It is reporting the following error: 1 client is using or hasn't closed the table properly. WordPress will attempt to repair this table…
    Successfully repaired the wp_postmeta table.

The wp_terms table is okay.

The wp_term_taxonomy table is not okay. It is reporting the following error: 1 client is using or hasn't closed the table properly. WordPress will attempt to repair this table…
    Successfully repaired the wp_term_taxonomy table.

The wp_term_relationships table is not okay. It is reporting the following error: 1 client is using or hasn't closed the table properly. WordPress will attempt to repair this table…
    Successfully repaired the wp_term_relationships table.

The wp_termmeta table is okay.

The wp_commentmeta table is not okay. It is reporting the following error: 1 client is using or hasn't closed the table properly. WordPress will attempt to repair this table…
    Successfully repaired the wp_commentmeta table.

The wp_actionscheduler_actions table is not okay. It is reporting the following error: 1 client is using or hasn't closed the table properly. WordPress will attempt to repair this table…
    Successfully repaired the wp_actionscheduler_actions table.

The wp_actionscheduler_claims table is not okay. It is reporting the following error: 2 clients are using or haven't closed the table properly. WordPress will attempt to repair this table…
    Successfully repaired the wp_actionscheduler_claims table.

The wp_actionscheduler_groups table is okay.

The wp_actionscheduler_logs table is not okay. It is reporting the following error: 1 client is using or hasn't closed the table properly. WordPress will attempt to repair this table…
    Successfully repaired the wp_actionscheduler_logs table.

The wp_wc_category_lookup table is okay.

Repairs complete. Please remove the following line from wp-config.php to prevent this page from being used by unauthorized users.

Looking forward to a solution and thanks for your help
Helene

• This reply was modified 2 years, 9 months ago by HeleneL.