+1
Fixed

Sublime's "Setting - User" file is not as mentioned in the docs

Breno Calazans 7 years ago updated by Paul Sinclair 7 years ago 8

At http://www.codeivate.com/token is written that you should update the file. But the file can't be update, because it's an empty file. I guess you should say that you should write in a JSON compliant format, like so:

{

"user_id": "xxx",

"user_token": "yyy"

}


Answer

Answer
Fixed

**update 2**

This appears to be a problem if you have installed an alpha version of the Package control manager.  


The Alpha version of the Package Control manager seems to:

  •  Ignore multiple branches listed in the repositories channel it always downloads the "master" branch. 
  • Also the alpha version of Package control doesn't seem to be able to automatically update itself.


To fix:

  1. Shutdown Sublime
  2. Delete the Packages control folder from the /Packages directory.
  3. Re-install the package manager https://sublime.wbond.net/installation
  4. run "Package Control:upgrade package" to force Codeivate to update to the ST3 version.


**update**

Sorry about this, investigating now



Cheers,

Paul



Under review

Hi Breno,


Thanks for reporting this, what version are you on ST2 or ST3?

Is the plugin working? and have you restarted since installing the plugin?


There is some code that runs on startup that checks if several values are present in the user settings file, if they don't exist it creates defaults (this is to make it easier for people to edit)


Cheers,

Paul



Hi, Paul,


I'm using ST3. The plugin is not working, even after restarting ST3. I'll try restarting the PC, though.


I restarted and nothing happens too. 


I'm using Ubuntu, maybe this will help you debugging.

I had the same issue, and it appears my plugin isn't working either (been coding for a while now and dashboard is still empty)

I'm using ST3 Build 3047 and Mac OS 10.8.4. I installed the plugin via Package Control.


Thanks,
Matt

I restarted Sublime and looked at the plugin loading "logs" in the console.  Here are my logs for the Codeivate plugin:

reloading plugin Codeivate.codeivate
Traceback (most recent call last):
  File "/Applications/Sublime Text.app/Contents/MacOS/sublime_plugin.py", line 73, in reload_plugin
    m = importlib.import_module(modulename)
  File "X/importlib/__init__.py", line 88, in import_module
  File "<frozen importlib._bootstrap>", line 1577, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1558, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1525, in _find_and_load_unlocked
  File "/Applications/Sublime Text.app/Contents/MacOS/sublime_plugin.py", line 671, in load_module
    exec(compile(source, source_path, 'exec'), mod.__dict__)
  File "codeivate in /Users/xelldran1/Library/Application Support/Sublime Text 3/Installed Packages/Codeivate.sublime-package", line 3, in <module>
ImportError: No module named 'codeivated'

Hope these help.


Matt

Started

**update**

Sorry about this, investigating now



Cheers,

Paul



The Sublime text 3 Version seems to be pulling down the ST2 code, I have just opened an issue


https://github.com/wbond/package_control_channel/issues/1725


Hopefully I will be able to resolve this issue soon, but It should still work if you install it manually

https://github.com/codeivate/codeivate-st/tree/sublime3


Cheers,

- Paul





Answer
Fixed

**update 2**

This appears to be a problem if you have installed an alpha version of the Package control manager.  


The Alpha version of the Package Control manager seems to:

  •  Ignore multiple branches listed in the repositories channel it always downloads the "master" branch. 
  • Also the alpha version of Package control doesn't seem to be able to automatically update itself.


To fix:

  1. Shutdown Sublime
  2. Delete the Packages control folder from the /Packages directory.
  3. Re-install the package manager https://sublime.wbond.net/installation
  4. run "Package Control:upgrade package" to force Codeivate to update to the ST3 version.


**update**

Sorry about this, investigating now



Cheers,

Paul



+1

Hi Paul,


Thanks a lot!  


Matt

Thanks, Paul! It worked.

I had this problem, works now! Thanks!