Jason Coward

> > did you report this in the phpthumb repository? > > I did create a pull request 3 days ago. [JamesHeinrich/phpThumb#218](https://github.com/JamesHeinrich/phpThumb/pull/218) > Oh, great! I was searching issues instead...

This change is currently breaking the grunt build with the following error: ``` Running "uglify:jsgrps" (uglify) task JS_Parse_Error [SyntaxError]: Unexpected token: punc «.» at JS_Parse_Error.get (eval at (/Users/opengeek/www/revo-2.x/_build/templates/default/node_modules/uglify-js/tools/node.js:18:1), :71:23) at...

I'd really like to move forward on this. What needs to be done?

> As someone not involved in the development of MODX, there are certain things that make me scratch my head. There exists an API to check for every installed extra...

> Looping back around on this, I think what @rthrash suggests in his comment above makes sense. I'd maybe nuance it slightly by terming major releases an "Upgrade" while keeping...

I think it needs to send the full version string, including the release labels. This will still be running even when users have various pre-releases currently installed. The real issue...

So just include all releases > the one sent and let the component work it out?

> Also, I recently helped someone who skipped an x.0 version, had trouble, and solved it by going back and installing the .0 version. I think that issue still exists,...

> > That is not an issue except in specific cases where it was identified as one. All upgrades SHOULD be safe to run directly. > > I know this...

FYI, I'm testing an endpoint that can be used for this purpose. It will return all releases with a version greater than the "current" version sent to the endpoint. It...