Sublime Forum

Package control update messages not appearing


I have been struggling to get messages to appear when I update my plugin. I have some feedback from users that they are not appearing. For me, my sublime points to my development directory so I don’t use package control for my particular plugin in the normal course of events.

But this time I switched to package control myself and waited for the updated to show up to see if it would work. I saw that it was updated in my console output, but still, no message was shown. Is it just me (I sure hope so!) or is there a general problem? Here’s my messages.json file:

  "install": "messages/install.txt",
  "2.0.0": "messages/v2.0.0.txt",
  "2.0.2": "messages/v2.0.2.txt",
  "2.0.4": "messages/v2.0.4.txt",
  "2.0.5": "messages/v2.0.5.txt",
  "2.0.6": "messages/v2.0.6.txt",
  "2.0.7": "messages/v2.0.7.txt",
  "2.0.8": "messages/v2.0.8.txt",
  "2.1.0": "messages/v2.1.0.txt",
  "2.1.1": "messages/v2.1.1.txt",
  "2.1.2": "messages/v2.1.2.txt",
  "2.1.3": "messages/v2.1.3.txt",
  "2.1.4": "messages/v2.1.4.txt",
  "2.1.5": "messages/v2.1.5.txt",
  "2.1.6": "messages/v2.1.6.txt",
  "2.1.7": "messages/v2.1.7.txt",

and my files are here:

$ ls -ls messages
total 144
 8 -rw-r--r--  1 jpayne  staff   524B Jun  6  2014 install.txt
 8 -rw-r--r--  1 jpayne  staff   773B Apr  2  2014 v2.0.0.txt
 8 -rw-r--r--  1 jpayne  staff   233B Apr  2  2014 v2.0.2.txt
 8 -rw-r--r--  1 jpayne  staff   650B Apr 17  2014 v2.0.4.txt
 8 -rw-r--r--  1 jpayne  staff   457B Jun  6  2014 v2.0.5.txt
 8 -rw-r--r--  1 jpayne  staff   173B Jun  6  2014 v2.0.6.txt
 8 -rw-r--r--  1 jpayne  staff   116B Sep 12  2014 v2.0.7.txt
 8 -rw-r--r--  1 jpayne  staff   639B Dec  6  2014 v2.0.8.txt
 8 -rw-r--r--  1 jpayne  staff   1.7K Feb 16  2015 v2.1.0.txt
 8 -rw-rw-r--  1 jpayne  staff   244B Mar 14  2015 v2.1.1.txt
 8 -rw-r--r--  1 jpayne  staff   192B Jan  6 14:32 v2.1.2.txt
 8 -rw-r--r--  1 jpayne  staff   505B Apr  2  2016 v2.1.3.txt
 8 -rw-r--r--  1 jpayne  staff   398B Apr 15  2016 v2.1.4.txt
 8 -rw-r--r--  1 jpayne  staff    97B Nov 26 11:11 v2.1.5.txt
 8 -rw-r--r--  1 jpayne  staff   318B Nov 26 11:56 v2.1.6.txt
24 -rw-r--r--  1 jpayne  staff   8.3K Jan  9 11:09 v2.1.7.txt

I am pretty sure the install.txt file showed up when I first installed from the package manager, so I must be on the right track.

I’d happily go to town experimenting with this, but I don’t want to annoy the people who are actually using this plugin with a billion updates as I muddle my way through this.

Any ideas of what I might be doing wrong? Is it the “v” in the file names? Should I lose the ‘v’ prefix?



Unfortunately the JSON spec does not allow a trailing comma. When you install or upgrade the package you will likely see a message in the console indicating the messages.json could not be parsed.



It’s going to sound like I’m doing an ad campaign soon, but I’ve done a plugin to deal with this comma in json: JSONComma. It adds the needed ones, and removes the trailing ones :wink:



That’s exactly what I’ve encountered! Unfortunately, there are no warning in the console, which make it hard to debug.