Thread

EE 1.6 offers significant improvements over pMachine Pro 2.4 while at the same time suffering serious degradation of usability.

The “Admin” menus in EE are an abomination to people that actually went to school B4 education was abolished in the US?

Many great features of pMachine were lost in the EE 1.x package?

I for one have great hopes that EE 2 brought back those “lost” usability features. I will be installing my licensed copy and reviewing EE 2.02 in the next few days.

Some several obvious CMS features are absent in EE 1.x and required a lot of php blundering and hacking to achieve usefulness. To be fair the provided templates in EE 1.6 do not seriously exhibit the power of the program.

The 1.6 API is missing some several essential coding options and presents likewise some several coding options that do not work.

Don’t get me wrong EE runs circles around just about any CMS - free or otherwise.

I still wonder why EE fails to address basic issues and needs while adding exotic useless features.

Additionally EE should NOT require a HTML/PHP wizard to make the package dance.  It should dance as offered!

Usability is the most important facet of any software package.  Power don’t mean squat if the customer can’t figure out how to use it!

Once I have my EE 2 running I will post another topic regards its features.

While I’m sure you have some valid points, you might want to actually give some specific examples so people can discuss them.

I have made some several posts here regards the EE 1.x issues -vs- pMachine. Which were all ignored by the EE team?

My evaluation of my EE 2 test install today shows no change in attitude of the programmers.

Obviously the refreshing concept of the simple power of pMachine has been abandoned for “progress” in EE 1.x and 2.x?

EE far exceeds the “freeware” CMS offerings but has yet to justify the price points they have adopted.

The EE 2 paid download doesn’t even include installation instructions!!!  How would you feel if you paid $300 for a program and weren’t even given a clue about how to install it?

If the provided package requires serious hacking to become a practical platform how is the purchase price justified?  That hacking costs big bucks to a Commercial enterprise.  To me it means a lot of wasted hours which I could be doing other things.

I believe in EE but wonder if there is anyone with a brain in management.

Okay, I’ll tackle a few of these.

I have made some several posts here regards the EE 1.x issues -vs- pMachine. Which were all ignored by the EE team?

I agree that the EE team here aren’t as responsive or as open to criticism as they could or should be, and I think they have a long way to go in terms of effectively managing customers; but with that said I’ve never seen the blatantly ignore legitimate concerns.

Obviously the refreshing concept of the simple power of pMachine has been abandoned for “progress” in EE 1.x and 2.x?

Not sure I’d agree with this one. I think EE 1.x is a great improvement over pMachine and think EE 2.x is another step forward, although not quite the step I was hoping for. So not really sure what you want here.

EE far exceeds the “freeware” CMS offerings but has yet to justify the price points they have adopted.

Again, not sure I’d agree with this one. As mentioned above I don’t think EE 2.x is where it should be, but I definitely wouldn’t say it’s not worth the small price tag.

The EE 2 paid download doesn’t even include installation instructions!!!  How would you feel if you paid $300 for a program and weren’t even given a clue about how to install it?

I’m pretty sure the readme.txt that comes with EE 2 has a link to the documentation, which so happens to have a nice big area called installation. From memory they also give you a direct link to download a copy of the documentation if you’d prefer to have it local.

If the provided package requires serious hacking to become a practical platform how is the purchase price justified?  That hacking costs big bucks to a Commercial enterprise.  To me it means a lot of wasted hours which I could be doing other things.

Again you’ll need to be more specific here. As stated above I do believe EE isn’t where it should be, but it definitely doesn’t require serious hacking to meet the targets of most of my projects. Although I’m not sure what you’re building.

I believe in EE but wonder if there is anyone with a brain in management.

I think that’s pretty unfair and uncalled for. While I have my disagreements with the EE Team and think they have some areas that really need improvement, they’re an extremely smart and talented bunch.

Not to be too much of a fanboy for something that helps me make a living, but…

EE 1.6 offers significant improvements over pMachine Pro 2.4 while at the same time suffering serious degradation of usability.

Is it possible to list five or six of those?

The “Admin” menus in EE are an abomination to people that actually went to school B4 education was abolished in the US?

For those of us who prefer to deal in facts as opposed to poison pen barbs, would it be possible to list five or six reasons why it’s an abomination, and perhaps a few examples of what would make it better?

Many great features of pMachine were lost in the EE 1.x package?

Since pM Pro has been dead for many years, it’s probably a moot point, but could you list five or six of those great features? I started on pM Pro and don’t miss anything about it except the price.

I for one have great hopes that EE 2 brought back those “lost” usability features. I will be installing my licensed copy and reviewing EE 2.02 in the next few days.

And once you’ve done that and find that some usability has been lost, would you mind pointing them out for those of us who have never gone to school and can’t spell abomination?

Some several obvious CMS features are absent in EE 1.x and required a lot of php blundering and hacking to achieve usefulness. To be fair the provided templates in EE 1.6 do not seriously exhibit the power of the program.

The provided templates in EE are sooooo 1999. Maybe that’s why the vast majority of EE users build their own templates from scratch, though I suspect we do that because that’s what EE is really good at doing.

The 1.6 API is missing some several essential coding options and presents likewise some several coding options that do not work.

This would be a good opportunity to share some of those essential coding options as well as those that do not work. Since EE’s templates can run PHP, and EE comes with API’s for extensions, modules, and plugins, it would be good to know some of what we’re missing.

Don’t get me wrong EE runs circles around just about any CMS - free or otherwise.

Some of my friends are WordPress users.

I still wonder why EE fails to address basic issues and needs while adding exotic useless features.

Rats. And I thought all my basic issues were addressed. Any chance we could get a quick list of a dozen basic issues that are not addressed, and another list to identify all those useless features I’m using?

Additionally EE should NOT require a HTML/PHP wizard to make the package dance.  It should dance as offered!

Is there a comparable CMS app that lets you build a comparable-to-EE site without HTML? That would help. I can’t spell PHP.

Usability is the most important facet of any software package.  Power don’t mean squat if the customer can’t figure out how to use it! Once I have my EE 2 running I will post another topic regards its features.

Yeah, those tens of thousands of EE customers using EE already probably haven’t figured out that they haven’t really figured out how to use it. Looking forward to the list requests from above. I’m sure it will be enlightening.

Cheers.