WordPMTL

Thanks!

Was this update released? I still see 3.0.4.0, from 5 days ago, as the latest one available.

The plugin will support French or English interfaces, but within a multilingual website it will need to use both languages for the restriction text.

As mentioned above, commenting out those lines fixes it.

Thanks! Even if I need to pay for a $10 add-on to allow this I’d definitely do it. You’ve got a great plugin and I appreciate your quick reply.

Hello amitkvint. Can you please let us know if this issue has been fixed in WPML?

Thanks for the prompt reply.

If I can just modify the HTML of the email that is fine. Can you suggest the best way for me to do that? Do I have to change your plugin code or can I use a filter hook?

Hi Jan, did you have a chance to see my reply? Thanks.

Hi Jan. Yes, the client and I can both access the site. But I find it strange that a website I host would send an email from my server with an altered domain name in the “from” address and the recovery URL. How can these things be manipulated when submitting a password recovery form?

Hi Alan. I’m having the same issue in internet explorer with the sample plugin and the Flatsome theme. Were you able to solve this? If so, could you please tell me how? Thanks.

I use a similar plugin (MainWP) and I also see this error message at the top of my “Sites” page. But Postman is working fine.

I should note I am using Vesta CP on a Digital Ocean droplet. I have tried disabling all plugins and using a default theme.

Hi Josh,

Just wondering if you ever solved this. I have a website using a Let’s Encrypt SSL which I just moved to an identical server (just a different IP).

And on that new server, the homepage has a redirect loop. All other pages load fine. Tried for a while to resolve without success.

Thanks.

Thanks Jordy. I must have had an outdated version.

I was able to update my review to 5 stars. This thread explains how (go to the main review page, and scroll to the bottom). Somewhat counterintuitive but it worked!

FYI, using the html code from your website results in a form that works immediate without delay. So, assuming the plugin and the website use the same Constant Contact backend to process the form entries, I would think the issue is more related to the form generated by the plugin.