Members are able to reply in Ask the Boot Guys  

Quote:

Originally Posted by Cirquerider 

Same problem in Ask A Ski Pro.  Members can reply to threads.

Is somebody geeting frustrated with the lack of functionality?

God forbid us mere mortals reply!  Shoot, we might actually convey some honest to goodness knowledge!  I don't think there is a smiley for this, but I have bug eyes with my hands pressed against my cheeks!  Heavens!

It's a pity members can't respond in some of those forums.  I see "low hanging fruit" questions which any knowledgeable skier here could answer, yet many go unanswered or wait for hours/days before a sanctioned "expert" gets to it.  Some of these questions must surely be an annoyance or noise to the actual experts who seem busy at times.  It would probably improve efficiency/etc... if easy questions could be addressed by anyone who knew the answer.

Quote:

Originally Posted by krp8128 

 

Is somebody geeting frustrated with the lack of functionality?

Many of us are eager to have function back that is missing. However, that doesn't mean that we don't appreciate the change, aren't delighted to have it, and aren't looking forward to what the improvements will bring. Put me squarely in both of those camps.

And why exactly couldn't basic features like this have been implemented and tested before migrating a gigantic production site?

vBulletin had forum/subforum user permissions worked out about a decade ago.

Quote:

Originally Posted by Garrett 

 

Many of us are eager to have function back that is missing. However, that doesn't mean that we don't appreciate the change, aren't delighted to have it, and aren't looking forward to what the improvements will bring. Put me squarely in both of those camps.

And why exactly couldn't basic features like this have been implemented and tested before migrating a gigantic production site?

 

vBulletin had forum/subforum user permissions worked out about a decade ago.

Because we had other things to implement instead.

Quote:

Originally Posted by ssh 

Quote:

Originally Posted by Garrett 

And why exactly couldn't basic features like this have been implemented and tested before migrating a gigantic production site?

Because we had other things to implement instead.

Wow. I can't believe that's the answer.

I worked in the software world for 10 years for several companies, on desktop and web applications, and if we had ever removed functionality from one version in an upgrade to a new one, we'd have been publicly and painfully skewered - it was never even an option. I honestly can't believe this is the response.

Quote:

Originally Posted by friolator 

Wow. I can't believe that's the answer.

 

I worked in the software world for 10 years for several companies, on desktop and web applications, and if we had ever removed functionality from one version in an upgrade to a new one, we'd have been publicly and painfully skewered - it was never even an option. I honestly can't believe this is the response.

 

You're comparing an upgrade from one version of an application to the next version of the same, to migration from one application to a completely different platform.

They're entirely different things.

Quote:

Originally Posted by frankfarmer 

You're comparing an upgrade from one version of an application to the next version of the same, to migration from one application to a completely different platform.

 

They're entirely different things.

No, they aren't.  Not when the mission of the software hasn't changed.  If I walked into a CAD shop and replaced SolidWorks09 with MediaWiki mashed up with some open source CAD software, someone would fire me.  Because design is what the software was supposed to do well, not wiki.

Stick to what you know.  Telling members here how software upgrades should be done is not a topic you know.  You have zero credibility on that front; you've proven you don't know what you are doing.

Quote:

Originally Posted by Garrett 

No, they aren't.  Not when the mission of the software hasn't changed.  If I walked into a CAD shop and replaced SolidWorks09 with MediaWiki mashed up with some open source CAD software, someone would fire me.  Because design is what the software was supposed to do well, not wiki.

 

Stick to what you know.  Telling members here how software upgrades should be done is not a topic you know.  You have zero credibility on that front; you've proven you don't know what you are doing.

If you'd like to discuss your issues you have with the new platform in a constructive and civil manner, I'd love to have your feedback.

Quote:

Originally Posted by frankfarmer 

If you'd like to discuss your issues you have with the new platform in a constructive and civil manner, I'd love to have your feedback.

You see, that was both constructive and civil.  I'm sorry you have such a thin skin, but this is something you are going to have to learn if you expect to ever do this sort of migration with a real business.

Facts: 

• Epicski was traditionally a forum
• You pushed a migration to software that is obviously and wholly inferior to the previous forum.
• You must now take some responsibility for that.

I'm locking this thread because it has become uncivil.  The purpose of this forum is to report problems.  Please try to keep posts and threads devoted to that purpose.