ypeynaud

Hi @timersys,

For information, I tried to upgrade to Emails Template Version 1.3.2.1 but it did not solve the problem. Still “Empty Body Emails”, only the first one sent.

Had to retrofit to Version 1.3.1.2 and working fine again.

Cheers

Thank you @johnjamesjacoby for your response! Good if my experience may possibly be useful in some way. It’s really a minimum in exchange to using such a nice plugin.

Regarding taxonomies, I also had to move some but it was easy through simple bulk-editing. So no real need to be able to translate taxonomies during the switch, although it would have been even more elegant ??

Thanks for all.

I have investigated further this “comment_type” field in the wp_comments database and as far as I understand, the types expected for this field in WordPress are: ‘comment’, ‘trackback’, ‘pingback’ or ‘pings’.

For some reason, the plugin generating the custom post types I want to switch from (namely DWQA Questions & Answers) uses a ‘dwqa-comment’ type for this field.

So the issue has nothing to do with PST, sorry. Simply changing ‘dwqa-comment’ to ‘comment’ in the wp_comments database fully solves the problem.

I let this post available in case it might help someone else.

OK, I have had a look at the WP database and it turns out that the wp_comments database do have a “comment_type” field storing the comment type.

In my case, the custom post type I switched has its own comment type. But when using PST to switch from CPT to regular post type, this field is not updated, intentionally or not.

As a result, it depends how the theme chooses to display comments. On the back end, probably all comment types are fetched when displaying regular posts, so the comments appear. But on the front end, probably only the “comment” comment type is fetched, so the comments coming from the CPT do not show since they do not have this “comment” type.

So it comes back to the question in my first post: could/would/should PST switch the comment type as well when switching post type? A filter would be convenient.

Thanks in advance for your answer or any tip.

Hi @timersys,

Unfortunately, I can’t provide access to my site. As I said, I have downgraded Email Template to 1.3.1.2, both on my production site (because my customers need to receive emails) and also on my staging site (because I have on-going developments also needing to send multiple emails).

In all cases, the error is clearly the same: “empty body”. Maybe I could check other things for you if this not too complicated?

Hi @benoit0neall,

Thanks for your answer. Yes, the process you propose is actually the one I have considered. But I’ve not succeeded in implementing it yet, hence my question.

It would be very interesting if you could provide it in a future version. It would allow my site to really be GDPR-compliant (which is not truly the case yet due to this automatic subscription process without consent).

Thanks!

Thanks Mike for your proposal but it’s not necessary: it appears that the problem was once again a matter of caching: by using anonymous windows, then flushing all pages from my site, the problem I mentioned disappeared. All is running fine with v2.1.10 on both my staging and production sites.

Sorry for the inconvenience and thanks again for your effective support!

Yves.

You’re right, I’m still with previous version on my production site. The problem I describe appears on my staging site which has been upgraded to v 2.1.10. I’m developping a new feature requiring a form which can’t be pushed to production until the issue is fixed.

Hi there,

I have a similar issue, apparently from version 2.1.9, also on 2.1.10. The scroll appears when you click ‘regular’ links (not with the modal-link class), as well as when you click in a field of a form to fill it. Which is particularly troublesome since you have to re-scroll down and reselect your field again, but when doing so, you are re-scrolled up again, and so on…

Yes! I do confirm it’s working fine now, with version 2.1.9 installed and “Use legacy method” checked.

It was obviously a cache problem again: opening an incognito window or flushing the navigator cache made it working fine ??

Again thanks a lot for your plugin and your support (I’ve made a small donation to this end).

Yves.

I tried turning on the legacy method in the plugin settings. It actually removes the 404 errors but the type error I mentioned earlier is still there:

TypeError: undefined is not an object (evaluating '$('#modal-content ' + postAnchor).offset().top') appearing on wp-post-modal-public.js 224:100.

Any idea?

Yes, the page loads anyway, but it doesn’t scroll, and it is really important for me to make the pages scroll at the right place: I use the plugin for ensuring GDPR compliance, and let users easily point to the right article of the right policy, when they subscribe to the site or to the newsletter, or when they contact a service, etc. Not pointing directly to the right article might be interpreted by the authorities as making such users confused, thus NOT complying with GDPR rules. So I do have to make this working, no choice.

Thanks again for any help in interpreting the error in the js code. I understand CSS, a little of PHP and quite nothing of Javascript. That’s why I use plugins. And yours might be really really useful, particularly with respect to GDPR compliance!

Yves.

Thanks for your answer but from my side, the anchor really is the second one, the one without the “/”, not the first one you mention.

And as I say, the 404 error also happens on a plain page link, without any #, like this one:
https://strategy4startup.com/en/conditions-generales-dutilisation-et-de-vente/

This is for example the first link in the page I mentioned:
https://strategy4startup.com/en/politique-de-respect-de-la-vie-privee/

So the problem is elsewhere, but where? My javascript understanding is very limited and I’m not able to find out.

Which slash do you mean? The anchor in the source code is:

Définitions

By the way, I realised that the first link in the page (without any internal anchor) generates the same 404 error:
Conditions Générales d’Utilisation et de Vente du site

What do I do wrong?
Thx,
Yves

Unfortunately not. I’ve updated to 2.1.9 and the TypeError is actually solved but I’m back to the 404 error I mentioned earlier.

Hi @allurewebsolutions,

Thanks for the answer. My site is now online so maybe you could give it a glance and tell me?

To see the problem:

– Go to the Privacy Policy page (content only available in French yet):
https://strategy4startup.com/en/politique-de-respect-de-la-vie-privee/

– In the first “Objet” paragraph, click on the second link “Définitions”, which should open the site’s General Terms of Use and Sale in a popup window, and scroll down to the “Definitions” article inside the popup.

As you can see, it doesn’t scroll, and the console returns now the following error:

TypeError: undefined is not an object (evaluating '$('#modal-content ' + postAnchor).offset().top')

This is a different error than on my development site but the result in the same: the popup opens but doesn’t scroll. And I’m still not able to understand the issue and fix it.

Thanks in advance for any tips!

Regards,
Yves.