Revo 2.1 Extras Compatibility

Since 2.1 brings the reduction of so much deprecated code including old Evo code, I think it’s very important that we know which Extras will and won’t work.

In the real world where shared hosting is the norm, most small sites don’t have the luxury of dev and staging environments so when they do the upgrade to 2.1, it’s a ’big bang’ approach - ie. not only does the core code have to work, all their existing Extras do too, straight off the bat otherwise they’ll be rolling back in minutes.

With that in mind, can we get an email out to all the authors in the package management database telling them to update their listings in the directory at http://modx.com/extras/package/ with some kind of clear Ready for Revo 2.1 strapline clearly display after they have thoroughly tested it?

This is exactly what I was driving at in this thread:

http://modxcms.com/forums/index.php/topic,64835.0.html

It appears from the responses that I must just be a demanding quack and shoudln’t expect so much.

with some kind of clear Ready for Revo 2.1 strapline clearly display after they have thoroughly tested it?

I would prefer the package manager to only show ones that work with the version of Revo that is installed as well as your suggestion.

Package Management will only show Extras that say they are compatible with your MODX version. However, if a developer of an Extra has not correctly marked their Extra as compatible, there is not really much we can do to help that. There is a "Report this Extra" button in the Extras section that you can use to report incorrectly marked Extras.

MODX cannot be responsible for the hundreds of 3rd-Party Extras that are out there. We’ve attempted to mitigate things, by adding ’solid’ markings on Extras vetted by the core team. But ultimately, this boils down to the developer of the Extra. The Core Team simply does not have the time to micromanage at that level.

We also notified the developers of Extras via a multitude of channels about 2.1’s changes. Again, if you find an Extra that is not correctly reporting compatibility (and incompatibility does not mean you find an obscure bug, it means completely not working because of deprecated code), you are free to report it using the link described above.

MODX cannot be responsible for the hundreds of 3rd-Party Extras that are out there. We’ve attempted to mitigate things, by adding ’solid’ markings on Extras vetted by the core team. But ultimately, this boils down to the developer of the Extra. The Core Team simply does not have the time to micromanage at that level.

Hi Shaun,

I totally agree with the fact that MODX can not be held responsible for vetting every single extra, but how about the following ( and this is only me thinking out loud )

When a extra is submitted it must be submitted with ( lets say ) decent instructions on the use of it ( for example 5 examples for different ways to use it ), that could then be added into a forum for testing by volunteers who only have access to that forum ( I’m more than willing to do tests on a development server ), the MODX team could set out a series of tests and the testers would follow them, if it passes the tests then it gets accepted to the package manager, if it doesn’t it gets passed back to the developer with the errors which they can then fix and re submit it, once passed the testers would update the wiki with the instructions ready for when the package is available.

Again I’m just thinking out loud so feel free to tell me to shut up

Quote from: paulp at Jun 08, 2011, 04:11 PM

When a extra is submitted it must be submitted with ( lets say ) decent instructions on the use of it ( for example 5 examples for different ways to use it ), that could then be added into a forum for testing by volunteers who only have access to that forum ( I’m more than willing to do tests on a development server ), the MODX team could set out a series of tests and the testers would follow them, if it passes the tests then it gets accepted to the package manager, if it doesn’t it gets passed back to the developer with the errors which they can then fix and re submit it, once passed the testers would update the wiki with the instructions ready for when the package is available.

While sounds okay in theory, that would never work in practice. That’s too high a bar for submission - not to mention, good luck finding 5 volunteers to commit to testing an Extra.

While sounds okay in theory, that would never work in practice. That’s too high a bar for submission - not to mention, good luck finding 5 volunteers to commit to testing an Extra.

Can’t say I agree with that, you have over 30,000 members and a lot of Partners so I’m more than sure we could get quite a few testers who are willing to give up a bit of time to do tests.

I used to test skins on invisionize before they started charging for mods etc, and everything on that site is tested before it is allowed into the downloads section, that site now has over 300,000 members and isn’t even an official site.

Any way it was just me thinking out loud, but if it wouldn’t work then not worth doing.