David GARNIER

Forum Replies Created

Viewing 9 posts - 1 through 9 (of 9 total)
in reply to: Subscriber status not updating #140177

David GARNIER
Participant

I tested again with all other plugins disabled (I assume just deactivating plugins is sufficient?) but that didn’t fix the issue. Doesn’t appear to be a plugin conflict.

The only thing I can think of that’s not very usual is that we’re using the wpdm_before_email_download_link hook in our theme to send email notifications to administrators. But I also tested with the hook and the function it calls commented out and got the same result.

Thanks.

in reply to: Subscriber status not updating #140170

David GARNIER
Participant

Hi,

We’ve updated the plugin to 5.3.0 and we’re still experiencing this issue – can you help us fix this?

Thanks.

in reply to: Subscriber status not updating #135234

David GARNIER
Participant

Hi,

We’re using WPDM version 5.1.20, along with WordPress 5.5 and PHP 7.4.

if possible, please, give your temporary wp-admin login details in a private reply for checking the issue.

Unfortunately, that’s one thing I’m not allowed to do. Is there another way we can debug this?

Thanks.

in reply to: Email header encoding #111895

David GARNIER
Participant

That’s good to know.

Thank you.

in reply to: Email header encoding #111891

David GARNIER
Participant

Hi,

I did as you suggested, but I still had the issue. However, using html_entity_decode instead did the trick apparently (found someone who had a similar problem here: https://wordpress.stackexchange.com/questions/215684/wp-mail-encode-in-rsquo-in-subject).

However if I change the plugin’s code like this, doesn’t that mean the changes will be lost next time the plugin is updated?

Thanks.

in reply to: Email header encoding #111727

David GARNIER
Participant

Hi,

I did as you suggested using option #1 and it does fix encoding issues with [#sitename#], however that’s unfortunately about half of the issue. Special characters in [#package_name#] are still encoded (only when the variable is used in the email’s subject, in the body, there’s no issue). I’ve checked in the database and the characters aren’t encoded, unlike the blogname. Also, if I write special characters in the template’s subject manually, they get encoded too.

Thanks.

in reply to: Email header encoding #111399

David GARNIER
Participant

Of course HTML encoding is interpreted in this forum apparently so my initial comment doesn’t make much sense (being able to edit/preview our own posts would be nice). What I meant as an example is that “&” gets converted to “&amp ;”.

By the way, I tried using %26 as well but all it did was to revert the template to the original one.

Thanks.

in reply to: wpdm_before_email_download_link hook #111366

David GARNIER
Participant

Hi,

This works great, thank you.

in reply to: wpdm_before_email_download_link hook #111200

David GARNIER
Participant

Hi,

Well I’m using the default form with the “Ask for Visitor’s Name” checkbox checked. The name of the field when I inspect the page is “custom_form_field[name]”, I’ve tried using that without success. I’ve also checked the contents of the $post array for all its values in case I’ve missed the name but it doesn’t seem to be present in the array at all.

I’ve noticed it’s possible to customize the form on the demo website, which is also using all of the free plugins. I don’t have the option, but we’re also not using the free plugins, is this feature enabled by one of these? I assume if $post is expanded with any of the additional custom fields, I could create a custom name field and get the value from there.

Thank you.

Viewing 9 posts - 1 through 9 (of 9 total)