Title: [Plugin: WPML Multilingual CMS]  Activation error
Last modified: August 20, 2016

---

# [Plugin: WPML Multilingual CMS] Activation error

 *  Resolved [Emre](https://wordpress.org/support/users/emrearman/)
 * (@emrearman)
 * [15 years ago](https://wordpress.org/support/topic/plugin-wpml-multilingual-cms-activation-error/)
 * I’ve updated my current WP to 3.1.2 and installed this plugin. But once I activate
   it, it says “You have no access for this page.” for every admin page. I cannot
   do anything but deleting it from FTP. Such a strange problem huh?
    Anyone can
   help?
 * [http://wordpress.org/extend/plugins/sitepress-multilingual-cms/](http://wordpress.org/extend/plugins/sitepress-multilingual-cms/)

Viewing 1 replies (of 1 total)

 *  Thread Starter [Emre](https://wordpress.org/support/users/emrearman/)
 * (@emrearman)
 * [15 years ago](https://wordpress.org/support/topic/plugin-wpml-multilingual-cms-activation-error/#post-2095405)
 * I’ve debugged and got the error msg as told on plugin site. I can send the debug
   report to verify the problem!

Viewing 1 replies (of 1 total)

The topic ‘[Plugin: WPML Multilingual CMS] Activation error’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/sitepress-multilingual-cms.svg)
 * [WPML Multilingual CMS](https://wordpress.org/plugins/sitepress-multilingual-cms/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/sitepress-multilingual-cms/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/sitepress-multilingual-cms/)
 * [Active Topics](https://wordpress.org/support/plugin/sitepress-multilingual-cms/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/sitepress-multilingual-cms/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/sitepress-multilingual-cms/reviews/)

 * 1 reply
 * 1 participant
 * Last reply from: [Emre](https://wordpress.org/support/users/emrearman/)
 * Last activity: [15 years ago](https://wordpress.org/support/topic/plugin-wpml-multilingual-cms-activation-error/#post-2095405)
 * Status: resolved