Title: Optimize pll_register_string
Last modified: April 14, 2020

---

# Optimize pll_register_string

 *  [Nextendweb](https://wordpress.org/support/users/nextendweb/)
 * (@nextendweb)
 * [6 years, 1 month ago](https://wordpress.org/support/topic/optimize-pll_register_string/)
 * Hi [@chouby](https://wordpress.org/support/users/chouby/),
    we have huge amount
   of strings to be registered with `pll_register_string` function. It seems like
   registering with `pll_register_string` only needed on the page of `Languages -
   > Strings translations` and on the `Clean strings translation database` action.
   Do you have an action which only only runs only when string should be registered?
 * Registering string on frontend and on other admin pages uses unnecessary resources.

The topic ‘Optimize pll_register_string’ is closed to new replies.

 * ![](https://ps.w.org/polylang/assets/icon-256x256.png?rev=3433336)
 * [Polylang](https://wordpress.org/plugins/polylang/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/polylang/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/polylang/)
 * [Active Topics](https://wordpress.org/support/plugin/polylang/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/polylang/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/polylang/reviews/)

 * 0 replies
 * 1 participant
 * Last reply from: [Nextendweb](https://wordpress.org/support/users/nextendweb/)
 * Last activity: [6 years, 1 month ago](https://wordpress.org/support/topic/optimize-pll_register_string/)
 * Status: not resolved