Title: Incorrect string display
Last modified: May 8, 2023

---

# Incorrect string display

 *  Resolved [Panos Web](https://wordpress.org/support/users/siteworks/)
 * (@siteworks)
 * [3 years ago](https://wordpress.org/support/topic/incorrect-string-display/)
 * Hi support,
 * thanks for the very useful plugin.
 * We have a problem with a.. “staborn” string that is displayed incorrectly.
 * It is displayed in the translated language both in the source and the translated
   language, and we fail to correct it.
 * When we try to edit it, it’s appearing as “undefined” in the string’s translation
   options.
 * It is the string of woocommerce checkout button, in the checkout page, where 
   we use a Paypal express plugin as payment method.
 * We would like to help us here.
 * The site utilizes Translationpress Version 2.5.1, WordPress 5.6.10 and woocommerce
   Version 4.9.2 and the paypal plugin is **YITH PayPal Express Checkout for WooCommerce**
   Version 1.7.0.
 * Thanks
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fincorrect-string-display%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 10 replies - 1 through 10 (of 10 total)

 *  Thread Starter [Panos Web](https://wordpress.org/support/users/siteworks/)
 * (@siteworks)
 * [3 years ago](https://wordpress.org/support/topic/incorrect-string-display/#post-16730073)
 * Can you help please with this?
 * Thanks
 *  [Andrei](https://wordpress.org/support/users/andrei202/)
 * (@andrei202)
 * [3 years ago](https://wordpress.org/support/topic/incorrect-string-display/#post-16745027)
 * Greetings,
 * We deeply apologize for the delayed response.
 * There has been a great load on our support team in the past few days, but such
   a long reply time is very uncommon.
 * Would you mind sending over a screenshot of the problem so I can have a better
   look?
 * Regards
 *  Thread Starter [Panos Web](https://wordpress.org/support/users/siteworks/)
 * (@siteworks)
 * [3 years ago](https://wordpress.org/support/topic/incorrect-string-display/#post-16746182)
 * Hi,
 * no worries..
 * I send you below in two screenshots, the problem.
 * The problem is that the supposed-to-be translated greek string “Ολοκλήρωση παραγγελίας
   στο Paypal” ( checkout button string ) appears also **the same** in the initiative
   english language.
 * ![](https://ibb.co/VmZj2mN)
 * ![](https://ibb.co/Jmzgq0m)
 *  Thread Starter [Panos Web](https://wordpress.org/support/users/siteworks/)
 * (@siteworks)
 * [3 years ago](https://wordpress.org/support/topic/incorrect-string-display/#post-16746193)
 * greek checkout page
 * [https://ibb.co/Jmzgq0m](https://ibb.co/Jmzgq0m)
 * english checkout page
 * [https://ibb.co/VmZj2mN](https://ibb.co/VmZj2mN)
 * both the same
 * you can test it live here , if you wish [https://banjo-show.com/shop/](https://banjo-show.com/shop/)
 * just add a product in the cart and go to checkout in both languages
 * Thanks in advance
 *  Thread Starter [Panos Web](https://wordpress.org/support/users/siteworks/)
 * (@siteworks)
 * [3 years ago](https://wordpress.org/support/topic/incorrect-string-display/#post-16764922)
 * Hi,
 * Did you check the info we gave you please?
 * Any help with this, would be appreciated.
 * Thanks
 *  Plugin Support [Alex](https://wordpress.org/support/users/alexcozmoslabs/)
 * (@alexcozmoslabs)
 * [2 years, 11 months ago](https://wordpress.org/support/topic/incorrect-string-display/#post-16819423)
 * I set this ticket as Resolved.
   You can also change its status back to unresolved
   and let us know by replying to this topic if your issue still needs attention.
   Another option is to let this ticket as it is and open a new one where to mention
   the issue again and ask for support.
 *  Thread Starter [Panos Web](https://wordpress.org/support/users/siteworks/)
 * (@siteworks)
 * [2 years, 11 months ago](https://wordpress.org/support/topic/incorrect-string-display/#post-16819522)
 * Hi,
 * But you didn’t give us any help with this !
 *  [Andrei](https://wordpress.org/support/users/andrei202/)
 * (@andrei202)
 * [2 years, 11 months ago](https://wordpress.org/support/topic/incorrect-string-display/#post-16819529)
 * We try to manage the tickets as efficiently as possible, but sometimes we need
   to take their pulse and see if the reported problems are still active to know
   if assistance is still needed.
   I will be getting back to you as soon as possible
   on this matter
 *  [Andrei](https://wordpress.org/support/users/andrei202/)
 * (@andrei202)
 * [2 years, 11 months ago](https://wordpress.org/support/topic/incorrect-string-display/#post-16821299)
 * Greetings,
 * Please visit the Advanced tab of TranslatePress and activate the: “Fix missing
   dynamic content” .
 * Let me know if this works.
 *  Thread Starter [Panos Web](https://wordpress.org/support/users/siteworks/)
 * (@siteworks)
 * [2 years, 11 months ago](https://wordpress.org/support/topic/incorrect-string-display/#post-16827123)
 * Thanks,
 * we’ve tested all these similar workarounds, but they don’t have result.

Viewing 10 replies - 1 through 10 (of 10 total)

The topic ‘Incorrect string display’ is closed to new replies.

 * ![](https://ps.w.org/translatepress-multilingual/assets/icon.svg?rev=3166541)
 * [TranslatePress - Translate Multilingual sites with AI Translation](https://wordpress.org/plugins/translatepress-multilingual/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/translatepress-multilingual/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/translatepress-multilingual/)
 * [Active Topics](https://wordpress.org/support/plugin/translatepress-multilingual/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/translatepress-multilingual/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/translatepress-multilingual/reviews/)

 * 10 replies
 * 3 participants
 * Last reply from: [Panos Web](https://wordpress.org/support/users/siteworks/)
 * Last activity: [2 years, 11 months ago](https://wordpress.org/support/topic/incorrect-string-display/#post-16827123)
 * Status: resolved