Thread

Not sure if this is the right place for it, but it isn’t quite a support question either.

At the moment, I rely quite a bit on a couple of modules, a few plugins and a few extensions. Some of them look likely to be updated for 2.0, but others have been abandoned already. Given that I’d have to abandon some features of the site entirely if I have to stop using these add-ons, I’ll probably be stuck with 1.6 unless I can figure out how to change them myself.

This leaves me wondering if its possible to give a rough idea of how much changing modules, plugins and extensions will need to work with 2.0? Are we talking complete rewrites, or is it something that even a non-coder such as myself could stand a chance of handling? For example, will there be a conversion manual with instructions along the lines of ‘if it previous was done this way, now change X to Y, etc’?

I know its a while off yet and that it may not be possible to give any information so far, but if there are any hints regarding this it would be very useful. 😊

Only time will tell how much will be required for making a plugin 2.0 compatible.  But I’m sure the EL developers have tried to make it as easy as possible to do so while still leveraging the CI framework that EE 2.0 is built on.

I’ve read/heard on multiple occasions that instructions and support will be provided in converting 1.x addons to 2.0.

I’ll leave the rest for an “official” response.

I’m sure there will be a post about migrating. Difficult to say when. I’m keeping my head down until the announcement.

Have a look at GearLive’s video of the Q&A;session at SXSW.  Paul describes what will be required, and sorry, don’t have a timecode, you’ll have to watch the whole thing. 😉

Thanks, Derek, will take a look at it. 😊 Though, I admit to being dubious that I’ll understand much of anything described in that sort of context, since I lack a lot of the technical knowledge that probably is needed to follow the discussion. But it might give me some insight. 😊

Do you think there’s a possibility (when the times come for the upgrade, that is) of some dedicated topics (stickied, perhaps) in the module, plugin and extension forums where a note can be posted for each add-on that is converted, so that it is easy to get an overview of the situation? For a non-coder as myself, concerns about what will end up breaking has an unfortunate way of getting in the way of just being able to look forward to the upgrade, so anything that helps provide an overview of what will and what won’t work is really valuable. 😊

We will have a developer preview period where qualified third party developers will have an opportunity to get their add-ons up to speed with the assistance of the dev team.  We will likely have separate forums at that time for converting add-ons to 2.0 to facilitate this process during that time period.  But as this will be a very busy time for us and critical for end users that we help qualified third party devs get up to speed, those forums will likely be read-only for the general public.

That sounds great. Read-only access, just to see what is being done, would be just what’s needed, I think. 😊

Thanks. 😊