# "Error updating information, contact site admin"

**URL:** https://meta.discourse.org/t/error-updating-information-contact-site-admin/28885
**Category:** WordPress
**Created:** [16 مايو 2015، 9:57ص UTC](https://meta.discourse.org/t/error-updating-information-contact-site-admin/28885 "2015-05-16T09:57:55Z")
**Posts on this page:** 20
**Page:** 1

<div class="post-metadata">

### Author: ![namtrok](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/namtrok/32/116125_2.png) [@namtrok](https://meta.discourse.org/u/namtrok)
#### Post date: [16 مايو 2015، 9:57ص UTC](https://meta.discourse.org/t/error-updating-information-contact-site-admin/28885/1 "2015-05-16T09:57:55Z")

</div>

Hi,

Loving Discourse, I’ve had it installed for almost 4 weeks now and connected to [my wordpress site through SSO](http://nomadtogether.com). I use “PrimeTime [WP Discourse](https://github.com/discourse/wp-discourse) SSO” as the plugin in Wordpress, and it works like a champ.

However I’ve been notified by one of my users who has logged in successfully before that he is getting the following error when trying to login to our discourse install today. “Error updating information, contact site admin” A screenshot can be found here: [Dropbox - Error - Simplify your life](https://www.dropbox.com/s/ts6fmqn6y42frih/Screen%20Shot%202015-05-16%20at%208.47.25%20am.png?dl=0)

I am able to impersonate the user via Discourse without issues.

When I login as the user in wordpress and click over to Discourse I receive the same error message on multiple browsers even after the browser cache is cleared.

In the log file I’m getting: “Job exception: 400 Bad Request”

And finally my Discourse version is: v1.3.0.beta9 +15 running on a linode VPS.

I’ve tried deactivating and re-activating the user but both error messages still occur (“Error updating information, contact site admin” on the client side and “Job exception: 400 Bad Request” on the server side)

Any other thoughts on how I can fix this or further troubleshoot this?

Thanks for your help!

---

<div class="post-metadata">

### Author: ![Grex315](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/grex315/32/115868_2.png) [@Grex315](https://meta.discourse.org/u/Grex315)
#### Post date: [16 مايو 2015، 10:42ص UTC](https://meta.discourse.org/t/error-updating-information-contact-site-admin/28885/2 "2015-05-16T10:42:59Z")

</div>

What does the [discourse sso](https://meta.discourse.org/t/13045?silent=true) info say. I had an issue like this before where the  
avatar url being passed was invalid.

---

<div class="post-metadata">

### Author: ![namtrok](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/namtrok/32/116125_2.png) [@namtrok](https://meta.discourse.org/u/namtrok)
#### Post date: [16 مايو 2015، 11:02ص UTC](https://meta.discourse.org/t/error-updating-information-contact-site-admin/28885/3 "2015-05-16T11:02:06Z")

</div>

the only thing in /logs is “Job exception: 400 Bad Request” is there somewhere else I can see more detailed logs? (I’d love to know what URL is getting a 400 error!)

---

<div class="post-metadata">

### Author: ![Grex315](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/grex315/32/115868_2.png) [@Grex315](https://meta.discourse.org/u/Grex315)
#### Post date: [16 مايو 2015، 11:03ص UTC](https://meta.discourse.org/t/error-updating-information-contact-site-admin/28885/4 "2015-05-16T11:03:08Z")

</div>

Sorry meant to say sso info for the user.

---

<div class="post-metadata">

### Author: ![namtrok](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/namtrok/32/116125_2.png) [@namtrok](https://meta.discourse.org/u/namtrok)
#### Post date: [16 مايو 2015، 12:18م UTC](https://meta.discourse.org/t/error-updating-information-contact-site-admin/28885/5 "2015-05-16T12:18:00Z")

</div>

His profile picture URL is empty. Email and username are his email address. ID is correct.

---

<div class="post-metadata">

### Author: ![namtrok](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/namtrok/32/116125_2.png) [@namtrok](https://meta.discourse.org/u/namtrok)
#### Post date: [16 مايو 2015، 5:59م UTC](https://meta.discourse.org/t/error-updating-information-contact-site-admin/28885/6 "2015-05-16T17:59:38Z")

</div>

I now have two users with this issue. The second user had this issue upon initial sign up today.

What can I do?

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [16 مايو 2015، 9:30م UTC](https://meta.discourse.org/t/error-updating-information-contact-site-admin/28885/7 "2015-05-16T21:30:12Z")

</div>

> [@namtrok](#):
>
> the log file I’m getting: “Job exception: 400 Bad Request”

What is the stack trace? There is something about the data for these users.

---

<div class="post-metadata">

### Author: ![namtrok](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/namtrok/32/116125_2.png) [@namtrok](https://meta.discourse.org/u/namtrok)
#### Post date: [19 مايو 2015، 10:01ص UTC](https://meta.discourse.org/t/error-updating-information-contact-site-admin/28885/8 "2015-05-19T10:01:45Z")

</div>

How do I get a stack trace?

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [19 مايو 2015، 10:40ص UTC](https://meta.discourse.org/t/error-updating-information-contact-site-admin/28885/9 "2015-05-19T10:40:17Z")

</div>

Try the stack trace tab at the bottom

---

<div class="post-metadata">

### Author: ![namtrok](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/namtrok/32/116125_2.png) [@namtrok](https://meta.discourse.org/u/namtrok)
#### Post date: [19 مايو 2015، 11:10ص UTC](https://meta.discourse.org/t/error-updating-information-contact-site-admin/28885/10 "2015-05-19T11:10:24Z")

</div>

I see a “Back Trace” tab – totally missed that before!

here’s the output:

```
/usr/local/lib/ruby/2.0.0/open-uri.rb:353:in `open_http'
/usr/local/lib/ruby/2.0.0/open-uri.rb:709:in `buffer_open'
/usr/local/lib/ruby/2.0.0/open-uri.rb:210:in `block in open_loop'
/usr/local/lib/ruby/2.0.0/open-uri.rb:208:in `catch'
/usr/local/lib/ruby/2.0.0/open-uri.rb:208:in `open_loop'
/usr/local/lib/ruby/2.0.0/open-uri.rb:149:in `open_uri'
/usr/local/lib/ruby/2.0.0/open-uri.rb:689:in `open'
/var/www/discourse/lib/file_helper.rb:17:in `block in download'
/var/www/discourse/lib/file_helper.rb:16:in `open'
/var/www/discourse/lib/file_helper.rb:16:in `download'
/var/www/discourse/app/models/discourse_single_sign_on.rb:131:in `change_external_attributes_and_override'
/var/www/discourse/app/models/discourse_single_sign_on.rb:57:in `lookup_or_create_user'
/var/www/discourse/app/controllers/session_controller.rb:71:in `sso_login'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/abstract_controller/base.rb:189:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/rendering.rb:10:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:552:in `block (2 levels) in compile'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:502:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:502:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:86:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/abstract_controller/callbacks.rb:19:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/rescue.rb:29:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/notifications.rb:159:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/notifications.rb:159:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/abstract_controller/base.rb:136:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.1.10/lib/action_view/rendering.rb:30:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.3/lib/mini_profiler/profiling_methods.rb:106:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal.rb:196:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal.rb:232:in `block in action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/routing/route_set.rb:82:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/routing/route_set.rb:82:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/routing/route_set.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/journey/router.rb:73:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/journey/router.rb:59:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/journey/router.rb:59:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/routing/route_set.rb:692:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/builder.rb:59:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.3/lib/rack/conditionalget.rb:25:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.3/lib/rack/head.rb:11:in `call'
/var/www/discourse/lib/middleware/anonymous_cache.rb:121:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/flash.rb:254:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-1.0.11/lib/message_bus/rack/middleware.rb:67:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.3/lib/rack/session/abstract/id.rb:225:in `context'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.3/lib/rack/session/abstract/id.rb:220:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/cookies.rb:562:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/query_cache.rb:36:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/connection_adapters/abstract/connection_pool.rb:621:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:82:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/remote_ip.rb:76:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/logster-0.8.1/lib/logster/middleware/reporter.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.10/lib/rails/rack/logger.rb:38:in `call_app'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.10/lib/rails/rack/logger.rb:22:in `call'
/var/www/discourse/config/initializers/quiet_logger.rb:10:in `call_with_quiet_assets'
/var/www/discourse/config/initializers/silence_logger.rb:26:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/request_id.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.3/lib/rack/methodoverride.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.3/lib/rack/runtime.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.3/lib/rack/sendfile.rb:112:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.3/lib/mini_profiler/profiler.rb:276:in `call'
/var/www/discourse/lib/middleware/request_tracker.rb:70:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.10/lib/rails/engine.rb:514:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.10/lib/rails/application.rb:144:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.10/lib/rails/railtie.rb:194:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.10/lib/rails/railtie.rb:194:in `method_missing'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.3/lib/rack/builder.rb:138:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.3/lib/rack/urlmap.rb:65:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.3/lib/rack/urlmap.rb:50:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.3/lib/rack/urlmap.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:576:in `process_client'
/var/www/discourse/lib/scheduler/defer.rb:85:in `process_client'
/var/www/discourse/lib/middleware/unicorn_oobgc.rb:95:in `process_client'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:670:in `worker_loop'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:525:in `spawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:140:in `start'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/bin/unicorn:126:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:23:in `load'
/var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:23:in `<main>'

```

---

<div class="post-metadata">

### Author: ![namtrok](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/namtrok/32/116125_2.png) [@namtrok](https://meta.discourse.org/u/namtrok)
#### Post date: [19 مايو 2015، 2:51م UTC](https://meta.discourse.org/t/error-updating-information-contact-site-admin/28885/11 "2015-05-19T14:51:58Z")

</div>

@sam or @codinghorror does that back trace tell you anything?

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [19 مايو 2015، 10:00م UTC](https://meta.discourse.org/t/error-updating-information-contact-site-admin/28885/12 "2015-05-19T22:00:27Z")

</div>

My guess, it’s having trouble downloading the avatar, we should have error handling there

---

<div class="post-metadata">

### Author: ![namtrok](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/namtrok/32/116125_2.png) [@namtrok](https://meta.discourse.org/u/namtrok)
#### Post date: [20 مايو 2015، 12:06ص UTC](https://meta.discourse.org/t/error-updating-information-contact-site-admin/28885/13 "2015-05-20T00:06:37Z")

</div>

Is there a way for me to clear or edit the information for his avatar?

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [20 مايو 2015، 12:44ص UTC](https://meta.discourse.org/t/error-updating-information-contact-site-admin/28885/14 "2015-05-20T00:44:43Z")

</div>

I committed

[https://github.com/discourse/discourse/commit/bd63699d63f09edcac1205f407c1b3576d710102](https://github.com/discourse/discourse/commit/bd63699d63f09edcac1205f407c1b3576d710102)

once it hits tests-passed (in 20 minutes) go ahead and deploy it.

---

<div class="post-metadata">

### Author: ![namtrok](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/namtrok/32/116125_2.png) [@namtrok](https://meta.discourse.org/u/namtrok)
#### Post date: [20 مايو 2015، 1:03ص UTC](https://meta.discourse.org/t/error-updating-information-contact-site-admin/28885/15 "2015-05-20T01:03:07Z")

</div>

Will it be a “release” and if not how do I deploy it, can I tell Discourse to grab a commit ID number and deploy that (would be magical if possible… )

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [20 مايو 2015، 1:04ص UTC](https://meta.discourse.org/t/error-updating-information-contact-site-admin/28885/16 "2015-05-20T01:04:12Z")

</div>

its in tests-passed now [GitHub - discourse/discourse at tests-passed · GitHub](https://github.com/discourse/discourse/tree/tests-passed)

If you use the web ui to update (and are on the tests-passed branch which is default)

you will get the fix.

---

<div class="post-metadata">

### Author: ![namtrok](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/namtrok/32/116125_2.png) [@namtrok](https://meta.discourse.org/u/namtrok)
#### Post date: [20 مايو 2015، 1:09ص UTC](https://meta.discourse.org/t/error-updating-information-contact-site-admin/28885/17 "2015-05-20T01:09:32Z")

</div>

How do I switch branches as I’m on the Beta branch not the tests-passed branch (v1.3.0.beta9 +15) I have no idea how I switched the branch in the first place

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [20 مايو 2015، 1:12ص UTC](https://meta.discourse.org/t/error-updating-information-contact-site-admin/28885/18 "2015-05-20T01:12:34Z")

</div>

no… you are on tests passed … if you were on beta it would not have that +15 that signifies you are 15 commits ahead of beta 🙂

---

<div class="post-metadata">

### Author: ![namtrok](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/namtrok/32/116125_2.png) [@namtrok](https://meta.discourse.org/u/namtrok)
#### Post date: [20 مايو 2015، 1:14ص UTC](https://meta.discourse.org/t/error-updating-information-contact-site-admin/28885/19 "2015-05-20T01:14:21Z")

</div>

Well the admin dashboard still says I’m up-to-date … how long do I need to wait?

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [20 مايو 2015، 1:18ص UTC](https://meta.discourse.org/t/error-updating-information-contact-site-admin/28885/20 "2015-05-20T01:18:04Z")

</div>

Screen shot of:

[http://yoursitename/admin/upgrade](http://yoursitename/admin/upgrade)

please?

[Next page](https://meta.discourse.org/t/error-updating-information-contact-site-admin/28885.md?page=2)
