Hi,
I would like to use Mark Huot’s extension File. Is it possible to find out if I start using it now if it will create problems for me down the road with ee 2.0 and its new file management capabilities? For example will the extension be redundant?

There is no further information on EE 2.0 at this time.  As far as the File extension; add-on authors will need to update their addons to work with 2.0, so you’d need to follow up with Mark to see if he intends to do that with his extensions.

Caught me fishin’ did you?

Well we haven’t seen hide nor hair of the man around these parts. I’m sure he still logs on but isn’t very active in supporting his add-ons anymore. I’m sure he is extremely busy as he was always very active and helpful.

He does Twitter so he’s still alive at the very least!

I wonder why he disappeared?

Doesn’t he work for Happy Cog so perhaps busy around those parts instead?

From Mr. Hout’s web site:

EE 2.0 Upgrade Plans
When EE 2.0 is released none of the following add-ons will be ported to EE 2.0. If you have a specific request you can email me at docs@markhuot.com.

So there you go. I think 2.0 will make File obsolete/redundant, because the new built-in stuff just looks to be so much better. That’s a good thing though! Right?

Since many people use that extension, maybe someone else will volunteer hack it for 2.0, so that 1.6.x sites w/File won’t break if upgrading. But I wouldn’t bet the farm on that.

IF EE isn’t planning on replicating MH’s “File Upload” functionality, then EE should buy Mr. Huot’s code and roll it into 2.0.   

This basic functionally should be built in. Period. 

The current EE file upload, while quite useful in its own way, can be confusing / non intuitive for clients.    Fine perhaps for a personal blog but doesn’t cut it for a professional CMS.

I too look forward to much improved file management functionality in 2.0

The man’s name, however is Mark Huot

EE 2.0 Upgrade Plans
When EE 2.0 is released none of the following add-ons will be ported to EE 2.0. If you have a specific request you can email me at docs@markhuot.com.

Therein lies one of my major issues with 3rd party plugins, extensions, et al. Continuity. Or, lack of. A similar problem exists with open source projects—CMS apps like Joomla, Drupal, and Word Press—and even jQuery. There is a tremendous lack of follow through.

From what I can see, there are far too many 3rd party projects (plugins, extensions, etc.) that are cool, usable, effective, thoughtful, helpful, and apparently not very commercial—most of which will die on the proverbial Vine of Neglect™.

It isn’t just an issue with 3rd party EE plugins and extensions. It’s very common these days. That makes it a tougher decision for web site developers and designers to invest time, effort, and money into purchase and/or integration of 3rd party solutions, though such effort is encouraged by EE as well as other projects. When things change and progress, some of those ‘solutions’ die.

I’m certain that some of the neglect is the fact that creating a commercially successful 3rd party plugin, extension, or module is a major challenge, especially with the ongoing expense of support.

What I’ve been doing is exercising extreme caution when adopting 3rd party plugins and extensions for integration into a site; whether they be for EE, jQuery, or anything else.

It’s a jungle out there.

I see it slightly differently Ronnie.

Myself when I started out with ExpressionEngine I didn’t really have much knowledge at all about how they system worked, just rather that it did and I could fit a site together pretty quickly.

As time went by there were a few things that I needed which couldn’t quite be handled by the ExpressionEngine core code, or at least it would have meant having PHP in my templates which I really don’t like, so I turned my hand to learning how add-ons are created for the system. Admitted I have only made some natty little plugins at the moment but they have got me out of some tight situations at times and have also helped out lots of other users in the process too as I always give them all away for free (I must be mad ). So where I come from is that yes there are some great additions made for ExpressionEngine but you can’t expect that developer to be around for ever as jobs change and so do what they do so that’s why I started to learn for myself so that if the inevitable happens and something you are using suddenly stops working or doesn’t quite do what you want it to do then you have a better knowledge to try and fix it yourself.

I don’t think (and this is no sleight on any of the developers here at all) that you can rely on a solution / developer for ever, especially when the solution was free as they probably will change jobs and not be able to be around so much so learning for yourself is a good way to ensure you can carry on. It’s also good as you get a better understanding of the whole way that ExpressionEngine works.

That’s me though.

Best wishes,

Mark

My apologies to all and especially Mark Huot! I started the thread and I spelled his name incorrectly. :-(