<p>Turns out that this was a bug and a patch was duly applied.</p>

<p>Thanks for the patch Brad.</p>

CC BY-SA 3.0
2014-09-25T07:14:41.250Z
2014-09-25T07:14:41.250Z
Bryan Hickey
<p>If your look at your browser's console on that page you'll see your getting several JavaScript errors:</p>

<p><img src="https://i.sstatic.net/XQWQC.jpg" alt="enter image description here"></p>

<p>Which seems to indicate that some of your files didn't FTP up properly and are corrupted.  Try re-uploading your files and make sure your FTP client is set to transfer in 'auto' mode.</p>

CC BY-SA 3.0
2014-08-13T04:13:28.640Z
Crap.

I've not been FTPing I've been using Git.

Now that I've forced a pull, I've brought down that site.

`Craft does not support backtracking to this version.`
Bryan Hickey
CC BY-SA 3.0
2014-08-13T04:14:35.693Z
Oh, along with some deploy tool?  I'd guess a file didn't get deployed properly then.  Try and redo it?
Brad Bell
CC BY-SA 3.0
2014-08-13T04:14:51.730Z
See above edited comment
Bryan Hickey
CC BY-SA 3.0
2014-08-13T04:17:08.160Z
Now somehow the files in craft/app are older than the database schema that you have in the database.  You can compare version/build/schema version in the craft_info table to the same values in craft/app/Info.php.
Brad Bell
CC BY-SA 3.0
2014-08-13T04:45:33.677Z
So the info.php tells me

`define('CRAFT_VERSION', '2.0');
define('CRAFT_BUILD', '2539');
define('CRAFT_SCHEMA_VERSION', '2.0.1');`

And the DB tells me

`Version 2.0 Build 2528 Scheme 2.0.0`

How can I update my repo to the Version/Build/Scheme in the live DB?
Bryan Hickey
CC BY-SA 3.0
2014-08-13T04:57:08.373Z
If I update my local instance to the current build and then push to the server will this work?
Bryan Hickey
CC BY-SA 3.0
2014-08-13T05:14:32.830Z
I'd put the 2528 (or later) files in place with the 2528 database (you can download 2528 here http://download.buildwithcraft.com/craft/2.0/2.0.2539/Craft-2.0.2539.zip) or download the latest from buildwithcraft.com and let it perform the update.
Brad Bell
CC BY-SA 3.0
2014-08-13T05:52:25.127Z
Both the files and DB are now at current.

Javascript error has returned and occurs only on server and not on local machine :-/

Thoughts?
Bryan Hickey
CC BY-SA 3.0
2014-08-13T16:43:04.563Z
If you want to send some CP/FTP credentials over to support@buildwithcraft.com, we can look at it and I'll update the answer here with the result.
Brad Bell
CC BY-SA 3.0
2014-08-13T03:32:31.543Z
2014-08-13T03:32:31.543Z
Brad Bell
<p>The Admin login screen for my site is not working.</p>

<p>The button to submit my credentials is greyed out and submission by pressing enter is not working either.</p>

<p>Not sure how to go about solving this one or updated the site to fix it if there is a bug?</p>

<control-panel>
Control Panel access. Greyed out button
# Control Panel access. Greyed out button

(Asked by: username_0 on 2014-08-13)

The Admin login screen for my site is not working.

The button to submit my credentials is greyed out and submission by pressing enter is not working either.

Not sure how to go about solving this one or updated the site to fix it if there is a bug?

**Tags:** control-panel


---

## 2 answers

### Answer by username_0 on 2014-09-25. Score: 0 | Accepted answer

Turns out that this was a bug and a patch was duly applied.

Thanks for the patch Brad.


---

### Answer by username_1 on 2014-08-13. Score: 1

If your look at your browser's console on that page you'll see your getting several JavaScript errors:

![enter image description here](https://i.sstatic.net/XQWQC.jpg)

Which seems to indicate that some of your files didn't FTP up properly and are corrupted. Try re-uploading your files and make sure your FTP client is set to transfer in 'auto' mode.

> **Comments:**
> **username_0**: Crap.  I've not been FTPing I've been using Git.  Now that I've forced a pull, I've brought down that site.  `Craft does not support backtracking to this version.`  
> **username_1**: Oh, along with some deploy tool?  I'd guess a file didn't get deployed properly then.  Try and redo it?  
> **username_0**: See above edited comment  
> **username_1**: Now somehow the files in craft/app are older than the database schema that you have in the database.  You can compare version/build/schema version in the craft_info table to the same values in craft/app/Info.php.  
> **username_0**: So the info.php tells me  `define('CRAFT_VERSION', '2.0'); define('CRAFT_BUILD', '2539'); define('CRAFT_SCHEMA_VERSION', '2.0.1');`  And the DB tells me  `Version 2.0 Build 2528 Scheme 2.0.0`  How can I update my repo to the Version/Build/Scheme in the live DB?  
> **username_0**: If I update my local instance to the current build and then push to the server will this work?  
> **username_1**: I'd put the 2528 (or later) files in place with the 2528 database (you can download 2528 here http://download.buildwithcraft.com/craft/2.0/2.0.2539/Craft-2.0.2539.zip) or download the latest from buildwithcraft.com and let it perform the update.  
> **username_0**: Both the files and DB are now at current.  Javascript error has returned and occurs only on server and not on local machine :-/  Thoughts?  
> **username_1**: If you want to send some CP/FTP credentials over to support@buildwithcraft.com, we can look at it and I'll update the answer here with the result.  

---

