Do you still remember this blog post 'Art des marionnettes sur l'eau au Vietnam' how your site blogger publish it on the site?

Because how this Easyblog decide to use which language to send email notification to the subscriber is, the system will check the current logged in user login as which language first.

If you recall correctly, when you login from backend, there got an option allow you to choose which language, if you choose English language before you login and publish a new blog post from backend, that email notification content will use English language to send to the subscriber.

By the way, can i have the permission to test re-send your existing blog post email notification to your subscriber?

Of course, you can do the tests on the Tripweo website

Thanks Hazel, it seems like I can reproduce this issue on your site, can you update this Tripweo website FTP details so we can better have a check?

Because I did tried those FTP details what you provided, it seems like that is not for Tripweo website.

In your backoffice for the details of the site, we can put only one site whereas I have licences for two websites TOP DESTINATIONS and TRIPWEO

I added in " Additional Details" of the first website, the information for TRIPWEO

Thanks you by advance

It seems like i getting this following error when i trying to connect :

Status:	Waiting to retry...

Status:	Connecting to 217.182.141.83:21...

Error:	Connection timed out after 20 seconds of inactivity

Error:	Could not connect to server

Then i put port 22

Status:	Connecting to 217.182.141.83...

Response:	fzSftp started, protocol_version=8

Command:	open "admintripweo@217.182.141.83" 22

Error:	Disconnected: No supported authentication methods available (server sent: publickey)

Error:	Could not connect to server

a thousand excuses !!!!!

mistake on the FTP
I rectified

I found out one of the language translation missing the double quote which caused this issue.

You can check my attached screenshot below.

I already help you correct it, it should work fine now.

Thanks for your help.

I could have seen the error. I will pay more attention to the future

Thanks again
Regards
Frank

You're most welcome.

Just for your information, I have locked and marked this thread as resolved to avoid confusions in the future. Please start a new thread if you have any other issue in the future so it will be easier for us to manage your inquiries.

Thanks for understanding