Title: Server 500 error when using WPML
Last modified: October 16, 2020

---

# Server 500 error when using WPML

 *  [thomhayes](https://wordpress.org/support/users/thomhayes/)
 * (@thomhayes)
 * [5 years, 7 months ago](https://wordpress.org/support/topic/server-500-error-when-using-wpml/)
 * I’ve seen this issue cropped up a few years ago, and someone found a fix. It’s
   the last comment on this page: [https://wordpress.org/support/topic/500-internal-server-error-on-wpml/](https://wordpress.org/support/topic/500-internal-server-error-on-wpml/)
 * But it’s not been added to any updates. Can anyone confirm when this fix will
   be in place? Obviously, without it, we can’t use it.
 * Cheers

Viewing 1 replies (of 1 total)

 *  Thread Starter [thomhayes](https://wordpress.org/support/users/thomhayes/)
 * (@thomhayes)
 * [5 years, 7 months ago](https://wordpress.org/support/topic/server-500-error-when-using-wpml/#post-13566293)
 * Hi guys – any update on this? Cheers!

Viewing 1 replies (of 1 total)

The topic ‘Server 500 error when using WPML’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/loomisoft-content-blocks_3fbcc2.svg)
 * [Reusable Content & Text Blocks by Loomisoft](https://wordpress.org/plugins/loomisoft-content-blocks/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/loomisoft-content-blocks/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/loomisoft-content-blocks/)
 * [Active Topics](https://wordpress.org/support/plugin/loomisoft-content-blocks/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/loomisoft-content-blocks/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/loomisoft-content-blocks/reviews/)

## Tags

 * [server 500](https://wordpress.org/support/topic-tag/server-500/)

 * 1 reply
 * 1 participant
 * Last reply from: [thomhayes](https://wordpress.org/support/users/thomhayes/)
 * Last activity: [5 years, 7 months ago](https://wordpress.org/support/topic/server-500-error-when-using-wpml/#post-13566293)
 * Status: not resolved