Title: Cannot save configuration settings
Last modified: October 21, 2016

---

# Cannot save configuration settings

 *  Resolved [pwssupport](https://wordpress.org/support/users/pwssupport/)
 * (@pwssupport)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/cannot-save-configuration-settings/)
 * Hi,
 * We used ADI 1.1.5 for our multisite network which works great. I installed the
   Next ADI 2.0.10 to our network due to SSO needs but I cannot get it to work. 
   I kept getting below error message when trying to save my changes. I tested this
   version by using single site installation and still got the same problem. Any
   feedback? Thanks!
 *     ```
       angular.min.js?ver=1.0:116 SyntaxError: Unexpected token u in JSON at position 0 at Object.parse (native)
       at DataService.vm.cleanOptions (https://test/wp-content/plugins/next-active-directory-integration/js/app/profile-options/services/data.service.js?ver=1.0:20:25)
       at DataService.vm.mergeScopeOptions (https://test/wp-content/plugins/next-active-directory-integration/js/app/profile-options/services/data.service.js?ver=1.0:71:42)
       at m.ProfileController.$scope.save (https://test/wp-content/plugins/next-active-directory-integ…on/js/app/profile-options/controllers/profile.controller.js?ver=1.0:161:36)
       at fn (eval at compile (https://test/wp-content/plugins/next-active-directory-integration/js/libraries/angular.min.js?ver=1.0:226:440), <anonymous>:4:203)
       at b (https://test/wp-content/plugins/next-active-directory-integration/js/libraries/angular.min.js?ver=1.0:124:63)
       at e (https://test/wp-content/plugins/next-active-directory-integration/js/libraries/angular.min.js?ver=1.0:268:394)
       at m.$eval (https://test/wp-content/plugins/next-active-directory-integration/js/libraries/angular.min.js?ver=1.0:142:467)
       at m.$apply (https://test/wp-content/plugins/next-active-directory-integration/js/libraries/angular.min.js?ver=1.0:143:188)
       at HTMLButtonElement.<anonymous> (https://test/wp-content/plugins/next-active-directory-integration/js/libraries/angular.min.js?ver=1.0:268:446)
       ```
   

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

 *  Plugin Author [schakko](https://wordpress.org/support/users/schakko/)
 * (@schakko)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/cannot-save-configuration-settings/#post-8339878)
 * This is the first time I see any JavaScript errors. My guess is that the returned
   JSON content is UTF-8 but your WordPress delivers another charset.
    How does 
   the HTTP server reponse which contains the JSON content look like? You can see
   it with the developer console of your browser.
 *  Thread Starter [pwssupport](https://wordpress.org/support/users/pwssupport/)
 * (@pwssupport)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/cannot-save-configuration-settings/#post-8340276)
 * We are using utf8mb4_unicode_ci which is still UTF-8. So, it shouldn’t be matter.
   To be safe, I created another site by using utf8_general_ci, but still got the
   same result.
 * Response Headers:
 *     ```
       HTTP/1.1 200 OK
       Date: Fri, 21 Oct 2016 19:29:27 GMT
       Server: Apache/2.4.23 (Win32) mod_authnz_sspi/0.1.0 OpenSSL/1.0.2h PHP/5.6.25
       X-Powered-By: PHP/5.6.25
       Expires: Wed, 11 Jan 1984 05:00:00 GMT
       Cache-Control: no-cache, must-revalidate, max-age=0
       X-Frame-Options: SAMEORIGIN
       Keep-Alive: timeout=5, max=96
       Connection: Keep-Alive
       Transfer-Encoding: chunked
       Content-Type: text/html; charset=UTF-8
       ```
   
 *  Thread Starter [pwssupport](https://wordpress.org/support/users/pwssupport/)
 * (@pwssupport)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/cannot-save-configuration-settings/#post-8349310)
 * Hi [@schakko](https://wordpress.org/support/users/schakko/), Any updates on this
   issue? Thank you.
 *  Plugin Author [schakko](https://wordpress.org/support/users/schakko/)
 * (@schakko)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/cannot-save-configuration-settings/#post-8351861)
 * [@pwssupport](https://wordpress.org/support/users/pwssupport/) Would you please
   include the HTTP body in your reply? Does the debug.log of NADI contains any 
   error messages? Does the error.log of your Apache contains any errors?
 *  Thread Starter [pwssupport](https://wordpress.org/support/users/pwssupport/)
 * (@pwssupport)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/cannot-save-configuration-settings/#post-8393260)
 * I re-apply Next ADI to our Linux server environment and it works fine. Might 
   be the issue under my local Window environment. I will rebuild it. We can consider
   this issue is resolved. Thanks for your help.
 *  Plugin Author [schakko](https://wordpress.org/support/users/schakko/)
 * (@schakko)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/cannot-save-configuration-settings/#post-8395571)
 * Glad to hear that, thank you for the info!

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

The topic ‘Cannot save configuration settings’ is closed to new replies.

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

## Tags

 * [SSO](https://wordpress.org/support/topic-tag/sso/)

 * 6 replies
 * 2 participants
 * Last reply from: [schakko](https://wordpress.org/support/users/schakko/)
 * Last activity: [9 years, 7 months ago](https://wordpress.org/support/topic/cannot-save-configuration-settings/#post-8395571)
 * Status: resolved