Success Message problem

This is hard for me, especially in Russian ??

Firstly, have you modified the success message? If so, perhaps you have added the 0 at the end by mistake.

In my language file for ‘Thank you. Your signature has been added to the petition.’ I have `Спасибо. Ваша подпись была добавлена ??в петицию.’

Is that the right translation?

Thank you for a quick response. I need to say that it’s not Russian, it’s the Ukrainian language. But anyway. I checked my custom message and it’s ok. But when I sign a petition I get zero symbol at the end of it. For example, my phrase in custom thankyou message’s field is “Thanks, bro!”, but visitors receive “Thanks, bro!0”

• This reply was modified 5 years ago by Mixa.

Oops…did I just stary a war? Sorry :o)

I will check this out and get back to you.

Thank you. I’ll try to fix this with jQuery DOM-manipulations as a temporary solution.

Mixa, I just signed your petition and can see it is happening Steve, дяку?мо за ваш п?дпис!0

I don’t provide a Ukranian translation do I? It would be speakout-uk_UK.po/mo and that isn’t in my list of language files. So I don’t think the source of this is the plugin itself.

Can you link to a screenshot like this https://gyazo.com/9d5cc41c290a56af070914c14cd74caf especially showing the field the arrow points to.

I am wondering if the 0 is in there.

Sure. There is no 0 at the end

https://ecoaction.org.ua/wp-content/uploads/2019/11/Capture11.png

• This reply was modified 5 years ago by Mixa.

This is really strange. I haven’t had any other reports of the same thing which leads to think it is either the language file or your WordPress.

Which language is your WordPress set to? I don’t provide a Ukranian translation so I am not sure where it is coming from

I just had an idea. I will switch my language to Ukranian and see what happens.

Nothing heard about this. Solved?

Well, the problem still there, and the problem only with that particular this petition (maybe due to the settings).

I just tested the plugin with a new petition on the clean page and it works well. So, I thought that the root of the problem in my custom page template and jQuery DOM manipulations. But when I use a shortcode of the problematic petition on the same page I get again that result.

OK…well, that makes it easy for me :o)